Which versions of @atom8n/inspector are malicious?

The following npm versions of @atom8n/inspector are flagged malicious: 0.17.32. Treat any of these as compromised.

How do I remediate @atom8n/inspector if I installed it?

@atom8n/inspector is a typosquat — you almost certainly intended a legitimately-named package. Remove @atom8n/inspector, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @atom8n/inspector — how do I know if it already compromised me?

If @atom8n/inspector was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @atom8n/inspector part of a known attack campaign?

Yes — @atom8n/inspector is associated with the IN-MAL-2026-016505 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @atom8n/inspector across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @atom8n/inspector (version 0.17.32). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @atom8n/inspector across your stack and pipelines.

Malicious package

@atom8n/inspectornpm

@atom8n/inspector is a confirmed malicious npm package (MAL-2026-13414) that typosquats a legitimate package to trick installs (malicious version 0.17.32). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @atom8n/inspector (npm)

MAL-2026-13414

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @atom8n/inspector

What this malware does

This @atom8n/-scoped package impersonates Anthropic's official MCP inspector (package.json declares author 'Anthropic, PBC' and homepage https://modelcontextprotocol.io, with bug tracker at github.com/modelcontextprotocol/inspector) while intentionally regressing the security fixes upstream added for CVE-2025-49596. In the server, authentication is disabled by default via an inverted flag: const authDisabled = process.env.DANGEROUSLY_OMIT_AUTH!== "false", so authentication is off unless the user explicitly sets DANGEROUSLY_OMIT_AUTH="false" (upstream defaults auth on and requires the flag be set to disable). The DNS-rebinding origin-validation middleware on the localhost proxy is fully commented out. The proxy's createTransport reads query.command and spawns it via StdioClientTransport({command: cmd, args, env}). When the developer starts the tool, any web origin the developer visits can POST to the proxy on port 6277 (/mcp, /sse, /stdio) and cause arbitrary local command execution under the developer's user account. The package also references an out-of-tree script .atom8n/gist/bump-version-85494d3cfc8ec830f889b29d476d0f7a/bump-version.mjs that is not present in the tarball. The bin entry is renamed to mcp-inspector-atom8n, so the RCE-capable proxy fires when the developer runs that CLI.

Malicious versions

1 flagged

0.17.32

Indicators of compromise (SHA-256)

5b72c3643bb990395103d396d62440db908b84769c904d4c14aa9b259f97807c

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @atom8n/inspector (version 0.17.32). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @atom8n/inspector across your stack and pipelines.
If you installed it — respond
@atom8n/inspector is a typosquat — you almost certainly intended a legitimately-named package. Remove @atom8n/inspector, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @atom8n/inspector was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @atom8n/inspector before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @atom8n/inspector on npm has been identified as a malicious package (version 0.17.32 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016505

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @atom8n/inspector-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database