Rackspace Spot breach let hackers access customer Kubernetes secrets
Rackspace Spot platform breached via compromised credentials, exposing customer Kubernetes secrets.
Rackspace disclosed a breach of its Rackspace Spot cloud platform, where hackers used leaked credentials to access customer Kubernetes secrets and deploy unauthorized workloads. The incident, which occurred on November 17, 2026, allowed attackers to read sensitive information like passwords and API keys stored in customer clusters. Rackspace has since revoked tokens, rotated keys, and strengthened access controls, while advising affected customers to reissue tokens and rotate credentials.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Rackspace?
Get an email when a new story names Rackspace, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonAttackers leveraged leaked credentials to authenticate into Rackspace's Spot platform and read sensitive Kubernetes secrets — including passwords and API keys — stored within customer clusters. The root issue was that valid credentials provided unrestricted access to highly sensitive secret objects without additional authentication layers or anomaly detection to flag the unusual access. This matters because Kubernetes secrets, if left unencrypted at rest and inadequately access-controlled, become a single point of failure that can expose an entire cloud workload's credentials. Cloud providers managing multi-tenant Kubernetes environments carry an elevated duty to enforce least-privilege access, detect credential misuse, and ensure secrets are protected beyond basic RBAC.
What helps against this
How we list vendors- Identity threat detection and response (ITDR)
Attackers who log in with real, stolen credentials get noticed.
- Secrets management
API keys, tokens and passwords stop leaking from code, chat and configuration files.
- Endpoint detection and response (EDR and XDR)
Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- malware: probe
- malware: i1
- malware: glm-
- ip: 23.224.79.106