How severe is GHSA-qj3p-xc97-xw74?

No CVSS score has been assigned to GHSA-qj3p-xc97-xw74 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qj3p-xc97-xw74?

GHSA-qj3p-xc97-xw74 affects the following packages: @metamask/sdk (npm), @metamask/sdk-react (npm), @metamask/sdk-communication-layer (npm). Ecosystems affected: npm.

How do I fix GHSA-qj3p-xc97-xw74?

Update @metamask/sdk to 0.33.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qj3p-xc97-xw74 is resolved across your whole dependency graph.

How do I detect GHSA-qj3p-xc97-xw74 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @metamask/sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qj3p-xc97-xw74 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qj3p-xc97-xw74 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qj3p-xc97-xw74 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qj3p-xc97-xw74 published, and has it been updated?

GHSA-qj3p-xc97-xw74 was published on September 15, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

MetaMask SDK indirectly exposed via malicious [email protected] dependencyGHSA-qj3p-xc97-xw74

Fix: MetaMask/metamask-sdk#1342

GHSA-qj3p-xc97-xw74 is a security vulnerability in @metamask/sdk. A fix is available for @metamask/sdk — see the affected versions and patch details below.

Published

Sep 15, 2025

Updated

Sep 15, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 15, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@metamask/sdknpm

519Kdownloads / week

@metamask/sdk-reactnpm

755downloads / week

@metamask/sdk-communication-layernpm

525Kdownloads / week

Description

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 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

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_modules and 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

GitHub Advisory for debug

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@metamask/sdk`	≥ 0.16.0&&< 0.33.1	0.33.1`npm install @metamask/sdk@0.33.1`
📦npm	`@metamask/sdk-react`	≥ 0.16.0&&< 0.33.1	0.33.1`npm install @metamask/sdk-react@0.33.1`
📦npm	`@metamask/sdk-communication-layer`	≥ 0.16.0&&< 0.33.1	0.33.1`npm install @metamask/sdk-communication-layer@0.33.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @metamask/sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @metamask/sdk to 0.33.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qj3p-xc97-xw74 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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` 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 attem

O3 Security · Impact-Aware SCA

Is GHSA-qj3p-xc97-xw74 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works