Rackspace has warned customers that attackers used compromised credentials to access parts of the Rackspace Spot cloud platform, deploy unauthorized workloads, and potentially read Kubernetes Secrets in customer clusters. The intrusion occurred on November 17, 2026, and led Rackspace to revoke tokens, remove unauthorized pods, rotate keys, and temporarily shut down access to the Spot management console.
Rackspace Spot is a cloud platform that organizations use to deploy and manage containerized applications with Kubernetes.
Attack exposed Kubernetes credentials and secrets
Rackspace disclosed the breach in a notice sent to affected customers and obtained by BleepingComputer. The company said the attacker accessed portions of the platform between approximately 00:20 and 22:00 UTC on November 17, 2026.
Rackspace said it learned of the incident on November 18 after receiving reports from customers and confirmed that recipient organizations were affected the same day.
“On November 17, 2026 (approximately 00:20-22:00 UTC), an unauthorized party gained access to portions of Rackspace Spot using compromised credentials,” the notice states.
According to Rackspace, the attackers were able to act as legitimate users in some customer organizations. They created pods within Kubernetes clusters, read Kubernetes Secrets, and listed nodes and volumes.
Kubernetes Secrets can contain sensitive information, including passwords, authentication tokens, and API keys used to access databases, cloud services, and other systems.
Rackspace warned that the attackers may have been able to read secrets stored in affected users’ clusters, along with Spot API tokens and refresh tokens held by those users.
Rackspace tells customers to rotate credentials
Rackspace said it has revoked affected tokens and sessions, removed unauthorized pods, rotated keys, and strengthened access controls and monitoring.
The company instructed affected customers to reissue Spot API tokens, replace refresh tokens used by automation tools, download new Kubernetes configuration files, and rotate credentials stored in cluster secrets.
Rackspace also advised customers to review logs dating back to November 17 for databases, container registries, Git repositories, cloud storage, and third-party services. The analysis could help identify potential misuse of exposed credentials.
The company shared the following indicators of compromise related to the attack:
- IP address: 23.224.79.106
- IP range: 23.224.0.0/15
- Prefixes for suspicious Kubernetes pods and objects: i1, glm-, and probe
BleepingComputer contacted Rackspace to ask how many customers were affected and whether customer data was stolen, but the company did not respond.
Rackspace Spot service outage
The breach also caused an extended outage of the Rackspace Spot management console. Customers were temporarily unable to manage their clusters or rotate potentially compromised credentials.
In a Reddit discussion, Sirish Raghuram, co-founder and chief growth officer of Platform9, which co-developed Rackspace Spot with Rackspace, said the company deliberately disabled access while securing its infrastructure.
“I have been instrumental in the founding and running of Spot, and my team and I are extremely disappointed that we have let you down in this way,” Raghuram said.
“We know you may not agree, but we have determined that to best protect everyone using Spot, the best thing we can do is shut down all access and disinfect the entire environment.”
After multiple delays, Rackspace announced that the service was fully restored on November 21.
Adaptive Security’s AI agent analyzes email intent, context, and behavior to uncover phishing, business email compromise, and invoice fraud.
See what’s happening with a 14-day read-only scan of Microsoft 365 or Google Workspace without making any changes to MX.
Source: www.bleepingcomputer.com




