Rackspace has confirmed a security breach affecting its Rackspace Spot cloud platform, a service designed for managing containerized applications through Kubernetes. The unauthorized access occurred on November 17, 2026, spanning a window from approximately 00:20 to 22:00 UTC. The company discovered the intrusion on November 18 following a report from a customer and subsequently verified that the incident had compromised specific user organizations.
According to the company, the attackers gained entry by utilizing leaked credentials, which allowed them to masquerade as legitimate users within the platform. This access granted the intruders the ability to perform a variety of administrative actions, including the deployment of unauthorized Kubernetes pods, the listing of nodes and volumes, and the retrieval of sensitive Kubernetes Secrets. These Secrets often contain critical authentication data, such as API keys, database passwords, and service tokens.
Rackspace has acknowledged that the attackers could have accessed any Secret stored within the clusters of affected customers. Furthermore, the breach potentially exposed Spot API tokens and refresh tokens used for automation. In response to the incident, Rackspace revoked all compromised sessions and tokens, purged the unauthorized pods, and performed a rotation of internal keys. The company also implemented enhanced monitoring and stricter access controls to secure the environment.
To mitigate the impact, Rackspace has issued comprehensive instructions to affected users. Customers are advised to reissue their Spot API tokens, replace any refresh tokens integrated into their automation workflows, and download new Kubernetes configuration files. Additionally, the company recommends that users rotate all credentials currently stored within their cluster Secrets. Because the attackers may have utilized these credentials to access external systems, Rackspace has urged customers to audit logs for databases, cloud storage, container registries, and third-party services dating back to November 17.
The incident resulted in a significant disruption to the Rackspace Spot administration console. The service was taken offline deliberately by the platform's operators as a security measure to sanitize the environment and prevent further unauthorized activity. While this outage prevented customers from managing their clusters or rotating credentials during the remediation phase, the company maintained that the shutdown was necessary to protect the broader user base. Full service was restored by November 21.
Rackspace has provided specific indicators of compromise to assist customers in their internal investigations. These include the IP address 23.224.79.106 and the broader IP range 23.224.0.0/15. Furthermore, customers are encouraged to search for suspicious Kubernetes object and pod prefixes, specifically those labeled as i1, glm-, and probe.
While Rackspace has confirmed the scope of the unauthorized access and the nature of the exposed data, the company has not disclosed the total number of customers impacted by the breach. It remains unverified whether the attackers successfully exfiltrated customer data beyond the initial access to the Kubernetes Secrets and API tokens. Rackspace has not provided further comment regarding the extent of potential data theft.





