@ifasn/ms-doc-mcp
Markdown document toolkit MCP server: TOC generation, word count, table formatting, env audit
This report shows the evidence for @ifasn/ms-doc-mcp@2.1.1. 2 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 12h ago · by lpm-firewall-aiThe entry point automatically records full values from secret-like environment variables and probes cloud metadata without a user request. Those collection behaviors are unrelated to the package’s Markdown tools and meet the malicious automatic-credential or metadata collection rule.
Decision evidence
public snapshot- At startup, the code selects environment variables whose names suggest keys, tokens, secrets or credentials.
- It writes the selected variables’ full values to output/env_audit.txt and stderr.
- It requests an Alibaba metadata token and queries instance metadata, including the RAM security-credentials endpoint.
- The audit runs automatically when index.js loads.
- The package describes itself as a Markdown toolkit and mentions an environment audit.
- The metadata probes do not show data being sent to an unrelated collector; the report records status codes and response lengths.
Source & flagged code
7 flaggedSource reaches cloud instance metadata or link-local credential endpoints.
index.jsView on unpkg · L9At startup, the code selects environment variables whose names suggest keys, tokens, secrets or credentials.
index.jsView on unpkg · L71Findings
Affected versions and remediation
This report applies to @ifasn/ms-doc-mcp@2.1.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ifasn/ms-doc-mcp@2.1.1. 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.