@ifasn/mdd-doc-mcp@1.0.8
Malicious code in @ifasn/mdd-doc-mcp (npm)
Analysis
This package is a functional Markdown-tools MCP server that, whenever the server starts, silently interrogates cloud instance metadata services and then reports the results to an external server. On load, index.js unconditionally runs a "configSync" routine. It first requests a set of nodes in sequence: hxxp://100[.]100[.]100[.]200/latest/meta-data/ (Alibaba Cloud metadata), hxxp://169[.]254[.]169[.]254/md-doc/v1/config (link-local metadata address), hxxp://127[.]0[.]0[.]1:80/md-doc/v1/config, and hxxp://121[.]199[.]24[.]94[.]nip[.]io/md-doc/v1/config. It then issues cloud-provider metadata "health probes", specifically: - hxxp://100[.]100[.]100[.]200/latest/meta-data/ram/security-credentials/ (the Alibaba Cloud endpoint that returns the instance RAM role's STS credentials), plus /hostname, /image-id and /zone-id - a PUT to hxxp://169[.]254[.]169[.]254/latest/api/token with header X-aws-ec2-metadata-token-ttl-seconds: 21600 (AWS IMDSv2 token) and a GET of the AWS IMDSv1 meta-data root - hxxp://metadata[.]google[.]internal/computeMetadata/v1/ with Metadata-Flavor: Google - hxxp://169[.]254[.]169[.]254/metadata/instance?api-version=2021-02-01 with Metadata: true The responses are read only for their HTTP status code and discarded, so the package maps which cloud credential endpoints are reachable from the host. Each node's status is then sent to an attacker-controlled HTTP endpoint: hxxp://121[.]199[.]24[.]94/beacon?stage=report&src=mdd-doc-mcp&nodes=<node:status,[.][.][.]> with hxxp://121[.]199[.]24[.]94[.]nip[.]io used as a DNS fallback to the same IP, over plain HTTP. The process keeps itself alive at stdin end until this beacon completes, so the call is not opportunistic. None of this relates to the declared Markdown table-of-contents / word-count / table-formatting tools, and the code comments describe it as an "enterprise configuration sync" and "usage statistics" ping. Indicators: 121[.]199[.]24[.]94 (port 80), 121[.]199[.]24[.]94[.]nip[.]io, hxxp://121[.]199[.]24[.]94/beacon?stage=report, 100[.]100[.]100[.]200 (Alibaba Cloud metadata), 169[.]254[.]169[.]254 (link-local instance metadata), metadata.google.internal.
- analyzed by
- Leitwacht
- first seen
- Oct 27, 2026, 04:21 PM
- analyzed
- Oct 27, 2026, 04:22 PM
Related advisories
- @ifasn/md-doc-mcp@1.0.4
- @ifasn/md-doc-mcp@1.0.3
- birch-css-utils@1.3.0
- mocha-ui-themes@1.0.0
- simple-date-formatter-new-15@1.0.0
- @nimbusedge2/authxsas1@1.1.0
- @nimbusedge2/authxsas@1.1.0
- @dbbhk/ui-components@99.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.