How severe is GHSA-p62r-jf56-h429?

No CVSS score has been assigned to GHSA-p62r-jf56-h429 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p62r-jf56-h429?

GHSA-p62r-jf56-h429 affects the following packages: evil-package (npm). Ecosystems affected: npm.

How do I fix GHSA-p62r-jf56-h429?

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.

How do I detect GHSA-p62r-jf56-h429 in my npm dependencies?

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

How do I mitigate GHSA-p62r-jf56-h429 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-p62r-jf56-h429 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p62r-jf56-h429 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-p62r-jf56-h429 published, and has it been updated?

GHSA-p62r-jf56-h429 was published on September 3, 2020 and was last updated on August 31, 2020. 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

Malicious Package in evil-packageGHSA-p62r-jf56-h429

GHSA-p62r-jf56-h429 is a security vulnerability in evil-package. No vendor fix is recorded yet; mitigation options are listed below.

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

55downloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`evil-package`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for evil-package, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
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.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works