Rackspace Spot Breach Let Attackers Access Customer Kubernetes Secrets

· Original article ↗

Summary

Rackspace confirmed attackers used leaked credentials to access its Spot platform, create Kubernetes pods and read customer Secrets. It revoked tokens, removed unauthorized pods and restored service; the number of affected customers and whether data was stolen remain un

Key points

  • Rackspace said attackers used leaked credentials to access parts of Rackspace Spot on November 17, 2026.
  • Attackers could act as legitimate users in some customer organizations, create Kubernetes pods, read Secrets, and list nodes and volumes.
  • Rackspace warned that affected users' Spot API tokens, refresh tokens, and cluster Secrets may have been exposed; whether customer data was stolen was not known.
  • The intrusion caused an extended outage of the Spot administration console, and Rackspace said service was fully restored on November 21.
  • Rackspace revoked affected tokens and sessions, removed unauthorized pods, rotated keys, and strengthened access controls and monitoring.
  • Customers were advised to replace tokens and credentials, obtain fresh Kubernetes configuration files, and review logs for possible misuse.
  • Rackspace provided the IP address 23.224.79.106, the range 23.224.0.0/15, and suspicious pod and object prefixes i1, glm-, and probe.

Article Details

Victim Organization
Rackspace
Victim Domain
Unknown
Incident Type
Unauthorized access using compromised credentials, with unauthorized Kubernetes pod deployment and access to customer Kubernetes Secrets.
Incident Date
2026-11-17
Disclosure Date
2026-11-21
Data Types Exposed
  • Kubernetes Secrets, which may contain passwords, authentication tokens, and API keys
  • Spot API tokens and refresh tokens
  • Credentials stored in cluster Secrets
Affected Records
Not disclosed
Affected Data Size
Not disclosed
Operational Impact
The Rackspace Spot administration console experienced an extended outage, temporarily preventing customers from managing clusters and rotating potentially compromised credentials. Rackspace removed unauthorized pods, revoked affected tokens and sessions, rotated keys, strengthened access controls and monitoring, and restored service on November 21.
Ransom Or Extortion
Not disclosed
Claim Status
confirmed

Indicators of compromise

TypeIndicatorContext
IPV423[.]224[.]79[.]106IP address listed by Rackspace as an indicator of compromise associated with the attack.

MITRE ATT&CK

People

Vendors

Products

Related Articles