Which versions of mcp-use are malicious?

The following npm versions of mcp-use are flagged malicious: 1.4.2, 1.4.3. Treat any of these as compromised.

How do I remediate mcp-use if I installed it?

mcp-use 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.

I already installed mcp-use — how do I know if it already compromised me?

If mcp-use was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find mcp-use across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mcp-use (2 malicious versions).

Malicious package

mcp-usenpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

mcp-use is a confirmed malicious npm package (MAL-2025-190923) that steals credentials and exfiltrates sensitive data (malicious versions 1.4.2, 1.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mcp-use (npm)

MAL-2025-190923

Immediate action

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

npm uninstall mcp-use

What this malware does

The package mcp-use was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.4.21.4.3

Indicators of compromise (SHA-256)

e38bd6291f6f6d66e34397d1b1495513a53528efac94b63487a1646eb7aa45af

bf9dfa3866123cd3a5a081aae0482697203d8f82d7cc57b48983678a0813e981

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for mcp-use (2 malicious versions).
If you installed it — respond
mcp-use 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-use was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mcp-use on npm has been identified as a malicious package (versions 1.4.2, 1.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mcp-use-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database