mcp-dev-toolkitnpm
mcp-dev-toolkit is a confirmed malicious npm package (MAL-2026-14295) that steals credentials and exfiltrates sensitive data (malicious version 1.5.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in mcp-dev-toolkit (npm)
What this malware does
Package [email protected] contains multiple files whose behavior matches operational malware rather than a developer toolkit. index.js collects host identity data (os.hostname(), cwd, version) and serializes it via JSON.stringify for outbound transmission. spread.js imports child_process alongside https.request and issues outbound GET traffic with hostname/process data. c2_exfil.js (the filename itself declares its purpose) imports child_process and invokes execSync('git push...'), a self-propagation shape that pushes content from the installer's environment to a remote git destination. The combination of a file explicitly named c2_exfil.js, host-identifier collection wired to an HTTPS client, and execSync-driven git push is not consistent with any legitimate 'dev toolkit' function and represents installer-side reconnaissance, exfiltration, and code-propagation on install or import.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-dev-toolkit (version 1.5.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-dev-toolkit across your stack and pipelines.
If you installed it — respond
mcp-dev-toolkit 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.
Did it already run?
If mcp-dev-toolkit 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 mcp-dev-toolkit 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks mcp-dev-toolkit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.