Rackspace Spot Breach Exposes Customer Kubernetes Secrets After Credential Compromise

Rackspace has notified affected customers of a breach on its Rackspace Spot cloud platform that occurred on November 17, 2026. Attackers used leaked credentials to gain access between 00:20 and 22:00 UTC, impersonate legitimate users, deploy unauthorized pods, and read sensitive Kubernetes Secrets containing passwords, tokens, and API keys. The company detected the intrusion after a customer report on November 18 and responded by revoking tokens, removing malicious pods, rotating keys, and disabling the administration console for remediation. Platform9 co-founder Sirish Raghuram confirmed the deliberate shutdown was intended to sanitize the environment and protect all users. Customers must now reissue API tokens, obtain fresh Kubernetes configuration files, and review logs for potential abuse of exposed credentials. Indicators of compromise include the IP address 23.224.79.106 and suspicious pod prefixes such as i1, glm-, and probe.

BleepingComputerTranslated from English

Read at source

Rackspace has warned customers that a breach of its Rackspace Spot cloud platform allowed attackers to access Kubernetes Secrets in customer clusters using compromised credentials.

Rackspace Spot enables organizations to deploy and manage containerized applications with Kubernetes. The intrusion took place on 17 November 2026 between approximately 00:20 and 22:00 UTC. Attackers acted as legitimate users, created pods, read Kubernetes Secrets, and listed nodes and volumes.

Kubernetes Secrets store passwords, authentication tokens, and API keys. The company stated that any Secret in affected clusters, along with Spot API and refresh tokens, could have been exposed.

After learning of the incident on 18 November, Rackspace revoked affected tokens and sessions, removed unauthorized pods, rotated keys, and strengthened access controls. Customers were instructed to reissue tokens, replace refresh tokens, download new configuration files, and rotate credentials stored in Secrets.

The company also recommended reviewing logs from databases, container registries, Git repositories, and cloud storage dating back to 17 November. Indicators of compromise include the IP address 23.224.79.106 and suspicious pod prefixes i1, glm-, and probe.

The breach caused a prolonged outage of the administration console. Platform9 co-founder Sirish Raghuram explained that access was deliberately disabled to sanitize the environment and best protect users.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Breaches & Leaks

FBI Investigates Second Breach Targeting National Crime Information Center Database
Bell Canada Confirms 'Agentic' Threat Actor Breach of Enterprise Customer Data via Maximo System
n0n Ransomware Claims Qubole Breach Exposing Chase Visa and Mastercard Customer Data