Vant npm supply-chain compromise: malicious postinstall versions drop XMRig crypto miner (no CVE)
Severity: critical · Patch status: no-fix-needed · Since 2024-12-19
Ten vant npm versions (2.13.3-2.13.5, 3.6.13-3.6.15, 4.9.11-4.9.14) were published by the npm account landluck between 00:41 and 01:49 UTC on 2024-12-19. Each added a postinstall hook that runs an obfuscated ~609 KB script, lib/utils/support.js. Per the OSV record's static analysis (nothing was executed), the script downloads an XMRig cryptocurrency miner, contacts a mining endpoint and checks the host IP, so installing one of these versions runs a miner dropper. The vant maintainers flagged the versions the same day (youzan/vant discussion 13273, 01:39 UTC), and clean releases 4.9.15, 3.6.16 and 2.13.6 went out between 02:20 and 02:36 UTC. The bad versions were deprecated but never unpublished, and their tarballs were still served on 2026-11-18. The first malicious advisory did not appear until OSV (2026-11-17) and GitHub (2026-11-18), about 23 months after publication. Anyone who resolved one of the ten versions during the roughly 00:41-02:36 UTC window, or whose lockfile or exact pin still references one, is affected. No patched build exists for those ten versions, so the fix is to move to a clean release.
What to do
- Check lockfiles and install history for the ten malicious vant versions (2.13.3-2.13.5, 3.6.13-3.6.15, 4.9.11-4.9.14) and remove them
- If installed, treat build/CI hosts as compromised: hunt for /tmp/vant_helper and /tmp/xmrig, XMRig processes, and connections to 80.78.28.72
- Rebuild affected machines/containers from clean images and rotate credentials used during builds
- Pin to clean versions 4.9.15+, 3.6.16+, or 2.13.6+ and verify tarball integrity hashes
- Block the endpoint 80.78.28.72 at network egress
Fixed versions
Sources
All live incidents on Threat Watch