# GHSA-9hc2-w9gg-q6jw: Malicious Package in boogeyman

> Malicious npm package steals SSH keys and npm tokens by executing remote payloads, requiring immediate credential rotation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2020

## What is GHSA-9hc2-w9gg-q6jw?

GHSA-9hc2-w9gg-q6jw is a vulnerability in boogeyman, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-9hc2-w9gg-q6jw?

2 open source packages ship an affected version, including boogeyman.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `boogeyman` | npm | From 0.0.0 | None |
| `boogeyman` | npm | From 0.0.0 | None |

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

No fix has been published for GHSA-9hc2-w9gg-q6jw yet. Limit exposure of the affected software until one is available.

## Is GHSA-9hc2-w9gg-q6jw being exploited?

There is no known exploitation of GHSA-9hc2-w9gg-q6jw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9hc2-w9gg-q6jw and fix it if it is affected.

What it is: GHSA-9hc2-w9gg-q6jw is a vulnerability in boogeyman, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-9hc2-w9gg-q6jw in the wild and no public exploit code.

Affected packages and fixed versions:
- boogeyman (npm): affected from 0.0.0; no fix listed
- boogeyman (npm): affected from 0.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-9hc2-w9gg-q6jw/ (Markdown: https://insights.sbomify.com/GHSA-9hc2-w9gg-q6jw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9hc2-w9gg-q6jw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9hc2-w9gg-q6jw/
Summaries are generated and may contain mistakes; the official description above is the record.