Hackers Breach Rackspace Spot and Access Kubernetes Secrets
┌─ rackspace-spot-breach-exposes-kubernetes-secrets.md :: hero
Rackspace has warned customers that attackers breached its Rackspace Spot cloud platform using leaked credentials, enabling unauthorised workload deployments and potential access to customer Kubernetes Secrets. The intrusion occurred on 17 November 2026 between approximately 00:20 and 22:00 UTC and was confirmed on 18 November following a customer report. Rackspace Spot, co-developed with Platform9, lets organisations run containerised Kubernetes applications. Attackers acting as legitimate users could create pods and read Secrets containing passwords, authentication tokens, and API keys. An extended administration console outage followed while Rackspace secured the platform, before full service resumed on 21 November 2026.
Key Facts
| Attribute | Value |
|---|---|
| Affected product | Rackspace Spot |
| Exploited in the wild | Yes; unauthorised access occurred on 17 November 2026 (approximately 00:20–22:00 UTC) using leaked credentials |
| Disclosure date | 21 November 2026 (reported by BleepingComputer following customer notifications) |
What Happened During the Rackspace Spot Breach?
On 17 November 2026 between roughly 00:20 and 22:00 UTC, an unauthorised party used leaked credentials to access parts of Rackspace Spot. Acting as legitimate users in some customer organisations, the attackers could create pods in Kubernetes clusters, list nodes and volumes, and read customer Kubernetes Secrets.
Rackspace stated in a customer notification that it learned of the intrusion on 18 November 2026 after receiving a customer report and confirmed the affected organisation the same day. BleepingComputer asked Rackspace how many customers were affected and whether customer data was stolen, but had not received a reply at publication time.
Attackers accessed Rackspace Spot for nearly 22 hours on 17 November 2026 using leaked credentials before Rackspace confirmed the intrusion the following day.
What Data and Systems Were Exposed?
Rackspace warned that attackers could have read any Kubernetes Secret stored in an affected user's clusters, as well as any Rackspace Spot API tokens or refresh tokens held by that user. Kubernetes Secrets store sensitive credentials including passwords, authentication tokens, and API keys for external systems.
Because exposed Secrets can unlock downstream infrastructure, Rackspace advised affected customers to inspect logs across databases, container registries, Git repositories, cloud storage, and third-party services dating back to 17 November 2026. Indicators of compromise associated with the attack, including network indicators and suspicious Kubernetes pod and object prefixes, are published in the original report.
Any secret stored in an affected customer's Kubernetes clusters or held as Spot API and refresh tokens could have been accessed during the breach.
How Did Rackspace Respond and Why Was the Console Offline?
Rackspace revoked affected tokens and sessions, removed unauthorised pods, rotated keys, and strengthened access controls and monitoring. To protect users while sanitising the infrastructure, the company deliberately disabled the Rackspace Spot administration console, causing an extended outage until service was fully restored on 21 November 2026.
In a Reddit discussion cited in the report, Sirish Raghuram, co-founder and Chief Growth Officer of Platform9, explained that the team chose to shut down all access and sanitise the environment rather than leave the console online while remediation was underway. Malaysian organisations operating workloads on Rackspace Spot should audit their clusters and connected services immediately, and may report confirmed security incidents to Cyber999 through MyCERT.
Rackspace fully restored the Rackspace Spot service on 21 November 2026 after disabling console access to remove unauthorised workloads and rotate keys.
What Should You Do?
- Reissue your Rackspace Spot API tokens and replace any refresh tokens used inside automation tools.
- Download fresh Kubernetes configuration files from your official Rackspace Spot account.
- Rotate all passwords, authentication tokens, and API keys stored in Kubernetes Secrets across affected clusters.
- Analyse logs for databases, container registries, Git repositories, cloud storage, and third-party services dating back to 17 November 2026 for signs of credential abuse.
- Consult the indicators of compromise published in the original BleepingComputer report to check your clusters for unauthorised pods or objects.
Common Questions
How did hackers gain access to Rackspace Spot?
According to Rackspace's customer notification, an unauthorised party used leaked credentials to access parts of the Rackspace Spot platform on 17 November 2026 between roughly 00:20 and 22:00 UTC. This allowed the intruders to act as legitimate users within some customer organisations.
Do we know how many customers were affected or if data was stolen?
No. BleepingComputer contacted Rackspace to ask how many customers were affected by the breach and whether customer data was stolen, but had not received a response at the time of publication. Rackspace confirmed individual affected organisations directly via customer notifications.
Why could customers not access the administration console during the incident?
Rackspace deliberately shut down access to the Rackspace Spot administration console to sanitise the environment and protect users. Platform9 co-founder Sirish Raghuram confirmed on Reddit that access was disabled during cleanup, temporarily preventing customers from managing clusters before service returned on 21 November 2026.
Sources and Methodology
This dispatch is based solely on the BleepingComputer report by Lawrence Abrams, published on 21 November 2026. No other documents, advisories, or vendor pages were reviewed or verified for this article.
$ ls -t news/ | head -5
$ ls ./tags
- #Data Breach