# GHSA-725f-3pw7-rq6x: Malicious Package in 8.9.4

> A malicious npm package reads local SSH keys during installation, requiring users to remove the package to prevent credential exposure.

- **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:** 3 Sep 2020

## What is GHSA-725f-3pw7-rq6x?

GHSA-725f-3pw7-rq6x is a vulnerability in 8.9.4, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions 1.0.2, 1.0.3, 1.0.4 and 1.0.5 of `8.9.4` contain malicious code as a preinstall script. The package reads the system's SSH keys but does not upload it to a remote server.

## Recommendation

Remove the package from your environment. There is no evidence of further compromise at the moment.

## Which versions are affected by GHSA-725f-3pw7-rq6x?

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


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

## How do I fix GHSA-725f-3pw7-rq6x?

No fix has been published for GHSA-725f-3pw7-rq6x yet. Limit exposure of the affected software until one is available.

## Is GHSA-725f-3pw7-rq6x being exploited?

There is no known exploitation of GHSA-725f-3pw7-rq6x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-725f-3pw7-rq6x and fix it if it is affected.

What it is: GHSA-725f-3pw7-rq6x is a vulnerability in 8.9.4, published on 3 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-725f-3pw7-rq6x in the wild and no public exploit code.

Affected packages and fixed versions:
- 8.9.4 (npm): affected from 0.0.0; no fix listed
- 8.9.4 (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-725f-3pw7-rq6x/ (Markdown: https://insights.sbomify.com/GHSA-725f-3pw7-rq6x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-725f-3pw7-rq6x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-725f-3pw7-rq6x/
Summaries are generated and may contain mistakes; the official description above is the record.