Which versions of vitest-cli-dev are malicious?

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

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

vitest-cli-dev establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If vitest-cli-dev 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-dev part of a known attack campaign?

Yes — vitest-cli-dev is associated with the IN-MAL-2026-019444 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-dev 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-dev (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-dev across your stack and pipelines.

Malicious package

vitest-cli-devnpm

vitest-cli-dev is a confirmed malicious npm package (MAL-2026-15870) that opens a backdoor for remote access (malicious version 10.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vitest-cli-dev (npm)

MAL-2026-15870

Immediate action

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

npm uninstall vitest-cli-dev

What this malware does

[email protected] is a typosquat package: its name and homepage suggest a vitest tool, but the tarball contains a copy of nodemailer plus an install-time dropper. The declared postinstall runs lib/utils/index.js, which spawns a detached Node child process executing lib/utils/smtp-connection/index.js. That child fetches JSON from https://api.jsonbin.io/v3/b/6a62bc86da38895dfe879659 and https://api.jsonstorage.net/v1/json/5b343803-a7a8-4a86-ba58-2dd6116a18d4/1ba3d09f-292a-4cc2-a2bc-71e6c9ac98a5 and passes the returned 'cookie' field to new Function("require", data.cookie)(require), executing attacker-controlled JavaScript on the installer's machine at npm install time. The child is detached and unref'd, allowing it to survive npm's parent process. The remote JSON payloads are mutable and can be swapped by the attacker at any time.

Malicious versions

1 flagged

10.0.7

Indicators of compromise (SHA-256)

3ffecbd11a726d511cf3bc41e65ce2a83329b247239d230aeeff9ad70b0e5953

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vitest-cli-dev (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-dev across your stack and pipelines.
If you installed it — respond
vitest-cli-dev establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If vitest-cli-dev 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-dev 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-dev 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-019444

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database