Rackspace Spot breach let hackers access customer Kubernetes Secrets using leaked credentials

· CyberSecurity

TLDR

  • An unauthorised party used leaked credentials to access parts of Rackspace Spot on 17 November, Rackspace told customers.1
  • Rackspace warned attackers could have read any Secret in affected users' clusters, plus their Spot API and refresh tokens.1
  • Affected customers are told to reissue API tokens, replace refresh tokens, fetch new Kubernetes configs and rotate Secrets credentials.1

Rackspace has warned customers that hackers breached its Rackspace Spot cloud platform using compromised credentials, BleepingComputer reports.1 Rackspace Spot is a cloud platform that lets organisations deploy and manage containerised applications using Kubernetes.1 BleepingComputer says it obtained the notification Rackspace sent to affected customers, which states that attackers accessed parts of the platform on 17 November 2026, between approximately 00:20 and 22:00 UTC.1 According to the notification, an unauthorised party used leaked credentials to do so.1 Rackspace says it learned of the intrusion on 18 November after a customer report and confirmed the same day that the recipient's organisation was affected.1

Rackspace says the attackers were able to act as legitimate users in some customer organisations, which let them create pods in Kubernetes clusters, read Kubernetes Secrets, and list nodes and volumes.1 BleepingComputer notes that Kubernetes Secrets store sensitive information such as passwords, authentication tokens and API keys that can be used to access databases, cloud services and other systems.1 Rackspace warned that the attackers could have read any Secret stored in an affected user's clusters, as well as any Spot API tokens or refresh tokens that user held.1

Rackspace says it has revoked affected tokens and sessions, removed the unauthorised pods, rotated keys, and strengthened access controls and monitoring.1 It has told affected customers to reissue their Spot API tokens, replace refresh tokens used in automation tools, download fresh Kubernetes configuration files, and rotate credentials stored in their cluster Secrets.1 It also advises analysing logs for databases, container registries, Git repositories, cloud storage and third-party services dating back to 17 November to spot possible abuse of exposed credentials.1 The indicators of compromise Rackspace shared are the IP address 23.224.79.106, the IP range 23.224.0.0/15, and suspicious Kubernetes pod and object prefixes i1, glm- and probe.1

The breach also caused an extended outage of the Rackspace Spot administration console, temporarily preventing customers from managing their clusters and rotating potentially compromised credentials, BleepingComputer reports.1 Sirish Raghuram, co-founder and Chief Growth Officer of Platform9, which co-developed Rackspace Spot with Rackspace, said in a Reddit discussion that the company deliberately disabled access while securing its infrastructure, as reported by BleepingComputer.1 After multiple delays, Rackspace announced that service had been fully restored on 21 November.1 BleepingComputer says it asked Rackspace how many customers were affected and whether customer data was stolen, but had not received a response.1 We found no Rackspace public notice or independent outlet confirming the incident, so this account rests on BleepingComputer's copy of the customer notification.

Why it matters: Rackspace says the attackers could have read any Secret in affected clusters, so customers are told to rotate every credential stored there and check logs back to 17 November.1

Sources

  1. Rackspace Spot breach let hackers access customer Kubernetes secrets (BleepingComputer)