MetaMask SDK indirectly exposed via malicious [email protected] dependency - @metamask/sdk
- Severity:
- Medium
Description
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 lo
Recommendation
Update the @metamask/sdk package to the latest compatible version. Followings are version details:
- Affected version(s): >= 0.16.0, <= 0.33.0
- Patched version(s): 0.33.1
References
Related Issues
- MetaMask SDK indirectly exposed via malicious [email protected] dependency - Vulnerability
- MetaMask SDK indirectly exposed via malicious [email protected] dependency - @metamask/sdk-react - Vulnerability
- MCPHub has Path Traversal via Malicious MCPB Manifest Name - Vulnerability
- Electerm Security Vulnerability: RCE via malicious SSH server filename in openFileWithEditor - CVE-2026-43943
You might also like:
- Tags:
- npm
- @metamask/sdk
Anything's wrong? Let us know Last updated on September 15, 2025