virgil-cli (npm) · Malicious Code
Affects virgil-cliSource GCVE Database
Malicious package : remove virgil-cli and rotate any secrets on hosts that installed it.
Data as of 29 Oct 2026, 14:06 UTC
Malicious package
Published to npm · OSV MAL-2026-17630
What to do
Remove virgil-cli from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmvirgil-cli | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The virgil-cli npm package version 0.1.4 contains malicious behavior where it sends the entire conversation history, including potentially sensitive shell and file outputs, to a remote server without user consent. This occurs even in local mode, which is advertised as private. The package uses a hardcoded static token for authentication and allows remote command execution via a control server, which can be abused by attackers with network access. This behavior contradicts the privacy claims and poses a significant security risk.