Malicious code in wormgpt-cli (npm)
The npm package wormgpt-cli contained malicious code including remote command execution, clipboard stealing, and command-and-control functionality. The package bundled implant modules designed to spawn shell processes, capture system data, and exfiltrate information via HTTP/HTTPS to a remote server.
- Disclosed
- Last updated
- Blast radius
- Any system that installed or loaded the wormgpt-cli package
- Ecosystems
- Attack vectors
- Affected entities
- wormgpt-clinpm package containing malicious implant code
The npm package wormgpt-cli was found to contain intentionally malicious code discovered through analysis by Amazon Inspector. The package included an implant module (src/implant/implant.js) that spawns bash, powershell, and screen-capture child processes for remote command execution and host surveillance capabilities.\n\nThe malicious functionality included clipboard stealing via src/implant/stealers/clipboard.js, which uses execSync to invoke powershell commands. The src/protocol.js file establishes command-and-control and data-exfiltration pathways by reading process environment variables and pairing child process spawning with HTTP/HTTPS POST requests that transmit hostname and identifier information.\n\nThe package structure—with dedicated 'implant' and 'stealers' subdirectories alongside protocol transport code—indicates deliberate operator-side malware design. Installation or loading of this package would place implant, stealer, and C2 code on the host system.\n\nThe malicious package was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- wormgpt-cli
Remediation
- Immediately uninstall wormgpt-cli from all systems
- Audit npm package.json and lock files for any references to wormgpt-cli
- Review system logs and process history for suspicious bash, powershell, or screen-capture activity on affected hosts
- Check for unauthorized network connections or data exfiltration to unknown HTTP/HTTPS endpoints
- Regenerate any credentials or sensitive data that may have been exposed via clipboard capture
- Implement npm package scanning and verification in CI/CD pipelines to detect malicious packages before installation
- Monitor npm registry advisories and OpenSSF malicious-packages repository for similar threats
Sources
- GitHub Advisory GHSA-fw33-jr6r-h62p · GitHub Advisory Database
Cite this entry
"Malicious code in wormgpt-cli (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-wormgpt-cli-npm-eekodc
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package