@ai-support-agent/clinpm
@ai-support-agent/cli is a confirmed malicious npm package (MAL-2026-10707) that steals credentials and exfiltrates sensitive data (malicious versions 0.3.2, 0.3.2-beta.0, 0.3.2-beta.1…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ai-support-agent/cli (npm)
What this malware does
The @ai-support-agent/cli package installs a long-running daemon (ai-support-agent start) that connects to a vendor API (default wss://api.ai-support-agent.com/ws/agent-terminal and matching AppSync/HTTP endpoints) and executes remote-delivered commands against the local host. In dist/vscode/vscode-server.js and related files, handleStdin base64-decodes WebSocket message payloads and writes them straight into a local PTY (session.write(decoded)), giving a caller with a valid token an interactive shell on the machine running the agent. A separate command-dispatch path handles structured messages including execute_command (shell), file_read/file_write/file_delete/file_mkdir, process_list/process_kill, chat (spawns Claude Code / arbitrary subprocess), and setup/reboot/update, streaming results back to the vendor. darwin-service.js and linux-service.js install the agent as a persistent system service that starts on boot, and the daemon reaches the vendor over the public internet by default. Anyone who legitimately holds — or who compromises — the vendor API endpoint has full-host remote code execution, filesystem read/write, process control, and reboot capability on every machine running this agent. The daemon behavior is documented as the product's purpose (Web UI drives remote shell/file/process operations), but the network-to-PTY and network-to-exec paths are a persistent backdoor by construction regardless of framing, and blast radius extends to any future compromise of the vendor's control plane.
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 @ai-support-agent/cli (29 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ai-support-agent/cli across your stack and pipelines.
If you installed it — respond
@ai-support-agent/cli 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 @ai-support-agent/cli 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 @ai-support-agent/cli 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 @ai-support-agent/cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.