A security incident at Rackspace Spot, the company's container orchestration platform, allowed unauthorized actors to access customer Kubernetes environments after obtaining valid login credentials. The intrusion occurred on November 17, 2026, between approximately 00:20 and 22:00 UTC, and Rackspace learned of the compromise the following day after a customer reported suspicious activity.
Rackspace Spot enables organizations to deploy and manage containerized workloads using Kubernetes. In the breach notification obtained by BleepingComputer, Rackspace stated: "On 17 November 2026 (about 00:20–22:00 UTC), an unauthorized party used leaked credentials to access parts of Rackspace Spot."
Scope of the Attack

The attackers leveraged their access to impersonate legitimate users within affected customer organizations. This capability allowed them to create pods within Kubernetes clusters, retrieve Kubernetes Secrets, and enumerate nodes and volumes across the infrastructure.
Kubernetes Secrets are database objects designed to hold sensitive data such as passwords, authentication tokens, and API keys—credentials commonly used to access databases, cloud services, and other integrated systems. Rackspace confirmed that attackers could have accessed any Secret stored in compromised clusters, along with Spot API tokens and refresh tokens associated with affected users.
Remediation Steps
Rackspace has revoked compromised tokens and sessions, removed unauthorized pods from customer environments, rotated cryptographic keys, and enhanced access controls and monitoring systems. The company instructed affected customers to take several protective actions:
- Reissue Spot API tokens
- Replace refresh tokens used in automation workflows
- Obtain fresh Kubernetes configuration files
- Rotate credentials stored within cluster Secrets
Rackspace also recommended that customers review audit logs from databases, container registries, Git repositories, cloud storage systems, and third-party services from November 17 onward to detect any unauthorized use of exposed credentials.
Indicators of Compromise
Rackspace provided the following technical indicators associated with the attack:
- IP address: 23.224.79.106
- IP range: 23.224.0.0/15
- Suspicious Kubernetes pod and object prefixes: i1, glm-, and probe
Service Disruption and Recovery
The incident triggered an extended outage of the Rackspace Spot administration console, temporarily blocking customers from managing their clusters and rotating potentially compromised credentials. Sirish Raghuram, co-founder and Chief Growth Officer of Platform9—which co-developed Rackspace Spot alongside Rackspace—addressed the service disruption in a Reddit discussion.
I've been instrumental in creating Spot and in its operations to date, and I can tell you that the team and I are incredibly disappointed to have let you down in this way. 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.
Sirish Raghuram, co-founder and Chief Growth Officer of Platform9
After several delays, Rackspace announced full service restoration on November 21. BleepingComputer requested information regarding the number of affected customers and whether customer data was exfiltrated, but Rackspace has not yet provided a response.