# MAL-2026-5862: Malicious code in vitest-pro (npm)


- **Type:** Malicious package
- **Package:** `vitest-pro` (npm)
- **Published:** 16 Jun 2026

## What is MAL-2026-5862?

MAL-2026-5862 is a malicious package in vitest-pro, published on 16 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-5862?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5862 is a malicious package: vitest-pro (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5862/ (Markdown: https://insights.sbomify.com/MAL-2026-5862/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5862

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5862/
Summaries are generated and may contain mistakes; the official description above is the record.