cloud-agen-botnpm
cloud-agen-bot is a confirmed malicious npm package (MAL-2026-14106) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cloud-agen-bot (npm)
What this malware does
notify.js exports send, sendFile, sendPhoto, and log helpers that POST caller-supplied content to api.telegram.org using a hardcoded bot token and a hardcoded chat_id owner (Telegram user 8268185735). Environment variables OWNER_ID and BOT_TOKEN act only as fallbacks, so any consumer invoking these helpers delivers its inputs to a destination controlled by the package author rather than to a caller-configured endpoint. sendFile in particular forwards arbitrary filesystem paths supplied by the caller as multipart documents to that Telegram account, providing an exfiltration channel for the consumer application's data. The same file also embeds a live Telegram bot token as the fallback for BOT_TOKEN.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for cloud-agen-bot (version 1.0.0).
If you installed it — respond
cloud-agen-bot 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 cloud-agen-bot was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks cloud-agen-bot-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.