@ifasn/mmdd-doc-mcp@1.0.2
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe Markdown server automatically reads cloud instance identifiers at startup and writes successful responses into its working directory, an unnecessary behavior for its advertised tools. I found no evidence that it sends those values elsewhere, so this is a warning rather than a confirmed attack.
Decision evidence
public snapshot- The package is described as a Markdown document toolkit, with `index.js` as its main entry point.
- At startup, the entry point automatically requests cloud metadata fields including hostname, instance ID and owner account ID.
- Successful metadata responses are written to `output/meta_field_dump.txt`.
- The metadata request uses GET; the inspected source does not send the collected values to another host.
- The package’s advertised Markdown tools perform TOC generation, text statistics and table formatting.
- The inspected metadata flow has no apparent credential collection or outbound transfer of the response values.
Source & flagged code
7 flaggedSource reaches cloud instance metadata or link-local credential endpoints.
index.jsView on unpkg · L10At startup, the entry point automatically requests cloud metadata fields including hostname, instance ID and owner account ID.
index.jsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @ifasn/mmdd-doc-mcp@1.0.2.
See all versions of @ifasn/mmdd-doc-mcp for other recorded verdicts.
- Review the evidence and your use of @ifasn/mmdd-doc-mcp@1.0.2 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.