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

GHSA-p62r-jf56-h429

GHSA-p62r-jf56-h429 is a security vulnerability in evil-package. O3 Security confirms whether GHSA-p62r-jf56-h429 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in evil-package

Published
Sep 3, 2020
Updated
Aug 31, 2020
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Aug 31, 2020 · 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.

evil-packagenpm
69downloads / week

Description

All versions of evil-package contain malicious code. The package uploads the contents of process.env to example.com/log.

Recommendation

Remove the package from your environment. Given the host where the information was uploaded to there is no further indication of compromise.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmevil-package0.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 evil-package. 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 evil-package has shipped for GHSA-p62r-jf56-h429 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-p62r-jf56-h429 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-p62r-jf56-h429. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `evil-package` contain malicious code. The package uploads the contents of `process.env` to `example.com/log`. ## Recommendation Remove the package from your environment. Given the host where the information was uploaded to there is no further indication of compromise.
O3 Security · Impact-Aware SCA

Is GHSA-p62r-jf56-h429 in your dependencies?

O3 detects GHSA-p62r-jf56-h429 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-p62r-jf56-h429: Malicious Package in… | O3 Security