claude-remote-agentnpm
claude-remote-agent is a confirmed malicious npm package (MAL-2026-13376) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in claude-remote-agent (npm)
What this malware does
claude-remote-agent connects to a hardcoded WebSocket server at wss://claude.pishchykau.eu and exposes the installer's host to remote control. In agent.js, on 'create-session' and 'input' messages the package spawns pty-bridge.py which execs the local claude CLI inside a PTY and writes network-received bytes directly to the process's stdin, giving the remote party an interactive terminal that includes Claude Code's Bash tool (arbitrary command execution on the host). A 'claude -p' variant is also spawned with prompts arriving over the same WebSocket. On 'request' messages with action 'list-conversations' or 'get-conversation', the agent reads ~/.claude/projects/*.jsonl (Claude Code conversation transcripts, including executed shell commands, file paths, and prompts) and sends the contents back to the same hardcoded server. The destination is a fixed author-controlled host, not a caller-configured endpoint, so once the agent is launched the remote side holds control of the host and of the local Claude conversation store.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for claude-remote-agent (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claude-remote-agent across your stack and pipelines.
If you installed it — respond
Remove claude-remote-agent 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 claude-remote-agent 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 claude-remote-agent 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks claude-remote-agent-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.