Carbonato Botnet Hijacks Exposed Docker Hosts via AI Agents

AI‑Driven Docker Hijack Exploits Open Daemon Ports

Security researchers discovered a new botnet called Carbonato that scans for Docker daemons left exposed without authentication. It installs the Hermes AI framework and takes control of the host, using worm‑like propagation to spread worldwide. The malware targets cloud infrastructure and aims to hijack resources for cryptocurrency mining or data theft.

Carbonato was uncovered in early September by a security team monitoring Docker registries. The malware scans the internet for Docker daemons that accept connections without a password. Once found, it drops the Hermes Agent framework and begins executing remote commands. Its worm‑like module replicates to other hosts, rapidly expanding the botnet.

The AI agents in Hermes analyze host resources. They pick profitable targets like cryptocurrency mining rigs or data exfiltration nodes. This smarter method evades detection by traditional security tools.

Is Your Docker Deployment Safe?

Security experts say misconfigured containers provide a low‑barrier entry point for attackers, a senior analyst noted.

Organizations that expose Docker APIs to the public without authentication are instantly at risk. The botnet can reach any reachable port 2375, the default Docker daemon port, and take full control of the host.

Even internal networks are vulnerable if firewalls misconfigure port forwarding or if containers run with privileged mode. Regular audits and strict firewall rules are essential defenses.

Frequently Asked Questions

Compromise of Docker hosts can lead to large‑scale data breaches, ransomware deployment, or the creation of massive botnets that threaten internet stability. As cloud adoption grows, the attack surface expands, urging providers to harden default configurations and enforce strong authentication. This trend highlights the urgent need for better container security practices worldwide.

How does Carbonato differ from earlier Docker‑targeting malware? Disable unauthenticated Docker API access, enforce strong passwords or TLS certificates, and limit container privileges. Regular updates and scan images for suspicious code.

What steps can administrators take to protect their Docker environments? The framework is a genuine open‑source AI tool, but the malware repurposes it for malicious automation. Its presence alone does not indicate compromise, but unusual network traffic from the host should trigger investigation.