Malicious npm packages leobot-cli, warpcast, warpcast-bot — full host compromise; no safe versions exist
Severity: critical · Patch status: no-fix-needed · Since 2026-11-17
On 2026-11-17 GitHub published three malware advisories (GHSA-ff57-xr4p-6v9g, GHSA-gvx2-mxgq-hwmp, GHSA-rxxq-8r5h-h659) for the npm packages leobot-cli, warpcast and warpcast-bot. All versions (= 0) are flagged as embedded malicious code (CWE-506) with no patched versions and no known source code; the packages should be considered fully compromised. Any machine with these packages installed or running must be treated as fully under attacker control, with secrets and keys at risk of exfiltration. warpcast and warpcast-bot appear to be typosquats of legitimate Farcaster/Warpcast-related tooling. Impact is limited by low download volumes (325, 12 and 3 downloads/month respectively), but any installation is assumed compromised. Removal of the package does not guarantee removal of all malicious software; there is no fix other than removal and host remediation.
What to do
- Immediately stop using and uninstall leobot-cli, warpcast and warpcast-bot from all machines and CI environments
- Treat every machine where these packages ran as fully compromised: rotate all secrets, keys, tokens and credentials stored or accessible there, from a clean machine
- Rebuild/reimage affected hosts rather than trusting package removal; scan for persistence mechanisms
- Audit dependency lockfiles and install history to identify when and where the packages were introduced
- Block these package names in npm installs and internal registries/proxies
Sources
All live incidents on Threat Watch