Rackspace Spot breach exposed Kubernetes secrets, prompting massive credential reset
A credential leak let attackers create pods, read Kubernetes Secrets, and disrupt the Rackspace Spot console for nearly a day, pushing customers to replace API tokens and rotate cluster credentials.

According to BleepingComputer, hackers accessed customer Kubernetes secrets on Rackspace Spot for nearly 22 hours on November 17, 2026, after using leaked credentials to infiltrate the platform.
Why it matters
The breach struck at the heart of modern cloud-native operations, where Kubernetes secrets hold the keys to databases, APIs, and internal services. When those secrets are exposed, attackers can move laterally across an organization, hijack workloads, and exfiltrate data without triggering traditional perimeter alerts. For enterprises that rely on Spot to run containerized applications, the incident underscored how a single credential compromise can cascade into a full‑scale compromise of multiple workloads.
How the attackers operated
Rackspace disclosed that the unauthorized party leveraged credentials that had been leaked elsewhere, allowing them to appear as legitimate users within several customer organizations. With that foothold, the attackers created pods inside affected Kubernetes clusters, listed nodes and volumes, and, crucially, read the contents of Kubernetes Secrets. Those Secrets typically contain passwords, authentication tokens, and API keys—information that can unlock databases, cloud services, and even on‑premise systems.
The intrusion window spanned from roughly 00:20 UTC to 22:00 UTC on the same day. During that period, the adversaries could have read any secret stored in the compromised clusters, as well as any Spot API or refresh tokens held by the affected users. Because the attackers acted as legitimate users, their actions blended with normal traffic, making detection difficult until a customer reported unusual behavior.
Rackspace’s response and next steps
Within hours of learning about the intrusion on November 18, Rackspace began revoking the compromised tokens and sessions, removing the unauthorized pods, rotating cryptographic keys, and tightening access controls. The company also shut down the Spot administration console, causing an extended outage that prevented customers from managing clusters or rotating credentials until the service was fully restored on November 21.
Customers received detailed instructions: reissue Spot API tokens, replace refresh tokens used in automation tools, download fresh Kubernetes configuration files, and rotate all credentials stored in cluster Secrets. Rackspace further advised clients to scrutinize logs from databases, container registries, Git repositories, cloud storage, and third‑party services dating back to the start of the breach to spot any abuse of exposed credentials.
In a Reddit discussion, Sirish Raghuram, co‑founder and Chief Growth Officer of Platform9—the partner that co‑developed Spot—explained that the team deliberately disabled access while securing the infrastructure. “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,” Raghuram said. “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.”
What to watch next
Industry observers will monitor whether the breach leads to broader credential‑theft campaigns targeting other managed Kubernetes services. The incident also raises questions about the adequacy of credential‑management practices in cloud‑native environments and whether additional zero‑trust controls could have limited the attackers’ reach. Organizations using Spot or similar platforms should prioritize rotating secrets, implementing short‑lived tokens, and deploying continuous monitoring to detect anomalous pod creation.
Finally, the episode highlights the importance of rapid incident communication. While Rackspace acted quickly once notified, the delay between the intrusion and customer awareness suggests a need for more proactive detection mechanisms that can alert providers and tenants in real time. As cloud workloads continue to proliferate, the balance between convenience and security will remain a central debate for both vendors and their customers.
The Morning Brief
One email a day with the stories that matter. Free, forever.
No spam. Unsubscribe anytime.
Comments (0)
Be the first to share your thoughts.
