Which versions of evil-package are affected by GHSA-P62R-JF56-H429?

evil-package (npm) versions >= 0.0.0 is affected.

Is there a fix for GHSA-P62R-JF56-H429?

No fixed version is listed for GHSA-P62R-JF56-H429 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-P62R-JF56-H429 exploitable, and should I be worried?

Whether GHSA-P62R-JF56-H429 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-P62R-JF56-H429 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-P62R-JF56-H429 in evil-package

GHSA-P62R-JF56-H429

GHSA-P62R-JF56-H429 is a critical-severity security vulnerability in evil-package (npm), affecting versions >= 0.0.0. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Malicious Package in evil-package

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

Impact

Affected versions

evil-package (>= 0.0.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is GHSA-P62R-JF56-H429? GHSA-P62R-JF56-H429 is a critical-severity security vulnerability in evil-package (npm), affecting versions >= 0.0.0. No fixed version is listed yet.
Which versions of evil-package are affected by GHSA-P62R-JF56-H429? evil-package (npm) versions >= 0.0.0 is affected.
Is there a fix for GHSA-P62R-JF56-H429? No fixed version is listed for GHSA-P62R-JF56-H429 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-P62R-JF56-H429 exploitable, and should I be worried? Whether GHSA-P62R-JF56-H429 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-P62R-JF56-H429 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.