GHSA-qj3p-xc97-xw74: MetaMask SDK indirectly exposed via malicious [email protected] dependency
Who is affected? This advisory only applies to developers who use MetaMask SDK in the browser and who, on Sept 8th 2025 between 13:00–15:30 UTC, performed one of the following actions and then deployed their application: - Installed MetaMask SDK into a project with a lockfile for the first time - Installed MetaMask SDK in a project without a lockfile - Updated a lockfile to pull in [email protected] (e.g., via npm update…
Published Sep 15, 2025
Affected packages
@metamask/sdk
- Ecosystem
- npm
- Affected
- >= 0.16.0, <= 0.33.0
- Fixed in
- 0.33.1
- Check
npm ls @metamask/sdk
@metamask/sdk-react
- Ecosystem
- npm
- Affected
- >= 0.16.0, <= 0.33.0
- Fixed in
- 0.33.1
- Check
npm ls @metamask/sdk-react
@metamask/sdk-communication-layer
- Ecosystem
- npm
- Affected
- >= 0.16.0, <= 0.33.0
- Fixed in
- 0.33.1
- Check
npm ls @metamask/sdk-communication-layer
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Who is affected?
This advisory only applies to developers who use MetaMask SDK in the browser and who, on Sept 8th 2025 between 13:00–15:30 UTC, performed one of the following actions and then deployed their application:
- Installed MetaMask SDK into a project with a lockfile for the first time
- Installed MetaMask SDK in a project without a lockfile
- Updated a lockfile to pull in
[email protected](e.g., vianpm updateoryarn upgrade)
What happened?
On Sept 8th, 2025 (13:00–15:30 UTC), a malicious version of the debug package (v4.4.2) was published to npm. The injected code attempts to interfere with dApp-to-wallet communication when executed in a browser context.
While MetaMask SDK itself was not directly impacted, projects installing the SDK during this window may have inadvertently pulled in the malicious version of debug.
Mitigation
- If your application was rebuilt and redeployed after Sept 8th, 2025, 15:30 UTC, the malicious version of debug should no longer be present. Please also verify that your package manager (npm, yarn, pnpm, etc.) is not caching
[email protected]. - If you have not yet deployed since performing one of the actions above, delete your
node_modulesand reinstall dependencies before deploying. - If your application was deployed during the attack window and has not been rebuilt since, perform a clean install of dependencies and redeploy to ensure the malicious package is removed.
Resources
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
