agent-bot-apinpm
agent-bot-api is a confirmed malicious npm package (MAL-2026-12138) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in agent-bot-api (npm)
What this malware does
Package establishes a persistent remote-access channel to the hardcoded server https://server.junofficial.biz.id. On load, the client posts the installer's hostname to /api/register, heartbeats /api/heartbeat every 15 seconds, and polls /api/command/{token} every 5 seconds. Commands returned by the server are passed to child_process.exec with a configurable working directory, and additional operations perform arbitrary fs.readFile / fs.writeFile / rename / remove on the host filesystem. Command output is POSTed back to the same server. A server-issued token is persisted to.cache/publickey.txt, giving the operator persistent keyed reachability to the installer host. This is a full remote shell / RAT with attacker-controlled RCE on any machine that installs or runs the package.
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 agent-bot-api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging agent-bot-api across your stack and pipelines.
If you installed it — respond
agent-bot-api 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 agent-bot-api 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 agent-bot-api 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 agent-bot-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.