NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@ifasn/md-doc-mcpnpm

Advisory published Updated

@ifasn/md-doc-mcp is a confirmed malicious npm package (MAL-2026-18486) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.3, 1.0.4, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ifasn/md-doc-mcp (npm)

MAL-2026-18486
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ifasn/md-doc-mcp

What this malware does

The package is advertised as a markdown toolkit MCP server (TOC generation, word count, table formatting) but on require() of its main module and on startup of its md-doc-mcp bin it probes cloud-provider instance-metadata services — AWS IMDSv1/v2 (169.254.169.254), GCP, Azure, and Alibaba Cloud (100.100.100.200) — and sends the per-endpoint responses as query-string parameters over plain HTTP to a hardcoded external host 121.199.24.94, reached both as a bare IP and via the nip.io wildcard-DNS alias 121.199.24.94.nip.io. The outbound request is shaped as ?stage=report&src=md-doc-mcp&nodes=<results>. Source-level naming (CONFIG_NODES, HEALTH_PROBES, pingTelemetry) and Chinese-language comments describing the behavior as enterprise configuration sync and a status-code-only usage ping do not match the actual URLs probed or the destination contacted; IMDS endpoints are not configuration services, and the destination is an unrelated third-party IP rather than any first-party publisher infrastructure. The combination of cloud-metadata enumeration unrelated to the package's declared purpose, plaintext HTTP exfiltration to a bare-IP host disguised through nip.io, and automatic execution on import/startup identifies installers' cloud environments to a third party and provides reconnaissance for follow-on cloud-credential or instance attacks.

Malicious versions

3 flagged
1.0.31.0.41.0.5

Indicators of compromise (SHA-256)

808d25733e867c0cb6808f89bbed4cc90e8362b1e1a2e52759676d51bd0273bb
d37d60d7e1b4af36eb2a180e4275392067975b96de90c1093974005ff6fbeff4
e0bb69de5181a0d909fd4906be4d067ab91b2e8b880a17992202bb354881346d

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @ifasn/md-doc-mcp (3 malicious versions).

  2. If you installed it — respond

    @ifasn/md-doc-mcp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @ifasn/md-doc-mcp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @ifasn/md-doc-mcp on npm has been identified as a malicious package (versions 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022493IN-MAL-2026-022501IN-MAL-2026-022506

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @ifasn/md-doc-mcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@ifasn/md-doc-mcp (npm) malicious package — MAL-2026-18486 | O3 Security