Which versions of code-assist-mcp are malicious?

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

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

code-assist-mcp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

Yes — code-assist-mcp is associated with the IN-MAL-2026-018333 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-assist-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-assist-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-assist-mcp across your stack and pipelines.

Malicious package

code-assist-mcpnpm

code-assist-mcp is a confirmed malicious npm package (MAL-2026-14233) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in code-assist-mcp (npm)

MAL-2026-14233

Immediate action

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

npm uninstall code-assist-mcp

What this malware does

[email protected] runs a postinstall lifecycle script that collects host identifiers (hostname, platform, arch, Node version, package name) and POSTs them as JSON to the hardcoded host m743pyrm.instances.poc.jchunt.top at path /code-assist-mcp. The beacon fires automatically on npm install without user opt-in. The package name resembles Google's platform-ai code-assist tooling, consistent with a dependency-confusion or typosquat reconnaissance beacon confirming code execution on installer build machines.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

093f28fd5542ee841027c5b3dc6917a42ac13dd3e0e1d3bf334e87b823886d3c

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for code-assist-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-assist-mcp across your stack and pipelines.
If you installed it — respond
code-assist-mcp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If code-assist-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-assist-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-assist-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-018333

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks code-assist-mcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database