NEWS

Rackspace Spot Breach Let Attackers Read Customer Kubernetes Secrets

Rackspace says leaked credentials let attackers act as users on its Spot platform on Nov 17, create pods and read Kubernetes Secrets. Customers should rotate tokens.

Dylan H.

News Desk

November 21, 2026
2 min read
Rackspace Spot Breach Let Attackers Read Customer Kubernetes Secrets

Overview

Rackspace has warned customers that attackers breached parts of its Rackspace Spot platform using leaked credentials, according to BleepingComputer's report on Nov 21, 2026. Spot is a cloud service for deploying and managing containerized applications on Kubernetes.

What happened

Rackspace says an unauthorized party accessed the platform on Nov 17, between about 00:20 and 22:00 UTC. A customer reported the intrusion on Nov 18, and Rackspace confirmed that day that the customer's organization was affected. The company has not said where the credentials leaked from.

In some customer organizations the attackers acted as legitimate users. They could create pods, read Kubernetes Secrets, and list nodes and volumes. Rackspace warned they could have read any Secret in an affected user's clusters, plus that user's Spot API tokens and refresh tokens.

Rackspace's response

Rackspace says it revoked affected tokens and sessions, removed the unauthorized pods, rotated keys and strengthened access controls and monitoring. It also shut down administration console access for an extended period while cleaning the environment, which left customers unable to manage clusters or rotate credentials. Full service restoration was announced on Nov 21 after several delays.

Rackspace has not said how many customers were affected or whether customer data was stolen.

Indicators of compromise

  • IP address 23.224.79.106, within the range 23.224.0.0/15
  • Suspicious Kubernetes pod and object name prefixes: i1, glm- and probe

What to do

  • Reissue Spot API tokens and replace refresh tokens used in automation.
  • Download fresh Kubernetes configuration files.
  • Rotate every credential stored in cluster Secrets.
  • Review logs from Nov 17 onward for databases, container registries, Git repositories, cloud storage and third-party services, looking for misuse of exposed credentials.
  • Search clusters for pods or objects matching the prefixes above and for traffic from the listed IP range.

Sources