# GHSA-w3f3-4j22-2v3p: Malicious Package in destroyer-of-worlds

> A malicious npm package executes destructive bash scripts during installation, causing system file deletion and resource exhaustion on UNIX systems.

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

## What is GHSA-w3f3-4j22-2v3p?

GHSA-w3f3-4j22-2v3p is a vulnerability in destroyer-of-worlds, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package `destroyer-of-worlds` contained malicious code. The package contained a bash script that was run as a postinstall script. The script deleted system files and attempted to exhaust resources by creating a large file, a fork bomb and an endless loop. The script targeted UNIX systems.

## Recommendation

Remove the package from your environment and perform additional incident response on your system's files and processes.

## Which versions are affected by GHSA-w3f3-4j22-2v3p?

2 open source packages ship an affected version, including destroyer-of-worlds.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `destroyer-of-worlds` | npm | All versions | None |
| `destroyer-of-worlds` | npm | All versions | None |

## How do I fix GHSA-w3f3-4j22-2v3p?

No fix has been published for GHSA-w3f3-4j22-2v3p yet. Limit exposure of the affected software until one is available.

## Is GHSA-w3f3-4j22-2v3p being exploited?

There is no known exploitation of GHSA-w3f3-4j22-2v3p in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-w3f3-4j22-2v3p and fix it if it is affected.

What it is: GHSA-w3f3-4j22-2v3p is a vulnerability in destroyer-of-worlds, published on 2 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-w3f3-4j22-2v3p in the wild and no public exploit code.

Affected packages and fixed versions:
- destroyer-of-worlds (npm): affected all versions; no fix listed
- destroyer-of-worlds (npm): affected all versions; 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-w3f3-4j22-2v3p/ (Markdown: https://insights.sbomify.com/GHSA-w3f3-4j22-2v3p/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-w3f3-4j22-2v3p

---
From sbomify Insights: https://insights.sbomify.com/GHSA-w3f3-4j22-2v3p/
Summaries are generated and may contain mistakes; the official description above is the record.