Summary
Malicious Package in destroyer-of-worlds
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.
Impact
GHSA-W3F3-4J22-2V3P has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Remove the package from your environment and perform additional incident response on your system's files and processes.
Frequently Asked Questions
- What is GHSA-W3F3-4J22-2V3P? GHSA-W3F3-4J22-2V3P is a critical-severity security vulnerability in destroyer-of-worlds (npm), affecting versions >= 0. No fixed version is listed yet.
- How severe is GHSA-W3F3-4J22-2V3P? GHSA-W3F3-4J22-2V3P has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of destroyer-of-worlds are affected by GHSA-W3F3-4J22-2V3P? destroyer-of-worlds (npm) versions >= 0 is affected.
- Is there a fix for GHSA-W3F3-4J22-2V3P? No fixed version is listed for GHSA-W3F3-4J22-2V3P yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-W3F3-4J22-2V3P exploitable, and should I be worried? Whether GHSA-W3F3-4J22-2V3P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-W3F3-4J22-2V3P is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.