GHSA-w3f3-4j22-2v3p
CRITICALGHSA-w3f3-4j22-2v3p is a critical-severity (CVSS 9.8) vulnerability in destroyer-of-worlds. O3 Security confirms whether GHSA-w3f3-4j22-2v3p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Malicious Package in destroyer-of-worlds
Real-World Exposure
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-worldsnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | destroyer-of-worlds | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for destroyer-of-worlds. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-w3f3-4j22-2v3p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w3f3-4j22-2v3p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w3f3-4j22-2v3p in your dependencies?
O3 detects GHSA-w3f3-4j22-2v3p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.