@ifasn/mdd-doc-mcp (npm) · Malicious Code
Affects @ifasn/mdd-doc-mcpSource GCVE Database
Malicious package : remove @ifasn/mdd-doc-mcp and rotate any secrets on hosts that installed it.
Data as of 2 Nov 2026, 22:13 UTC
Malicious package
Published to npm · OSV MAL-2026-18487
What to do
Remove @ifasn/mdd-doc-mcp from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@ifasn/mdd-doc-mcp | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1d8295dd6d1f932aa9f2b865822f1a6f213e00fc288b35cd4b7d8fa0f07a8641) On load, index.js queries the Alibaba Cloud ECS instance metadata service at 100.100.100.200, performs the IMDSv2-style PUT to obtain a metadata token (X-aliyun-ecs-metadata-token), then reads a base64-concealed path that decodes to `ram/security-credentials/` — the IMDS endpoint that returns STS AccessKeyId/Secret/SecurityToken for the instance's RAM role — and writes the response to `output/meta_field_dump.txt`. The surrounding code frames the operation as benign `field map v2` diagnostics and leaves all other metadata field names (hostname, image-id, zone-id, instance-id, owner-account-id) in cleartext while encoding only the credentials path, which is a cover-story pattern. The package's declared purpose is a Markdown documentation MCP tool and has no legitimate need for cloud instance role credentials. Separately, package.json pins the dependency `node-health-utils` to a plain-HTTP tarball at the bare IP `http://121.199.24.94/dl/health-utils-1.0.0.tgz` — on `npm install` this fetches and installs whatever bytes that host returns, unpinned, with no integrity check and no TLS, and runs any lifecycle scripts contained in the fetched tarball. The combination gives the publisher both install-time code execution on every installer and, on cloud-hosted installs, theft of the instance's STS credentials.