Which versions of @aicommander/agent are malicious?

The following npm versions of @aicommander/agent are flagged malicious: 1.0.34. Treat any of these as compromised.

How do I remediate @aicommander/agent if I installed it?

Remove @aicommander/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.

I already installed @aicommander/agent — how do I know if it already compromised me?

If @aicommander/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.

Is @aicommander/agent part of a known attack campaign?

Yes — @aicommander/agent is associated with the IN-MAL-2026-010794 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 @aicommander/agent across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @aicommander/agent (version 1.0.34). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @aicommander/agent across your stack and pipelines.

Malicious package

@aicommander/agentnpm

Malicious code in @aicommander/agent (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10708

Immediate action

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

npm uninstall @aicommander/agent

What this malware does

@aicommander/agent installs a remote-machine agent that opens an outbound WebSocket to the hardcoded relay https://aicommander.dev and executes shell commands received over that channel on the installer's host. The message handler dispatches received commands to child_process.spawn with shell:true, streaming stdout/stderr back to the relay. A session code shared with the remote operator authorizes arbitrary command execution as the agent's uid — root when installed as the documented systemd service. This is full-host remote code execution driven by a network-sourced party, regardless of the relay being a first-party vendor server; possession of the session code by any remote party equates to full control of the installer's machine.

Malicious versions

1 flagged

1.0.34

Indicators of compromise (SHA-256)

9a0d4917f10db91a59e47821bfa2399801219a85da0a59b8596d85fd3931fc93

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @aicommander/agent (version 1.0.34). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @aicommander/agent across your stack and pipelines.
If you installed it — respond
Remove @aicommander/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 @aicommander/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 @aicommander/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

No. @aicommander/agent on npm has been identified as a malicious package (version 1.0.34 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010794

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @aicommander/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.

Malware detection Runtime egress monitoring