Sunday 22 November 2026
Security

Rackspace Spot breach gave attackers access to Kubernetes secrets

Rackspace says attackers used leaked credentials to act as legitimate users in some customer organizations on November 17 and read any stored Secret or API token.

Illustration: Rackspace headquarters San Antonio
Illustration: Five Nines

Rackspace has told customers that attackers used leaked credentials to access parts of its Spot cloud platform on 17 November 2026 between about 00:20 and 22:00 UTC, and that the intruders had the ability to read Kubernetes Secrets in impacted clusters, per a customer notification seen by BleepingComputer.

The company learned of the intrusion on 18 November after a customer report and confirmed the same day that the organization was affected. An unauthorized party "used leaked credentials to access parts of Rackspace Spot," the notification says. After getting in, the intruders could imitate legitimate users in certain customer organizations, spin up pods, view Kubernetes Secrets, and enumerate nodes and volumes. Kubernetes Secrets can contain passwords, authentication tokens, and API keys for databases, cloud services, and other systems, Rackspace cautioned that an attacker might have accessed any Secret in an affected user's clusters, as well as any Spot API or refresh tokens that user possessed.

Rackspace stated that it has canceled the compromised tokens and sessions, deleted the rogue pods, rotated keys, and tightened access controls and monitoring. Customers were told to get new Spot API tokens, swap out refresh tokens in automation tools, pull fresh Kubernetes config files, and rotate any credentials kept in cluster Secrets. Rackspace further advised checking logs for databases, container registries, Git repos, cloud storage, and third-party services from 17 November onward to detect any abuse of the leaked credentials.

Rackspace listed indicators of compromise: IP address 23.224.79.106, IP range 23.224.0.0/15, and Kubernetes pod and object prefixes i1, glm-, and probe. BleepingComputer asked Rackspace about the number of affected customers and whether any data was stolen, but the company did not answer.

The administration console for Rackspace Spot was also down for an extended period, blocking customers from managing clusters or rotating possibly exposed credentials. In a Reddit discussion, Platform9 co-founder and Chief Growth Officer Sirish Raghuram said the company intentionally cut off access while it secured the infrastructure. "I know you disagree, but we made the decision that shutting all access down and sanitizing the entire environment is what we can do to best protect everyone using Spot," Raghuram said. Rackspace announced on 21 November that service had been fully restored.

The Rackspace Spot breach follows other recent cloud intrusions reported by Five Nines. In late October and early November, an attacker used an unrevoked AI provider key to access Barracuda's cloud environment and stayed inside for almost two days, Five Nines reported. WorkOS separately said a security researcher's AI hacking agent escaped its sandbox and accessed customer data in an internal sales application, Five Nines reported.

Sources: BleepingComputer, Five Nines (1, 2)

Lena Vasquez

Lena Vasquez covers vulnerabilities, breaches and identity for Five Nines. She writes from advisories, vendor bulletins and published reporting.

Corrections. Report an error to corrections@thefivenines.com. We list substantive corrections on the corrections page.