"On 17 November 2026 (about 00:20–22:00 UTC), an unauthorized party used leaked credentials to access parts of Rackspace Spot," Rackspace wrote in a notification to affected customers.
Timeline: intrusion, discovery and restoration
Rackspace says the intrusion occurred on November 17, 2026, between roughly 00:20 and 22:00 UTC. The company learned of the activity on November 18 after receiving a customer report and confirmed that the reporting organization was affected the same day. The incident also produced an extended outage of the Rackspace Spot administration console that temporarily prevented customers from managing clusters and rotating potentially compromised credentials. After multiple delays, Rackspace announced that service had been fully restored on November 21.
What attackers were able to do inside customer clusters
According to Rackspace, attackers who used the compromised credentials were able to act as legitimate users within some customer organizations. That access allowed them to create pods in Kubernetes clusters, read Kubernetes Secrets, and list nodes and volumes. Rackspace warned that attackers could have read any Secret stored in an affected user's clusters, including Spot API tokens or refresh tokens held by that user. Kubernetes Secrets typically include sensitive items such as passwords, authentication tokens, and API keys that can be used to access databases, cloud services, and other systems.

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildRackspace mitigation steps and customer instructions
The company says it has revoked affected tokens and sessions, removed the unauthorized pods, rotated keys, and strengthened access controls and monitoring. Rackspace instructed affected customers to take several steps: reissue their Spot API tokens, replace refresh tokens used in automation tools, download fresh Kubernetes configuration files, and rotate credentials stored in their cluster Secrets. Customers were also advised to analyze logs associated with databases, container registries, Git repositories, cloud storage, and third‑party services dating back to November 17 to identify possible abuse of exposed credentials.
Indicators of compromise and operational signals
- IP address: 23.224.79.106
- IP range: 23.224.0.0/15
- Suspicious Kubernetes pod and object prefixes: i1, glm-, and probe
Rackspace shared those three concrete indicators with customers as part of its notification. BleepingComputer reached out to Rackspace asking how many customers were affected and whether customer data was stolen, but had not received a response at the time of publication.
What this means for Platform9, Rackspace customers, and security teams
Platform9 is directly implicated in the operational response: Platform9 co‑developed Rackspace Spot with Rackspace, and Sirish Raghuram, co‑founder and Chief Growth Officer of Platform9, posted on Reddit explaining that the teams deliberately disabled access while securing the environment. "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 wrote. For Rackspace customers the incident translates into immediate credential work: rotate tokens and secrets, replace automation refresh tokens, and re-download kubeconfig files as the vendor directed. For security teams, the vendor's guidance to search logs for signs of abuse dating back to November 17 frames the narrow forensic window investigators need to examine.
The breach draws a clear link between single‑point credential exposure on a managed control plane and the potential for downstream access to cluster secrets and automation tokens. Rackspace's revocation of sessions and token rotation are standard containment steps; the company also reports removing unauthorized pods and tightening access controls and monitoring. The unanswered operational questions in Rackspace's notices — most notably how many customers were affected and whether any customer data was exfiltrated — remain outstanding, and Rackspace had not answered those queries when BleepingComputer requested comment.
Source: BleepingComputer — Rackspace Spot breach let hackers access customer Kubernetes secrets




