# GHSA-w8fh-pvq2-x8c4: Malicious npm package: sonatype

> A malicious npm package named sonatype grants attackers full control of the host, requiring immediate secret rotation and system cleanup.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2021

## What is GHSA-w8fh-pvq2-x8c4?

GHSA-w8fh-pvq2-x8c4 is a vulnerability in sonatype, published on 29 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The npm `sonatype` package has been identified as malicious and removed from the npm package registry.

## Remediation

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## Which versions are affected by GHSA-w8fh-pvq2-x8c4?

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


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

## How do I fix GHSA-w8fh-pvq2-x8c4?

No fix has been published for GHSA-w8fh-pvq2-x8c4 yet. Limit exposure of the affected software until one is available.

## Is GHSA-w8fh-pvq2-x8c4 being exploited?

There is no known exploitation of GHSA-w8fh-pvq2-x8c4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-w8fh-pvq2-x8c4 and fix it if it is affected.

What it is: GHSA-w8fh-pvq2-x8c4 is a vulnerability in sonatype, published on 29 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-w8fh-pvq2-x8c4 in the wild and no public exploit code.

Affected packages and fixed versions:
- sonatype (npm): affected from 0.0.0; no fix listed
- sonatype (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-w8fh-pvq2-x8c4/ (Markdown: https://insights.sbomify.com/GHSA-w8fh-pvq2-x8c4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-w8fh-pvq2-x8c4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-w8fh-pvq2-x8c4/
Summaries are generated and may contain mistakes; the official description above is the record.