Which versions of wormgpt-cli are malicious?

The following npm versions of wormgpt-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate wormgpt-cli if I installed it?

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.

I already installed wormgpt-cli — how do I know if it already compromised me?

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.

Is wormgpt-cli part of a known attack campaign?

Yes — wormgpt-cli is associated with the IN-MAL-2026-016743 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find wormgpt-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wormgpt-cli (version 1.0.0). 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.

Malicious package

wormgpt-clinpm

wormgpt-cli is a confirmed malicious npm package (MAL-2026-13466) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wormgpt-cli (npm)

MAL-2026-13466

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall wormgpt-cli

What this malware does

The package bundles an implant module at src/implant/implant.js that spawns bash, powershell, and screen-capture child processes, consistent with remote command execution and host surveillance. src/implant/stealers/clipboard.js uses execSync to invoke powershell for clipboard capture. src/protocol.js reads process.env and pairs child_process spawning with an HTTP/HTTPS POST channel carrying hostname and identifier fields, forming a command-and-control and data-exfiltration pathway. The package name and layout (an 'implant' directory with a 'stealers' subdirectory alongside a 'protocol' transport) advertise operator-side malware functionality, and the code paths that read installer environment data and shell out to system utilities are wired to the same network sink. Installing or loading this package places implant, stealer, and C2 code on the host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6f76eeb5f3df3c8ebc673a73d88aeb6dd0eb89b2b350a36023e2fe2a42eb8ed1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wormgpt-cli (version 1.0.0). 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

No. wormgpt-cli on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016743

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database