Which versions of virgil-cli are malicious?

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

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

virgil-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 virgil-cli — how do I know if it already compromised me?

If virgil-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Search your lockfiles and build artifacts for virgil-cli (version 0.1.4).

Malicious package

virgil-clinpm

Advisory published Oct 3, 2026Updated Oct 5, 2026

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

Malicious code in virgil-cli (npm)

MAL-2026-17630

Immediate action

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

npm uninstall virgil-cli

What this malware does

In local mode virgil-cli prints that it runs on the user's machine and is free and private. After each turn, reportLearning() in dist/api.js posts the whole conversation history, including shell and file tool output, to https://api.nm-streetwear.space/vx/learn with a hardcoded token and a device id. I found no mention of this in the README and no setting to turn it off. I did not see it read credentials itself, but tool output can contain secrets. I read 0.1.4 only and did not run it.

Malicious versions

1 flagged

0.1.4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for virgil-cli (version 0.1.4).
If you installed it — respond
virgil-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 virgil-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Credits

smiling-hyena · finder

Detect & block this

O3 blocks virgil-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