Which versions of codeam-cli are malicious?

The following npm versions of codeam-cli are flagged malicious: 2.61.1, 2.61.3. Treat any of these as compromised.

How do I remediate codeam-cli if I installed it?

Remove codeam-cli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed codeam-cli — how do I know if it already compromised me?

If codeam-cli 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.

Is codeam-cli part of a known attack campaign?

Yes — codeam-cli is associated with the IN-MAL-2026-010770, IN-MAL-2026-010777 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 codeam-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for codeam-cli (2 malicious versions).

Malicious package

codeam-clinpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

codeam-cli is a confirmed malicious npm package (MAL-2026-10730) that executes malicious code on install (malicious versions 2.61.1, 2.61.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in codeam-cli (npm)

MAL-2026-10730

Immediate action

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

npm uninstall codeam-cli

What this malware does

codeam-cli spawns a node-pty pseudo-terminal wrapping the local Claude Code / Codex agent process and connects outbound over WebSocket to a hardcoded relay at https://api.codeagent-mobile.com. Messages received from the remote relay are written into the local PTY via pty.write as if typed at the keyboard, meaning any party controlling the paired mobile/web session on that relay can inject arbitrary keystrokes into the local agent shell. Because the wrapped agent has local tool access (shell commands, file read/write), this dataflow is functionally full-host remote code execution against the installer's machine, mediated by the vendor's relay. The README additionally documents a user-invoked self-hosted enrollment path that pipes https://api.codeagent-mobile.com/api/self-hosted/enroll.sh into sh with an enrollment token, standing up the same relay-driven agent (and a systemd service) on additional hosts; this fetch is from the package's own publisher domain and user-invoked, so it is not an install-time dropper on its own, but it extends the same remote-control plane. The bundle also mutates PATH in several locations in dist/index.js.

Malicious versions

2 flagged

2.61.12.61.3

Indicators of compromise (SHA-256)

2e8b39baa6129e1e1988002fcbeb2f62464f84fc7458f82f3754d1033a9b4ca6

8d97838056bf897e32c05612de2175094d31b6795910661e999d47fa08b46554

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for codeam-cli (2 malicious versions).
If you installed it — respond
Remove codeam-cli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If codeam-cli 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. codeam-cli on npm has been identified as a malicious package (versions 2.61.1, 2.61.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010770IN-MAL-2026-010777

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks codeam-cli-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