Tech BusinessLOT 261122 · 3 min read

Hackers Read Customer Kubernetes Secrets in Rackspace Spot Breach

Hackers used leaked credentials to access Rackspace Spot for 22 hours on Nov. 17, reading Kubernetes Secrets and creating pods. Customers must rotate every credential; the console was down until Nov. 21.

By Tom Whitfield587 words

Key takeaways

  1. Intruders accessed Rackspace Spot from about 00:20 to 22:00 UTC on Nov. 17 using leaked credentials.
  2. Attackers could read Kubernetes Secrets, create pods and act as legitimate users in some customer organizations.
  3. Rackspace learned of the breach on Nov. 18 from a customer; the Spot console was fully restored Nov. 21.
  4. Indicators of compromise include IP 23.224.79.106 and pod name prefixes 'i1', 'glm-' and 'probe'.
  5. The breach follows Rackspace's $66 million raise from Voss Capital and others for its GPU cloud business.
Rackspace says hackers used leaked credentials to breach its Spot cloud and read customer Kubernetes secrets
Rackspace says hackers used leaked credentials to breach its Spot cloud and read customer Kubernetes secrets — blickpixel / pixabay

An unauthorized party held access to Rackspace Spot, the company's Kubernetes cloud platform, for roughly 22 hours on November 17 and could read customer Kubernetes Secrets, Rackspace told customers in a notice obtained by BleepingComputer.

The intrusion ran from about 00:20 to 22:00 UTC. "On 17 November 2026 (about 00:20–22:00 UTC), an unauthorized party used leaked credentials to access parts of Rackspace Spot," the notice said. Rackspace learned of the incident only on November 18, after a customer reported it.

The attackers did not break the platform itself. They entered with credentials that had already leaked, which turns the breach into a question of how much those credentials were allowed to do.

What could the attackers reach?

Rackspace Spot lets companies run containerized applications on Kubernetes. According to the notice, the intruder could act as a legitimate user inside some customer organizations. That level of access allowed three concrete actions:

  • create pods in customer clusters
  • read Kubernetes Secrets
  • list nodes and volumes

Kubernetes Secrets typically hold passwords, authentication tokens and API keys for databases, cloud services and other systems. Exposure therefore reaches well beyond the cluster itself. Rackspace warned that the attackers could have read any Secret in an affected user's clusters, as well as any Spot API or refresh tokens that user held.

The takeaway is stark: a leaked credential on this platform could unlock the keys to everything a customer had connected to it.

What must customers do now?

Rackspace says it revoked affected tokens and sessions, removed the unauthorized pods, rotated keys and tightened access controls and monitoring. It placed the burden of cleanup on customers, with four required steps:

  • reissue Spot API tokens
  • replace refresh tokens used in automation
  • download fresh Kubernetes configuration (kubeconfig) files
  • rotate every credential stored in cluster Secrets

The company also advised checking logs for databases, container registries, Git repositories, cloud storage and third-party services back to November 17. The indicators it shared include the IP address 23.224.79.106, the address range 23.224.0.0/15, and suspicious pod and object name prefixes "i1", "glm-" and "probe".

In short, Rackspace cannot rule out that stolen Secrets were used elsewhere, so customers must treat every connected credential as compromised.

Why was the console down for days?

The breach also knocked out the Spot administration console for an extended period. That outage had a compounding effect: customers could not manage their clusters or rotate credentials while the exposure was still fresh.

Sirish Raghuram, co-founder of Platform9, which co-developed Spot with Rackspace, said on Reddit that the team deliberately shut off access to sanitize the environment. He wrote that the team was "incredibly disappointed to have let you down in this way." Rackspace said service was fully restored on November 21.

The company has not said how many customers were affected or whether data was actually stolen.

The incident lands at a sensitive moment for Rackspace. The company is trying to grow its GPU cloud business and this month raised $66 million from Voss Capital and others for those plans, after tripling its capital spending. A credentials-based breach on an existing platform will not stop that expansion by itself, but it gives prospective GPU cloud customers a fresh reason to scrutinize the company's access controls.

Rackspace has not disclosed whether the leaked credentials came from a customer, a partner or its own systems, and until it does, the scope of the cleanup remains the number to watch.

mlq.ai (Source)

Filed under

Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Staff writer covering companies, deals and strategy in Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.

1,200 articles

Read also

« Previous article