Evidence · DiggingBeagle record
GitHub malware advisory: mnm-doc-mcp remote tarball dependency
OpenSSF/Amazon Inspector finding on malicious MCP npm package 1.0.0 with unpinned insecure off-registry tarball dependency.
- Published
- Nov 12, 2026
- Source role
- primary disclosure
Evidence record
OpenSSF/Amazon Inspector finding on malicious MCP npm package 1.0.0 with unpinned insecure off-registry tarball dependency.
Claim-level citations (2)
- supportsA malicious MCP package delegated install-time authority to a mutable off-registry tarball: The published npm package @rfewqa-fes/mnm-doc-mcp version 1.0.0 presented an inert MCP entry module while declaring node-health-utils as a tarball dependency hosted at an unpinned plain-HTTP address outside the npm registry. Anyone controlling the endpoint or intervening in its transport could replace the dependency bytes that npm installs. The direct installer execution boundary is npm fetching and unpacking the remote dependency and potentially running its lifecycle scripts, before an agent ever invokes a tool. A package name and safe-looking index.js do not attest all imported dependency code.
GitHub Advisory GHSA-3qjp-mvhh-w85g, package 1.0.0, unpinned HTTP tarball dependency and risk assessment
- supportsA malicious MCP package delegated install-time authority to a mutable off-registry tarball: GitHub and OpenSSF classify the package as malicious; the inspected advisory does not provide a preserved payload, observed installation trace, affected host count or confirmed exfiltration. A capability to execute a changed tarball is not proof which malicious code was actually served at each time. This is a plugin supply-chain attack path rather than a model prompt-injection episode; it targets developer systems installing AI-facing tool extensions.
Primary disclosure: results, scope and limitations