Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@ai-support-agent/clinpm

Malicious code in @ai-support-agent/cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10707
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ai-support-agent/cli

What this malware does

When ai-support-agent start is invoked, the CLI subscribes to a remote AppSync/WebSocket channel at api.ai-support-agent.com and dispatches server-delivered messages into local execution sinks. execute_command messages are passed to spawn(shellCmd, ['-c', command]) in shell-executor.js; terminal-ws stdin frames are base64-decoded and written into a node-pty session (terminal-websocket.js handleStdin: Buffer.from(msg.data,'base64').toString('utf-8'); session.write(decoded)); additional handlers cover file_read/write/delete, process_kill, ssh_exec, server_setup_exec, reboot, and update. Whoever controls the vendor server — or anyone who obtains a valid agent token — has full shell-level control of the host running the agent. Related components include dist/vscode/vscode-server.js and dist/browser/browser-local-server.js (local HTTP endpoints and ping-based reachability probes) and dist/cli/service/{darwin,linux}-service.js (installs the agent as a persistent system service that modifies PATH), which extend and persist that control surface.

Malicious versions

1 flagged
0.3.2-beta.1

Indicators of compromise (SHA-256)

9e75ec61a75a0063b3e468c17ed905250c786c148bc8e30edfa93e20c4a19a54

Detection & response playbook

Credential / info stealer

  1. Find 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 (version 0.3.2-beta.1). 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.

  2. 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.

  3. 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.

  4. 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

No. @ai-support-agent/cli on npm has been identified as a malicious package (version 0.3.2-beta.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010795

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.

Malware detection Runtime egress monitoring