
Rackspace has warned customers that attackers broke into its Rackspace Spot cloud platform using compromised credentials, BleepingComputer reports. Spot is a platform for deploying and managing containerized applications on Kubernetes. According to a notification sent to affected customers and obtained by BleepingComputer, an unauthorized party used leaked credentials to access parts of the platform on November 17, 2026, between about 00:20 and 22:00 UTC. Rackspace says it learned of the intrusion on November 18 after a customer report.
In some customer organizations the attackers could act as legitimate users: they could create pods in Kubernetes clusters, read Kubernetes Secrets, and list nodes and volumes. Secrets are where applications keep passwords, authentication tokens and API keys, so Rackspace warned that the attackers could have read any Secret stored in an affected user’s clusters, plus any Spot API tokens or refresh tokens that user held. Rackspace says it has revoked affected tokens and sessions, removed the unauthorized pods, rotated keys, and tightened access controls and monitoring. BleepingComputer asked how many customers were affected and whether customer data was stolen, and had not received a response when it published.
The incident also caused an extended outage of the Spot administration console, which temporarily stopped customers from managing clusters and rotating credentials. In a Reddit thread linked by BleepingComputer, Sirish Raghuram, co-founder and Chief Growth Officer of Platform9 (which co-developed Spot with Rackspace), said access was deliberately shut off while the environment was sanitized. Rackspace announced that service was fully restored on November 21.
How to check if you’re affected
Affected products are Rackspace Spot accounts and the Kubernetes clusters in them. Rackspace’s notice went to affected customers, and the company has not said how many organizations were impacted. If your organization runs workloads on Rackspace Spot and received the notice, the instructions it gives customers (as relayed by BleepingComputer) are to:
- Reissue Spot API tokens and replace refresh tokens used in automation tools.
- Download fresh Kubernetes configuration files.
- Rotate credentials stored in your cluster Secrets.
- Analyze logs for databases, container registries, Git repositories, cloud storage and third-party services from November 17 onward to spot possible abuse of exposed credentials.
Rackspace shared these indicators of compromise: IP address 23.224.79.106, the IP range 23.224.0.0/15, and suspicious Kubernetes pod and object name prefixes i1, glm- and probe. Rackspace says it has already removed the unauthorized pods it found; checking your own clusters for pods with those prefixes is our suggestion, not a step BleepingComputer attributes to Rackspace. We have not read the notice itself.
Sources
- BleepingComputer: Rackspace Spot breach let hackers access customer Kubernetes secrets
- Reddit r/rxt_spot: “Rackspace Spot down right now” (linked from BleepingComputer; page loaded as a shell with no readable content; not read directly)
- Reddit r/rxt_spot: “Service fully restored” (linked from BleepingComputer; not read directly)
