# GHSA-jjhg-qw5v-r8xx: Malicious Package in anarchy

> The anarchy npm package contains malicious code that deletes all files on the system during installation, requiring immediate removal.

- **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-jjhg-qw5v-r8xx?

GHSA-jjhg-qw5v-r8xx is a vulnerability in anarchy, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `anarchy` contain malicious code. The package ran `rm - rf /` as an install script.

## Recommendation

Remove the package from your environment.

## Which versions are affected by GHSA-jjhg-qw5v-r8xx?

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


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

## How do I fix GHSA-jjhg-qw5v-r8xx?

No fix has been published for GHSA-jjhg-qw5v-r8xx yet. Limit exposure of the affected software until one is available.

## Is GHSA-jjhg-qw5v-r8xx being exploited?

There is no known exploitation of GHSA-jjhg-qw5v-r8xx in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jjhg-qw5v-r8xx and fix it if it is affected.

What it is: GHSA-jjhg-qw5v-r8xx is a vulnerability in anarchy, 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-jjhg-qw5v-r8xx in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jjhg-qw5v-r8xx

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