What is GHSA-2HQF-QQMQ-PGPP?

GHSA-2HQF-QQMQ-PGPP is a critical-severity security vulnerability in commander-js (npm), affecting versions >= 0.0.0. No fixed version is listed yet.

How severe is GHSA-2HQF-QQMQ-PGPP?

GHSA-2HQF-QQMQ-PGPP has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of commander-js are affected by GHSA-2HQF-QQMQ-PGPP?

commander-js (npm) versions >= 0.0.0 is affected.

Is there a fix for GHSA-2HQF-QQMQ-PGPP?

No fixed version is listed for GHSA-2HQF-QQMQ-PGPP yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-2HQF-QQMQ-PGPP exploitable, and should I be worried?

Whether GHSA-2HQF-QQMQ-PGPP 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-2HQF-QQMQ-PGPP 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-2HQF-QQMQ-PGPP in commander-js

Summary

Malicious Package in commander-js

All versions of commander-js are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads an arbitrary file and executes its contents as a post-install script.

Impact

GHSA-2HQF-QQMQ-PGPP has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

commander-js (>= 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

This package is not available on the npm Registry anymore. If you happen to find this package in your environment you should consider the system it was installed on compromised and assess if further response (such as rotating all credentials found on the compromised machine) is necessary.

Frequently Asked Questions

What is GHSA-2HQF-QQMQ-PGPP? GHSA-2HQF-QQMQ-PGPP is a critical-severity security vulnerability in commander-js (npm), affecting versions >= 0.0.0. No fixed version is listed yet.
How severe is GHSA-2HQF-QQMQ-PGPP? GHSA-2HQF-QQMQ-PGPP has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of commander-js are affected by GHSA-2HQF-QQMQ-PGPP? commander-js (npm) versions >= 0.0.0 is affected.
Is there a fix for GHSA-2HQF-QQMQ-PGPP? No fixed version is listed for GHSA-2HQF-QQMQ-PGPP yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-2HQF-QQMQ-PGPP exploitable, and should I be worried? Whether GHSA-2HQF-QQMQ-PGPP 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-2HQF-QQMQ-PGPP 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.