Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Malicious Package in destroyer-of-worldsGHSA-w3f3-4j22-2v3p

CRITICAL

GHSA-w3f3-4j22-2v3p is a critical-severity (CVSS 9.8) vulnerability in destroyer-of-worlds. No vendor fix is recorded yet; mitigation options are listed below.

Published
Updated
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 30, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

destroyer-of-worldsnpm
5downloads / week

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmdestroyer-of-worldsall versionsNo fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for destroyer-of-worlds, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of destroyer-of-worlds has shipped for GHSA-w3f3-4j22-2v3p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-w3f3-4j22-2v3p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Malicious Package in destroyer-of-worlds (Critical 9.8)