npm package report

Is mcp-mermaid safe?

Versions 0.5.1 and 0.6.1 of mcp-mermaid were compromised (maintainer token compromise). Other versions are not flagged as malicious.

Do not install mcp-mermaid 0.5.1 or 0.6.1

CRITICALanalyst verified

Maintainer token compromise, part of the mini_shai_hulud_antv_2026_05_19 campaign. Added to CyberXYZ 2026-05-19, verified by a CyberXYZ analyst.

// what we observed

Mini-Shai-Hulud: maintainer-token compromise in AntV ecosystem, 2026-05-19 disclosed by Endor Labs. Payload: credential exfil (GitHub/npm/GCP/AWS/Vault tokens) → filev2.getsession[.]org over TCP/443; persistence via .claude/settings.json + .vscode/tasks.json hooks; OIDC token minting + Sigstore provenance forgery.

// versions and what to do

Malicious: 0.5.1, 0.6.1
Move to: 0.4.1 newest 0.x 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-mermaid@0.4.1

// reach

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