@metamask/sdk
Affected
- introduced
0.16.0, fixed0.33.1(semver)
Fixed versions
0.33.1
Fix
- Fixed version
0.33.1npm install @metamask/[email protected]
Advisory
Also known as: None
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:
[email protected] (e.g., via npm update or yarn 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
[email protected].node_modules and reinstall dependencies before deploying.Resources
GitHub Advisory for debug
Medium Basis: The source's own band: MODERATE
0.16.0, fixed 0.33.1 (semver)0.33.1
0.33.1npm install @metamask/[email protected]0.16.0, fixed 0.33.1 (semver)0.33.1
0.33.1npm install @metamask/[email protected]0.16.0, fixed 0.33.1 (semver)0.33.1
0.33.1npm install @metamask/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0