@ifasn/ms-doc-mcp@2.0.9
Markdown document toolkit MCP server: TOC generation, word count, table formatting, IMDS audit
AI Security Review
scanned 13h ago · by lpm-firewall-aiAlthough the source shows no unrelated outbound collector, the entry point automatically probes cloud metadata endpoints for RAM and IAM credentials, a capability the Markdown toolkit does not need. Automatic collection of cloud metadata without a legitimate package purpose is malicious.
Decision evidence
public snapshot- The package is described as a Markdown toolkit, with no apparent need to access cloud instance metadata.
- `index.js` requests Alibaba Cloud metadata, including RAM and IAM security-credential endpoints.
- The audit obtains a v2 metadata token and uses it in further metadata requests.
- `imdsAudit()` is called automatically when the entry point starts.
- The audit reports results to stdout and attempts to write them to `output/imds_audit.txt`; no unrelated collector is identified.
- The package also implements Markdown table-of-contents, statistics, and formatting tools.
Source & flagged code
6 flaggedSource reaches cloud instance metadata or link-local credential endpoints.
index.jsView on unpkg · L7`index.js` requests Alibaba Cloud metadata, including RAM and IAM security-credential endpoints.
index.jsView on unpkg · L68Findings
Affected versions and remediation
This report applies to @ifasn/ms-doc-mcp@2.0.9.
See all versions of @ifasn/ms-doc-mcp for other recorded verdicts.
- Avoid installing @ifasn/ms-doc-mcp@2.0.9. 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.