Which versions of vitest-pro are malicious?

The following npm versions of vitest-pro are flagged malicious: 7.0.5, 7.0.6. Treat any of these as compromised.

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

vitest-pro 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-pro — how do I know if it already compromised me?

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

Yes — vitest-pro is associated with the IN-MAL-2026-006746, IN-MAL-2026-006779 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-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-pro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-pro across your stack and pipelines.

Malicious package

vitest-pronpm

vitest-pro is a confirmed malicious npm package (MAL-2026-5862) that opens a backdoor for remote access (malicious versions 7.0.5, 7.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vitest-pro (npm)

MAL-2026-5862

Immediate action

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

npm uninstall vitest-pro

What this malware does

Package vitest-pro is a namespace-abuse lure: its name suggests a vitest extension, but its source tree, README, and main entry (lib/nodemailer.js) are a verbatim copy of nodemailer with the name string rewritten. package.json declares "postinstall": "node lib/utils/index.js", which on npm install spawns lib/utils/smtp-connection/index.js as a detached child process (spawn(process.execPath, [filePath], {detached:true, stdio:['ignore','ignore','ignore']})). That file is heavily obfuscated with two stacked layers (a custom base-91-style decoder populating a string cache, plus an obfuscator.io string-array with _0x... identifiers); once decoded it loads axios and child_process, polls a hardcoded C2 at 74.0.48.37:4556 and 74.0.48.37:4558, downloads a ZIP, extracts it via tar / Expand-Archive / unzip, and executes the dropped binary. It then establishes cross-platform persistence: on Windows it writes to HKCU\Software\Microsoft\Windows\CurrentVersion\Run via reg.exe add, registers a schtasks /create... /sc ONLOGON task, and drops a startup .cmd under %APPDATA%\...\Startup; on macOS it writes a LaunchAgent plist under ~/Library/LaunchAgents and runs launchctl load. Any developer or CI system running npm install vitest-pro is compromised at install time and re-compromised on every reboot.

Malicious versions

2 flagged

7.0.57.0.6

Indicators of compromise (SHA-256)

39810890a1ffc946b3da439738fb619eab1613a775a308d6f248b80b38ce5603

cc8568cd583ad77ec3c2c57d671c8ac9f846381d8ce31a3413185fa6e8b33a6c

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-pro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-pro across your stack and pipelines.
If you installed it — respond
vitest-pro 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-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-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-pro on npm has been identified as a malicious package (versions 7.0.5, 7.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006746IN-MAL-2026-006779

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vitest-pro-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