Skip to content

Data Breaches

Attackers used leaked credentials to access customer Secrets in Rackspace Spot

BleepingComputer said Rackspace found the intrusion on November 18, 2026, after a customer report, and confirmed the affected organization that day.

https://breach-signal.com/data-breaches/rackspace-spot-leaked-credentials-kubernetes-secrets-breach/

Share

Using leaked credentials, intruders got into parts of Rackspace Spot on November 17, 2026, during a window that ran from about 00:20 to 22:00 UTC, BleepingComputer reported. Rackspace learned of the intrusion on November 18, 2026, after a customer report and confirmed the affected organization that same day.

Once inside, the intruders acted as legitimate users within some customer organizations, created pods, viewed Kubernetes Secrets, and listed nodes and volumes. These secrets store passwords, authentication tokens and API keys that can reach databases, cloud services and other systems. The intruders might have reached every Secret in affected clusters along with the user’s Spot API tokens and refresh tokens.

Rackspace cancelled affected tokens and sessions, removed unauthorized pods, replaced keys, and tightened access controls and monitoring. During the outage, customers temporarily could not reach the Rackspace Spot administration console, manage clusters, or rotate credentials. Spot service came back fully on November 21 after several delays, Rackspace said.

Platform9 helped build Rackspace Spot, a cloud platform that runs containerized applications through Kubernetes, a system for managing them. Sirish Raghuram, Platform9’s co-founder and Chief Growth Officer, said on Reddit that the team had cut off access to secure infrastructure and regretted the incident. BleepingComputer sought the number of affected customers and asked whether data had been stolen, but Rackspace had not replied.

Indicators of compromise are IP address 23.224.79.106, range 23.224.0.0/15, and prefixes for pods and objects: i1, glm-, and probe. Rackspace tells affected customers to reissue Spot API tokens, replace refresh tokens used by automation tools, download fresh Kubernetes files, and rotate credentials in cluster Secrets. The company also told customers to check logs from November 17 onward for code repositories, databases, storage, registries, and outside services to spot misuse of exposed credentials.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *