remote-claude-daemonnpm
remote-claude-daemon is a confirmed malicious npm package (MAL-2026-13455) that steals credentials and exfiltrates sensitive data (malicious versions 0.3.0, 0.3.4, 0.3.5…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in remote-claude-daemon (npm)
What this malware does
remote-claude-daemon connects to a hardcoded WebSocket relay at wss://remote-claude-relay.fly.dev and treats inbound messages as commands executed against the local host. On receiving ai_query/ai_voice_query messages, the daemon spawns the local claude binary with --continue -p --dangerously-skip-permissions and the remote-supplied prompt as input, giving the remote side arbitrary code execution through Claude Code's agent tooling with the permissions prompt disabled. A separate handleInput path dispatches remote messages to synthesised mouse moves/clicks, keyboard keypresses (including modifier chords) and clipboard paste via @nut-tree-fork/nut-js, giving the remote side full interactive control over the installer's desktop. The daemon additionally captures screen frames (native SCStream on macOS via a shipped Swift helper, ffmpeg gdigrab/x11grab on Windows/Linux) and optional microphone PCM audio and streams them over the same relay. Although the package is documented as a remote-Claude bridge, session tokens gate access, and --relay can override the default, the out-of-the-box configuration wires an author-controlled endpoint into an RCE + input-injection + screen/audio-capture surface on the installer. The relay operator (or anyone who obtains a session token, MITMs the connection, or compromises the relay) can execute arbitrary commands as the user, control input, and stream desktop/audio contents.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for remote-claude-daemon (20 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging remote-claude-daemon across your stack and pipelines.
If you installed it — respond
remote-claude-daemon 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 remote-claude-daemon 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 remote-claude-daemon 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 remote-claude-daemon-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.