Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

GHSA-jqjg-v355-hr9q

CRITICAL

GHSA-jqjg-v355-hr9q is a critical-severity (CVSS 9.8) vulnerability in buffer-xop. O3 Security confirms whether GHSA-jqjg-v355-hr9q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in buffer-xop

Published
Sep 3, 2020
Updated
Sep 29, 2021
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 29, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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

buffer-xopnpm
1downloads / week

Description

Version 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.

Recommendation

Remove the package from your environment. Ensure no Ethereum funds were compromised.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmbuffer-xop0.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for buffer-xop. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of buffer-xop has shipped for GHSA-jqjg-v355-hr9q yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jqjg-v355-hr9q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jqjg-v355-hr9q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user. ## Recommendation Remove the package from your environment. Ensure no Ethereum funds were compromised.
O3 Security · Impact-Aware SCA

Is GHSA-jqjg-v355-hr9q in your dependencies?

O3 detects GHSA-jqjg-v355-hr9q across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-jqjg-v355-hr9q: Malicious Package in… | O3 Security