Rackspace Spot breach exposed Kubernetes secrets after attackers used leaked credentials
Rackspace said attackers used leaked credentials to access parts of its Spot cloud platform on 17 November, acting as legitimate users in some customer organisations. They could deploy pods, read Kubernetes Secrets and list nodes and volumes; Rackspace says it revoked tokens, removed the unauthorised pods and restored service on 21 November, but has not said how many customers were affected or whether data was stolen.
Bottom line — Rackspace has restored Spot, but affected customers must rotate exposed secrets and investigate activity dating back to 17 November.
Go deeper 6
-
BleepingComputer reported that the intrusion lasted from about 00:20 to 22:00 UTC on 17 November; Rackspace learned of it the next day after a customer report.
-
Rackspace warned that attackers could have read any Kubernetes Secret in affected clusters, including passwords, API keys and authentication tokens.
-
Rackspace told affected customers to reissue Spot API tokens, replace automation refresh tokens, download fresh Kubernetes configuration files and rotate cluster credentials.
-
The company advised checking logs for databases, container registries, Git repositories, cloud storage and third-party services from 17 November onward.
-
Rackspace also shared indicators including suspicious pod or object names beginning i1, glm- or probe, according to SecurityElites.
-
The Spot administration console was offline during remediation, temporarily preventing customers from managing clusters and rotating credentials; Platform9 co-founder Sirish Raghuram said the team shut access to sanitise the environment.