Loading npm security reports…

virgil-cli@0.1.4: Malicious npm security report (Block) | LPM Firewall

LPM Firewall

Threat feed How it works Policy

Blocked & quarantined

Quarantined by product-default policy — this version is not allowed through the firewall.

View on npm All versions

registry / virgil-cli / 0.1.4

virgil-cli@0.1.4

Virgil in your terminal — an AI agent that does real work on your machine. No account, no store, one command.

OSV Malicious Advisory

imported 3d ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-17630 confirms this npm version as malicious. 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...

Advisory

MAL-2026-17630

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in virgil-cli (npm)

Details

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.

Decision reason

OpenSSF Malicious Packages via OSV confirms virgil-cli@0.1.4 as malicious (MAL-2026-17630): Malicious code in virgil-cli (npm)

References

OSV advisory

Source & flagged code

0 flagged

No flagged code excerpts are attached to this scan.

Source & flagged code

0 flagged · loading source

No flagged code excerpts are attached to this scan.

Findings

LPM Firewall

Stop threats before they install.

Firewall

Threat feed
How it works
Policy

LPM

1 High

HighOsv Malicious Advisory

Affected versions and remediation

This report applies to virgil-cli@0.1.4.

See version security history for other recorded verdicts.

Avoid installing virgil-cli@0.1.4. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-10-05 23:15:04.941Z (UTC).

Source advisory published: 2026-10-03 22:47:45.000Z (UTC).

This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.

—%Advisory

External advisory

TypeMalware

Firewall policyMatched malicious

Trusted malware advisory MAL-2026-17630 identifies this version as malicious. Firewall keeps the version blocked under its trusted-intelligence policy. An AI recommendation to allow or warn does not override that advisory.

Package metadata

npm

Maintainersvirgilbynm

Version0.1.4

Latest on npm0.1.8

PublishedOct 2, 2026

LicenseMIT

Dependencies1

Keywordsaiagentcliterminalvirgilassistant

Runtime surface

package.json

Entrypointsbin → virgil

Runtimenode >=18

Artifact85.6 KB · 24 files2 signature(s)

Install lifecycleprepublishOnly

LPM.dev Registry

LPM CLI

LPM Vault

Source & flagged code

0 flagged

No flagged code excerpts are attached to this scan.