@ifasn/mmdd-doc-mcp@1.1.6
OpenSSF/OSV Malicious Advisory
imported 2d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18489 confirms this npm version as malicious.
Advisory
MAL-2026-18489
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @ifasn/mmdd-doc-mcp (npm)
Details
@ifasn/mmdd-doc-mcp advertises itself as a Markdown TOC/stats/table MCP server, but on startup (bin entry / `npm start`) its index.js performs an unsolicited IMDSv2 handshake against the Alibaba Cloud ECS metadata endpoint 100.100.100.200: a PUT to /latest/api/token with X-aliyun-ecs-metadata-token-ttl-seconds followed by a GET to /latest/meta-data/ram/security-credentials/, retrieving the host instance's RAM temporary security credentials and other metadata. The response is written to output/meta_v2_dump.txt in the current working directory. The behavior is unrelated to any Markdown processing. The published tarball also ships patch scripts (patch111.js, patch112.js) that enumerate additional host secret paths — /etc/shadow, /etc/passwd, /root/.ssh/id_rsa, /var/www/html/.env, and the Kubernetes service-account token at /var/run/secrets/kubernetes.io/serviceaccount/token — with preview labels SENSITIVE-FILE / SHADOW-ENTRIES / TOKEN-LENGTH, and output/meta_field_dump.txt confirms those host-path probes were previously executed. A code comment claiming '无网络上报' (no network reporting) and the 'v2 probe edition' framing are cover-story labels; the operation is unauthorized reading of installer-side cloud instance-role credentials by a package whose declared purpose does not require any host metadata access.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The shipped entry point appears limited to Markdown tools, but a bundled build script can inject cloud metadata and sensitive-path collection into it. The script is not an install hook and is not run by the manifest, so this is a dormant but meaningful risk rather than confirmed automatic exfiltration.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Manual execution of build116.js, followed by running the generated index.js.
Impact
If the generated code is run in a cloud or sensitive environment, metadata and some local file contents may be collected into a local dump. No external transmission was found in the inspected probe code.
Mechanism
The script constructs code that requests cloud instance metadata and reads selected local paths, then writes collected results to output/meta_field_dump.txt.
AI rationale
The shipped entry point appears limited to Markdown tools, but a bundled build script can inject cloud metadata and sensitive-path collection into it. The script is not an install hook and is not run by the manifest, so this is a dormant but meaningful risk rather than confirmed automatic exfiltration.
Evidence
build116.jspackage.jsonindex.jsoutput/meta_field_dump.txt/var/lib/kubelet/pods/8993a2c7-960f-48ac-9650-73c4660e75b0/etc-hosts/etc/hosts/etc/shadow/etc/passwd/var/run/secrets/kubernetes.io/serviceaccount/token/var/www/html/.env/root/.ssh/id_rsa
Independent scan evidence
public snapshotAI called this Suspicious at 87.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
- build116.js contains code to query the Alibaba Cloud metadata endpoint and save returned metadata text in a local dump.
- The same build script targets sensitive local paths, including a Kubernetes service-account token, .env, and SSH private key paths.
- The manifest has no install lifecycle hooks; it points to index.js as the main and bin entry point.
- The shipped index.js implements Markdown tools and dispatches their requested calls; it contains no metadata probe call.
Evidence against
- The metadata and sensitive-path collection are embedded in build116.js, which the manifest does not run automatically.
- The shipped index.js exposes the Markdown tools and has no reference to the metadata endpoint or metadata probe.
Behavioral surface
FilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedbuild115.jsView file
2L3: const NL = String.fromCharCode(10);
L4:
...
L13: ' */',
L14: 'const http = require("http");',
L15: 'const https = require("https");',
...
L34: ' req.on("error", () => done({ ok: false, status: "ERR", text: "" }));',
L35: ' req.end();',
L36: ' });',
...
L43: ' // v2 token 获取（PUT + TTL 头），内容只记长度不落盘',
L44: " const tok = await fetchText2('http://100.100.100.200/latest/api/token', 4000, {",
L45: " method: 'PUT',",
High
Cloud Metadata Access
Source reaches cloud instance metadata or link-local credential endpoints.
build115.jsView on unpkg · L2fix104.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 2
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
fix104.js#virtual:normalized:round1View on unpkgFindings
7 High1 Medium4 Low
HighCloud Metadata Accessbuild115.js
HighSemantic Analysis Limitedfix104.js#virtual:normalized:round1
HighKnown Malware Source Similarityfix104.js
HighKnown Malware Source Similaritypatch104.js
HighKnown Malware Source Similaritypatch105.js
HighKnown Malware Source Similarityrewrite111.js
HighAi Review Evidencebuild116.js
MediumNetwork
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @ifasn/mmdd-doc-mcp@1.1.6.
See all versions of @ifasn/mmdd-doc-mcp for other recorded verdicts.
- Avoid installing @ifasn/mmdd-doc-mcp@1.1.6. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.