Overview
- Rackspace says an unauthorized party used leaked credentials to access Rackspace Spot on Tuesday and in some customer organizations created pods that listed nodes and volumes and interacted with clusters.
- Independent timelines reported attackers mounted service account tokens inside malicious containers and began reading Kubernetes Secrets in less than eight minutes after initial login.
- Rackspace disabled access to sanitize the environment revoked affected tokens removed unauthorized pods rotated keys and restored full Spot service on Saturday, November 21.
- The company published indicators of compromise including IP 23.224.79.106 the 23.224.0.0/15 range and suspicious pod/object prefixes i1 glm- and probe and instructed customers to reissue Spot API tokens refresh automation tokens download fresh kubeconfigs and rotate Secrets.
- Kubernetes Secrets often hold database passwords API keys and tokens so their exposure can let attackers pivot to databases registries and external services which raises pressure on managed-cloud operators to add runtime controls least-privilege RBAC and continuous scanning.