How severe is GHSA-2hqf-qqmq-pgpp?

GHSA-2hqf-qqmq-pgpp has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2hqf-qqmq-pgpp?

GHSA-2hqf-qqmq-pgpp affects the following packages: commander-js (npm). Ecosystems affected: npm.

How do I fix GHSA-2hqf-qqmq-pgpp?

No patched version of commander-js has shipped for GHSA-2hqf-qqmq-pgpp 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-2hqf-qqmq-pgpp in my npm dependencies?

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

How do I mitigate GHSA-2hqf-qqmq-pgpp 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-2hqf-qqmq-pgpp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2hqf-qqmq-pgpp 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-2hqf-qqmq-pgpp published, and has it been updated?

GHSA-2hqf-qqmq-pgpp was published on September 2, 2020 and was last updated on October 1, 2021. 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

CRITICAL severity

Malicious Package in commander-jsGHSA-2hqf-qqmq-pgpp

CRITICAL

GHSA-2hqf-qqmq-pgpp is a critical-severity (CVSS 9.8) vulnerability in commander-js. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 2, 2020

Updated

Oct 1, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 1, 2021 · 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.

commander-jsnpm

4downloads / week

Description

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.

Recommendation

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`commander-js`	≥ 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 commander-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of commander-js has shipped for GHSA-2hqf-qqmq-pgpp 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 `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. ## Recommendation 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.

O3 Security · Impact-Aware SCA

Is GHSA-2hqf-qqmq-pgpp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works