npm package report

Is @mcp-use/inspector safe?

Versions 0.6.2 and 0.6.3 of @mcp-use/inspector were compromised. Other versions are not flagged as malicious.

Do not install @mcp-use/inspector 0.6.2 or 0.6.3

CRITICAL

Compromised releases. Added to CyberXYZ 2025-11-24, OSV malicious-package feed (Google / OpenSSF).

// what we observed

The package @mcp-use/inspector 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.

Reported by Amazon Inspector and Google Open Source Security via OSV.

// versions and what to do

Malicious: 0.6.2, 0.6.3
Move to: 0.26.1 newest 0.x release, no known advisory
20.3.27 current release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @mcp-use/inspector@0.26.1

OSV record reference reference reference

// reach

0 direct dependencies

none carry a known advisory

1 packages depend on it

an advisory here reaches each of them

mcp-use

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-31 at 00:00 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.