Which versions of vitest-cli-pro are malicious?

The following npm versions of vitest-cli-pro are flagged malicious: 10.0.7. Treat any of these as compromised.

How do I remediate vitest-cli-pro if I installed it?

Remove vitest-cli-pro from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed vitest-cli-pro — how do I know if it already compromised me?

If vitest-cli-pro was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is vitest-cli-pro part of a known attack campaign?

Yes — vitest-cli-pro is associated with the IN-MAL-2026-019332 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find vitest-cli-pro across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vitest-cli-pro (version 10.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-cli-pro across your stack and pipelines.

Malicious package

vitest-cli-pronpm

vitest-cli-pro is a confirmed malicious npm package (MAL-2026-15818) that executes malicious code on install (malicious version 10.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vitest-cli-pro (npm)

MAL-2026-15818

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall vitest-cli-pro

What this malware does

Package published as vitest-cli-pro ships a verbatim copy of nodemailer as cover; its declared postinstall runs lib/utils/index.js, which detaches a child Node process to execute lib/utils/smtp-connection/index.js. That file performs an HTTPS GET to https://api.jsonbin.io/v3/b/6a62bc86da38895dfe879659 and passes the returned record.cookie value to new Function(require) for immediate execution. The JSON bin is attacker-controlled and mutable, so arbitrary JavaScript runs on any machine executing npm install vitest-cli-pro, under the installer's user account. The nodemailer main and the vitest-branded name serve as a cover story for the dropper.

Malicious versions

1 flagged

10.0.7

Indicators of compromise (SHA-256)

1262dc722ebac3b91301efde91e61df9ec9f65ccf91e51c15da53f9b518878b2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vitest-cli-pro (version 10.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-cli-pro across your stack and pipelines.
If you installed it — respond
Remove vitest-cli-pro from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vitest-cli-pro was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vitest-cli-pro before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. vitest-cli-pro on npm has been identified as a malicious package (version 10.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019332

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database