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

GHSA-jh67-3wqw-cvhr

CRITICAL

GHSA-jh67-3wqw-cvhr is a critical-severity (CVSS 9.8) vulnerability in js-sxa3. O3 Security confirms whether GHSA-jh67-3wqw-cvhr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in js-sxa3

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

Real-World Exposure

1 pkg affected
📦js-sxa3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Version 0.8.0 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
📦npmjs-sxa30.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 js-sxa3. 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 js-sxa3 has shipped for GHSA-jh67-3wqw-cvhr 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-jh67-3wqw-cvhr 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-jh67-3wqw-cvhr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 0.8.0 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-jh67-3wqw-cvhr in your dependencies?

O3 detects GHSA-jh67-3wqw-cvhr 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-jh67-3wqw-cvhr: Malicious Package in… | O3 Security