Rackspace Spot: Leaked credentials let attackers read customer Kubernetes secrets
Severity: high · Patch status: no-fix-needed · Since 2026-11-21
Rackspace disclosed that an unauthorized party used leaked credentials to access parts of its Rackspace Spot managed Kubernetes platform on November 17, 2026, between approximately 00:20 and 22:00 UTC. Acting as legitimate users in some customer organizations, attackers could create pods, read Kubernetes Secrets, and list nodes and volumes; exposed Secrets could include passwords, tokens, and API keys, plus Spot API and refresh tokens. Rackspace learned of the intrusion on November 18 and confirmed affected customers that day. It revoked affected tokens and sessions, removed unauthorized pods, rotated keys, strengthened access controls, and restored service on November 21 after an administration-console outage. Affected customers must rotate credentials and review logs. No CVE or product patch applies; this is a credential-based breach.
What to do
- Reissue Rackspace Spot API tokens and replace refresh tokens used in automation tools.
- Download fresh Kubernetes configuration files and rotate all credentials stored in cluster Secrets.
- Remove unauthorized pods and audit Kubernetes RBAC, service accounts, and workloads for persistence.
- Analyze logs for databases, container registries, Git repositories, cloud storage, and third-party services dating back to November 17 for abuse of exposed credentials.
- Search for indicators of compromise: IP 23.224.79.106, IP range 23.224.0.0/15, and suspicious pod/object prefixes i1, glm-, and probe.
Sources
All live incidents on Threat Watch