npm package report

Is mcp-use safe?

Confirmed malicious. Do not install it, and remove it where it has been installed.

Do not install this package

CRITICAL

Confirmed malicious. Confirmed 2025-11-24, OSV malicious-package feed (Google / OpenSSF).

// what we observed

--- -= Per source details. Do not edit below this line.=- Source: amazon-inspector (e38bd6291f6f6d66e34397d1b1495513a53528efac94b63487a1646eb7aa45af) The package mcp-use was found to contain malicious code. Source: google-open-source-security (bf9dfa3866123cd3a5a081aae0482697203d8f82d7cc57b48983678a0813e981) 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.

// versions and what to do

Malicious: 1.4.2, 1.4.3
Clean: none confirmed

Remove it from every machine and lockfile it reached. Treat any credentials, tokens and SSH keys present on those machines as exposed and rotate them. Check CI runners and container images that installed it.

npm uninstall mcp-use

OSV record reference reference reference

// reach

9 direct dependencies

4 carry known advisories, worst HIGH

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-10-21 at 00:18 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.