wormgpt-clinpm
wormgpt-cli is a confirmed malicious npm package (MAL-2026-13466) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in wormgpt-cli (npm)
What this malware does
The package's bin entries (wormgpt-cli, wormgpt, deepholegpt, wgpt) map to bin/victim.js, which silently spawns a detached implant on any invocation (including --help/--version). The implant connects to a hardcoded C2 at http://13.60.13.215:7771 over an AES-256-GCM/HMAC-signed protocol with pool failover and a DNS TXT dead-drop channel (protocol.js pollDnsDeaddrop) that rotates the C2 URL and shared secret at runtime. On beacon, implant.js gatherInfo() collects hostname, user, OS, architecture, PID, cwd, home, LAN IP, admin flag, and a persistent victim_id, and accepts opcodes for shell/PowerShell execution, interactive PTY reverse shell, file up/download, keylogging (GetAsyncKeyState PowerShell loop), clipboard capture, screenshots, LAN lateral-movement scanning, privilege-escalation checks, and anti-forensics wipe. stealers/browser.js reads Chrome/Edge/Brave/Opera/Vivaldi Login Data SQLite databases, decrypts DPAPI-protected passwords via PowerShell with an AMSI bypass stub (AMSI_BYPASS_B64 base64 blob run through powershell -EncodedCommand), parses Firefox logins.json, and regex-scans Discord/Chrome LevelDB for auth tokens (/[\w-]{24}\.[\w-]{6}\.[\w-]{27}|mfa\.[\w-]{84}/g), exfiltrating results via C2 opcode OP_BROWSER_DATA. persist.js installs persistence across six autostart layers per OS: Windows HKCU/HKLM Run keys, Startup.lnk, WMI __EventFilter/CommandLineEventConsumer permanent subscription, scheduled tasks, and hidden Windows Helper directories via attrib +H +S; Linux XDG autostart, systemd --user units, @reboot crontab, shell RC injection (.bashrc/.zshrc/.profile/.xinitrc), and /etc/rc.local; macOS LaunchAgent plist with KeepAlive and Login Items via osascript. loader.js runs a watchdog sibling process (poll every 20s, MAX_REVIVES = 50) plus uncaughtException respawn to keep the implant alive.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wormgpt-cli (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wormgpt-cli across your stack and pipelines.
If you installed it — respond
wormgpt-cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wormgpt-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks wormgpt-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks wormgpt-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.