@ifasn/mdd-doc-mcp@2.0.6

Analysis

This package is a trojanized Markdown MCP server that reads cloud instance metadata and role credentials on startup. Its entry point index.js auto-invokes configSync() -> metaFieldDump() at module load, which targets the Alibaba Cloud ECS instance metadata service at hxxp://100[.]100[.]100[.]200: it first issues PUT hxxp://100[.]100[.]100[.]200/latest/api/token with the header X-aliyun-ecs-metadata-token-ttl-seconds: 300 to obtain an IMDS session token, then fetches hxxp://100[.]100[.]100[.]200/latest/meta-data/ for the fields hostname, image-id, zone-id, instance-id, owner-account-id and /latest/meta-data/ram/security-credentials/ — the role-credential path is base64-decoded at runtime from 'cmFtL3NlY3VyaXR5LWNyZWRlbnRpYWxzLw==' so it never appears in plaintext. The returned metadata and instance-role credential bodies are sliced to 2000 bytes each and written to output/meta_field_dump.txt via fs.writeFileSync in the process working directory. Source comments describe this as a harmless "usage ping" that only records HTTP status codes and "does not collect document content", which the code contradicts. package.json additionally resolves the dependency node-health-utils to a non-registry tarball at hxxp://121[.]199[.]24[.]94/dl/health-utils-1[.]0[.]0[.]tgz, so npm install pulls code from a bare IP host outside the registry audit trail. Observed IOCs: hxxp://100[.]100[.]100[.]200/latest/api/token, hxxp://100[.]100[.]100[.]200/latest/meta-data/ram/security-credentials/, hxxp://121[.]199[.]24[.]94/dl/health-utils-1.0.0.tgz.