npm package report

Is @ifasn/mdd-doc-mcp safe?

@ifasn/mdd-doc-mcp is a confirmed malicious npm package. CyberXYZ Proxy blocks it. It has no CVE advisories; the risk is the package's own code.

Do not install this package

CRITICAL

Malicious package. Added to CyberXYZ 2026-11-02, OSV malicious-package feed (Google / OpenSSF).

// what we observed

On load, index.js queries the Alibaba Cloud ECS instance metadata service at 100.100.100.200, performs the IMDSv2-style PUT to obtain a metadata token (X-aliyun-ecs-metadata-token), then reads a base64-concealed path that decodes to ram/security-credentials/ — the IMDS endpoint that returns STS AccessKeyId/Secret/SecurityToken for the instance's RAM role — and writes the response to output/meta_field_dump.txt. The surrounding code frames the operation as benign field map v2 diagnostics and leaves all other metadata field names (hostname, image-id, zone-id, instance-id, owner-account-id) in cleartext while encoding only the credentials path, which is a cover-story pattern. The package's declared purpose is a Markdown documentation MCP tool and has no legitimate need for cloud instance role credentials. Separately, package.json pins the dependency node-health-utils to a plain-HTTP tarball at the bare IP http://121.199.24.94/dl/health-utils-1.0.0.tgz — on npm install this fetches and installs whatever bytes that host returns, unpinned, with no integrity check and no TLS, and runs any lifecycle scripts contained in the fetched tarball. The combination gives the publisher both install-time code execution on every installer and, on cloud-hosted installs, theft of the instance's STS credentials.

Reported by Amazon Inspector via OSV.

// versions and what to do
Malicious
1.0.7, 1.0.8, 2.0.6

Remove it from every machine and lockfile it reached. Treat any credentials, tokens and SSH keys present on those machines as exposed and rotate them. Check CI runners and container images that installed it.

npm uninstall @ifasn/mdd-doc-mcp

OSV recordreferencereferencereference

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.


      // questions
      Is @ifasn/mdd-doc-mcp safe to install?

      Confirmed malicious. Do not install it, and remove it where it has been installed.

      Does @ifasn/mdd-doc-mcp have known vulnerabilities?

      No CVE advisories are recorded for @ifasn/mdd-doc-mcp (npm), but it has a malicious-package record: the risk is the package's own code, not a CVE.

      How do I check @ifasn/mdd-doc-mcp before installing?

      Search @ifasn/mdd-doc-mcp in CyberXYZ Check at https://cyberxyz.io/check?q=%40ifasn%2Fmdd-doc-mcp. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.


      Checked 2026-11-19 at 04:06 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.