Container and cluster secrets incident
Unnamed: organisation operating an exposed notebook and Kubernetes cluster · attacker-operated agent
- What happened
- Security firm Sysdig observed an attacker-directed AI agent exploit an exposed notebook, use its mounted Docker socket to reach the host, and reuse a Kubernetes service-account token. The agent read host credentials and copied all of the cluster’s stored secrets.
- Impact
- Database and cloud credentials, SSH keys, an API key and a webhook were exposed (reported). Any later use was not reported.
- What would have caught it
- Remove host Docker sockets from application containers and restrict which accounts can read secrets. Alert on privileged container creation and bulk secret reads.
- Sources
- Sysdig investigation (source date 2026-06-04)