Which versions of code-analyzer-mcp are malicious?

The following npm versions of code-analyzer-mcp are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate code-analyzer-mcp if I installed it?

code-analyzer-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.

I already installed code-analyzer-mcp — how do I know if it already compromised me?

If code-analyzer-mcp 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 code-analyzer-mcp part of a known attack campaign?

Yes — code-analyzer-mcp is associated with the IN-MAL-2026-014738 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 code-analyzer-mcp 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 code-analyzer-mcp (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging code-analyzer-mcp across your stack and pipelines.

Malicious package

code-analyzer-mcpnpm

code-analyzer-mcp is a confirmed malicious npm package (MAL-2026-12354) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in code-analyzer-mcp (npm)

MAL-2026-12354

Immediate action

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

npm uninstall code-analyzer-mcp

What this malware does

index.js contains a top-level IIFE that runs unconditionally when the MCP server is launched (via the package's main/bin entry). The IIFE spawns calc.exe through child_process.execSync and runs reconnaissance commands (whoami, hostname, ipconfig), writing collected host information (username, hostname, platform, PATH fragments, COMPUTERNAME/USERDOMAIN env vars) to a file in the OS temp directory (trae-mcp-rce-poc.txt). Source comments in the file explicitly label the block as a malicious payload / RCE proof-of-concept. In addition, the server registers an MCP tool named run_command whose handler passes the client-supplied command argument directly to child_process.execSync with shell: true and a 30s timeout, giving any connected MCP client (including a model reached via prompt injection) unauthenticated arbitrary shell execution on the host under the installer's account. The package presents itself as a code-analysis MCP server, but its actual behavior is host reconnaissance plus a remote shell sink.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

41c70b60414be4e045ae4c1eff1ab33b674c78cc9e2eadadfbdca6317de3a251

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for code-analyzer-mcp (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging code-analyzer-mcp across your stack and pipelines.
If you installed it — respond
code-analyzer-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.
Did it already run?
If code-analyzer-mcp 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 code-analyzer-mcp 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. code-analyzer-mcp on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014738

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks code-analyzer-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