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

GHSA-wfjh-3hq2-r276

CRITICAL

GHSA-wfjh-3hq2-r276 is a critical-severity (CVSS 9.8) vulnerability in node-spdy. O3 Security confirms whether GHSA-wfjh-3hq2-r276 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in node-spdy

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

Real-World Exposure

1 pkg affected
📦node-spdy

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

This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.

Recommendation

Remove the package from your environment. There are no indications of further compromise.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmnode-spdy0.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 node-spdy. 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 node-spdy has shipped for GHSA-wfjh-3hq2-r276 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-wfjh-3hq2-r276 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-wfjh-3hq2-r276. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server. ## Recommendation Remove the package from your environment. There are no indications of further compromise.
O3 Security · Impact-Aware SCA

Is GHSA-wfjh-3hq2-r276 in your dependencies?

O3 detects GHSA-wfjh-3hq2-r276 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-wfjh-3hq2-r276: Malicious Package in… | O3 Security