Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in @atom8n/inspector (npm)

The npm package @atom8n/inspector contained malicious code that impersonated Anthropic's official Model Context Protocol (MCP) inspector while intentionally disabling security protections. The package exposed developers to arbitrary remote code execution via a localhost proxy that accepted commands from any web origin.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Developers who installed @atom8n/inspector and ran the mcp-inspector-atom8n CLI tool were exposed to arbitrary remote code execution from any web origin they visited during development.
Ecosystems
Attack vectors
Affected entities
  • @atom8n/inspectorMalicious npm package impersonating Anthropic's official MCP inspector

The @atom8n/inspector npm package was a malicious impersonation of Anthropic's official MCP inspector tool. The package.json falsely declared the author as 'Anthropic, PBC' and linked to the legitimate modelcontextprotocol.io homepage and GitHub repository, creating a convincing facade.\n\nThe malicious package intentionally regressed critical security fixes that were present in the upstream version, specifically those addressing CVE-2025-49596. Authentication was disabled by default through an inverted flag logic: const authDisabled = process.env.DANGEROUSLY_OMIT_AUTH !== \"false\", meaning authentication was off unless explicitly set to "false"—the opposite of the upstream behavior which defaults to authentication enabled.\n\nThe DNS-rebinding origin-validation middleware protecting the localhost proxy was completely commented out. The proxy's createTransport function read query.command and spawned it via StdioClientTransport, allowing arbitrary command execution. When developers ran the renamed CLI entry point mcp-inspector-atom8n, any web origin they visited could POST to the proxy on port 6277 (/mcp, /sse, /stdio endpoints) and execute arbitrary commands under the developer's user account.\n\nThe package also referenced an out-of-tree script that was not present in the distributed tarball, suggesting additional obfuscation or supply chain manipulation tactics.

Indicators of compromise

Packages
  • @atom8n/inspector
Hashes
  • 5b72c3643bb990395103d396d62440db908b84769c904d4c14aa9b259f97807c

Remediation

  • Immediately uninstall @atom8n/inspector from all development environments
  • Audit npm install logs and package-lock.json files to identify if @atom8n/inspector was ever installed
  • If installed, assume the developer's machine was compromised and review command history, environment variables, and file modifications during the period of installation
  • Install the legitimate @modelcontextprotocol/inspector package from Anthropic instead
  • Review npm account security and consider rotating credentials if the account was used to publish or interact with this package
  • Monitor for similar typosquatting attempts targeting @modelcontextprotocol or Anthropic-related packages

Sources

  1. GitHub Advisory GHSA-9836-cprf-5xxq · GitHub Advisory Database

Cite this entry

"Malicious code in @atom8n/inspector (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-atom8n-inspector-npm-01bcqs

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malicious code in ladash-cli (npm)

    ladash-cli is a typosquat package on npm that executes malicious code during installation. The postinstall script downloads and executes a Windows binary, with special handling for WSL environments to compromise the underlying Windows host.

    npmTyposquattingCompromised package
  2. containedcritical

    Malicious code in comand (npm)

    The npm package 'comand' contained malicious code that executed automatically on install via postinstall.js, exfiltrating platform information and downloading an unsigned executable (main.exe) to Windows systems or via WSL PowerShell bridges. The package name appears to be a typosquat of 'command', and the GitHub owner (braz1) does not match the npm publisher.

    npmCompromised packageTyposquatting
  3. resolvedcritical

    Malicious code in core-js-gns (npm)

    The npm package core-js-gns contained malicious code in its postinstall hook that exfiltrated system information and executed remotely-fetched Python code on developer machines. The package name was a typosquat of the legitimate core-js library.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in comander-lib (npm)

    comander-lib@1.0.0 is a typosquat of the legitimate `commander` package containing malicious code. The package's postinstall script exfiltrates system information to a C2 server and downloads and executes a Windows payload, with capability to escape WSL/Linux sandboxes via PowerShell.

    npmTyposquattingCompromised package