{"id":"GHSA-qj3p-xc97-xw74","aliases":[],"status":"published","title":"MetaMask SDK indirectly exposed via malicious debug@4.4.2 dependency","description":"### Who is affected?\nThis 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:\n- Installed MetaMask SDK into a project with a lockfile for the first time\n- Installed MetaMask SDK in a project without a lockfile\n- Updated a lockfile to pull in `debug@4.4.2` (e.g., via `npm update` or `yarn upgrade`)\n\n### What happened?\nOn 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. \n\nWhile MetaMask SDK itself was not directly impacted, projects installing the SDK during this window may have inadvertently pulled in the malicious version of `debug`.\n\n### Mitigation\n- 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 `debug@4.4.2`.\n- If you have not yet deployed since performing one of the actions above, delete your `node_modules` and reinstall dependencies before deploying.\n- 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.\n\n### Resources\n[GitHub Advisory for debug](https://github.com/advisories/GHSA-8mgj-vmr8-frr6)","facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-506"],"published":"2025-09-15T13:55:56Z","modified":"2025-09-15T13:55:59Z","fixes":[{"ecosystem":"npm","package":"@metamask/sdk","fixed_in":["0.33.1"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@metamask/sdk-react","fixed_in":["0.33.1"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@metamask/sdk-communication-layer","fixed_in":["0.33.1"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"@metamask/sdk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.16.0"},{"last_affected":"0.33.0"},{"fixed":"0.33.1"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@metamask/sdk-react","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.16.0"},{"last_affected":"0.33.0"},{"fixed":"0.33.1"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@metamask/sdk-communication-layer","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.16.0"},{"last_affected":"0.33.0"},{"fixed":"0.33.1"}]}]},{"source":"osv","ecosystem":"npm","package":"@metamask/sdk","ranges":[{"type":"SEMVER","events":[{"introduced":"0.16.0"},{"fixed":"0.33.1"}]}]},{"source":"osv","ecosystem":"npm","package":"@metamask/sdk-react","ranges":[{"type":"SEMVER","events":[{"introduced":"0.16.0"},{"fixed":"0.33.1"}]}]},{"source":"osv","ecosystem":"npm","package":"@metamask/sdk-communication-layer","ranges":[{"type":"SEMVER","events":[{"introduced":"0.16.0"},{"fixed":"0.33.1"}]}]}],"references":[{"url":"https://github.com/MetaMask/metamask-sdk/security/advisories/GHSA-qj3p-xc97-xw74","tags":["web"]},{"url":"https://github.com/MetaMask/metamask-sdk/pull/1342","tags":["web"]},{"url":"https://github.com/MetaMask/metamask-sdk/commit/baa185c6cfa97755a3d389d956372ad9eb37c4a4","tags":["web"]},{"url":"https://github.com/advisories/GHSA-qj3p-xc97-xw74"},{"url":"https://github.com/MetaMask/metamask-sdk","tags":["package"]}],"sources":{"ghsa":[{"id":"GHSA-qj3p-xc97-xw74","title":"MetaMask SDK indirectly exposed via malicious debug@4.4.2 dependency","description":"### Who is affected?\nThis 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:\n- Installed MetaMask SDK into a project with a lockfile for the first time\n- Installed MetaMask SDK in a project without a lockfile\n- Updated a lockfile to pull in `debug@4.4.2` (e.g., via `npm update` or `yarn upgrade`)\n\n### What happened?\nOn 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. \n\nWhile MetaMask SDK itself was not directly impacted, projects installing the SDK during this window may have inadvertently pulled in the malicious version of `debug`.\n\n### Mitigation\n- 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 `debug@4.4.2`.\n- If you have not yet deployed since performing one of the actions above, delete your `node_modules` and reinstall dependencies before deploying.\n- 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.\n\n### Resources\n[GitHub Advisory for debug](https://github.com/advisories/GHSA-8mgj-vmr8-frr6)","status":"published","published":"2025-09-15T13:55:56Z","modified":"2025-09-15T13:55:59Z","cwes":["CWE-506"],"updated_at":"2026-11-02T14:38:58.107905Z"}],"osv":[{"id":"GHSA-qj3p-xc97-xw74","title":"MetaMask SDK indirectly exposed via malicious debug@4.4.2 dependency","description":"### Who is affected?\nThis 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:\n- Installed MetaMask SDK into a project with a lockfile for the first time\n- Installed MetaMask SDK in a project without a lockfile\n- Updated a lockfile to pull in `debug@4.4.2` (e.g., via `npm update` or `yarn upgrade`)\n\n### What happened?\nOn 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. \n\nWhile MetaMask SDK itself was not directly impacted, projects installing the SDK during this window may have inadvertently pulled in the malicious version of `debug`.\n\n### Mitigation\n- 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 `debug@4.4.2`.\n- If you have not yet deployed since performing one of the actions above, delete your `node_modules` and reinstall dependencies before deploying.\n- 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.\n\n### Resources\n[GitHub Advisory for debug](https://github.com/advisories/GHSA-8mgj-vmr8-frr6)","status":"published","published":"2025-09-15T13:55:56Z","modified":"2025-09-15T13:55:56Z","cwes":["CWE-506"],"updated_at":"2026-11-02T15:46:54.760124Z"}]}}