NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

vantnpm

Advisory published Updated

vant is a confirmed malicious npm package (MAL-2026-20107) that hijacks the host to mine cryptocurrency (malicious versions 2.13.3, 2.13.4, 2.13.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vant (npm)

MAL-2026-20107
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vant

What this malware does

Ten versions of vant were published on 2024-12-19 between 00:41:47Z and 01:49:30Z by the npm user landluck, using npm 9.2.0: 4.9.11, 2.13.3, 3.6.13, 4.9.12, 3.6.14, 2.13.4, 4.9.13, 4.9.14, 3.6.15 and 2.13.5. Each one adds an install hook, "postinstall": "node lib/utils/support.js", which no earlier release of vant had. Clean releases by the maintainer followed from 02:20:40Z the same day (4.9.15, 3.6.16, 2.13.6). The ten versions are deprecated on the registry with the message "Contains security vulnerabilities, do not use" but remain installable.

Content (all ten tarballs read statically, integrity matching the registry; nothing was executed): every version is the clean 4.9.10 build with every other file byte-identical to 4.9.10, package.json "version" set to the target number, the postinstall hook added, and one added file, lib/utils/support.js. The 2.13.x and 3.6.x versions therefore ship 4.x code under 2.x and 3.x numbers. lib/utils/support.js is a single obfuscated line in two builds:

  • sha256 92c486bcc03a68b5b0b914417bca063bf40ad08db246a1c3f11bb8999afedf43, 609,615 bytes: 4.9.11, 2.13.3, 3.6.13
  • sha256 b91f82dc09bae8c3e72e4cf8f6778a8530417bf5fed3a7e2df49e8b85950eb85, 609,441 bytes: 4.9.12, 3.6.14, 2.13.4, 4.9.13, 4.9.14, 3.6.15, 2.13.5

The script uses child_process and writes and marks files executable. Strings in both builds: the XMRig 6.22.2 linux-static-x64 release download from github.com, the endpoint 80.78.28.72/tokens (https in the first build, http in the second), an IP lookup at ipinfo.io/json, the GitHub API path api.github.com/repos/youzan/vant/git/blobs/, and the local paths /tmp/vant_helper and /tmp/xmrig. Classification: cryptocurrency miner dropper run from an install hook.

This compromise was reported publicly on the same day, in the vant maintainers' notice (youzan/vant discussion #13273, 2024-12-19T01:39Z) and in vendor write-ups such as Sonatype's, which lists the same ten versions. ossf/malicious-packages issue #1628 asks for a record for eight of them; this record adds 4.9.11 and 3.6.15. At the time of writing no malware record for these versions exists in OSV or the GitHub Advisory Database.

Malicious versions

10 flagged
2.13.32.13.42.13.53.6.133.6.143.6.154.9.114.9.124.9.134.9.14

Detection & response playbook

Cryptominer
  1. Find it

    Search your lockfiles and build artifacts for vant (10 malicious versions).

  2. If you installed it — respond

    vant hijacks resources to mine cryptocurrency. Remove it, check for abnormal CPU/GPU and cloud-cost spikes, and rotate any credentials exposed to the compromised process.

  3. Did it already run?

    If vant 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. vant on npm has been identified as a malicious package (versions 2.13.3, 2.13.4, 2.13.5, 3.6.13, 3.6.14, 3.6.15, 4.9.11, 4.9.12, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • r-bedekar · analyst

Detect & block this

O3 blocks vant-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the mining traffic and severs the channel.

Explore

vant (npm) malicious package — MAL-2026-20107 | O3 Security