How severe is GHSA-9hc2-w9gg-q6jw?

GHSA-9hc2-w9gg-q6jw has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9hc2-w9gg-q6jw?

GHSA-9hc2-w9gg-q6jw affects the following packages: boogeyman (npm). Ecosystems affected: npm.

How do I fix GHSA-9hc2-w9gg-q6jw?

No patched version of boogeyman has shipped for GHSA-9hc2-w9gg-q6jw 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-9hc2-w9gg-q6jw in my npm dependencies?

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

How do I mitigate GHSA-9hc2-w9gg-q6jw 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-9hc2-w9gg-q6jw actively exploited in the wild?

No public exploit code has been indexed for GHSA-9hc2-w9gg-q6jw 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-9hc2-w9gg-q6jw published, and has it been updated?

GHSA-9hc2-w9gg-q6jw was published on September 1, 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 boogeymanGHSA-9hc2-w9gg-q6jw

CRITICAL

GHSA-9hc2-w9gg-q6jw is a critical-severity (CVSS 9.8) vulnerability in boogeyman. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 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.

boogeymannpm

61downloads / week

Description

All versions of boogeyman are considered malicious. This particular package would download a payload from pastebin.com, eval it to read ssh keys and the users .npmrc and send them to a private pastebin account.

Recommendation

This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate your ssh keys and your npm token.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`boogeyman`	≥ 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 boogeyman, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of boogeyman has shipped for GHSA-9hc2-w9gg-q6jw 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 `boogeyman` are considered malicious. This particular package would download a payload from pastebin.com, eval it to read ssh keys and the users `.npmrc` and send them to a private pastebin account. ## Recommendation This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate your ssh keys and your npm token.

O3 Security · Impact-Aware SCA

Is GHSA-9hc2-w9gg-q6jw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works