---
title: Rackspace Spot breach: attackers used leaked credentials on Nov 17 to act as users in some customer organizations, create pods and read Kubernetes Secrets; customers told to rotate everything in their clusters | ctxsec
url: https://ctxsec.com/items/rackspace-spot-breached-nov-17-leaked-credentials-attackers-read-customer-kubernetes-secrets-created-pods-rotate-cluster-secrets
description: "Rackspace told affected customers that on Nov 17, from about 00:20 to 22:00 UTC, an unauthorized party used leaked credentials to access parts of Rackspace Spot, its managed Kubernetes platform. In some customer organizations the attacker could act as a legitimate user, create pods, read Kubernetes Secrets and list nodes and volumes, and could have read any Secret in an affected user's clusters plus that user's Spot API and refresh tokens. Rackspace learned of it on Nov 18 from a customer report, revoked tokens and sessions, removed the unauthorized pods and rotated keys. Spot co-creator Sirish Raghuram wrote on GitHub that an observability system was breached with a compromised credential, and the multi-day console outage that followed was caused by the cleanup. Rackspace says service was fully restored on Nov 21. It hasn't said how many customers were affected or whether data was taken."
status: "official (Rackspace customer notification as published by BleepingComputer, Nov 21, 2026; Spot co-creator statement on GitHub, Nov 20, 2026); number of affected customers not disclosed"
published: 2026-11-21
---

> Rackspace told affected customers that on Nov 17, from about 00:20 to 22:00 UTC, an unauthorized party used leaked credentials to access parts of Rackspace Spot, its managed Kubernetes platform. In some customer organizations the attacker could act as a legitimate user, create pods, read Kubernetes Secrets and list nodes and volumes, and could have read any Secret in an affected user's clusters plus that user's Spot API and refresh tokens. Rackspace learned of it on Nov 18 from a customer report, revoked tokens and sessions, removed the unauthorized pods and rotated keys. Spot co-creator Sirish Raghuram wrote on GitHub that an observability system was breached with a compromised credential, and the multi-day console outage that followed was caused by the cleanup. Rackspace says service was fully restored on Nov 21. It hasn't said how many customers were affected or whether data was taken.

[← Cybersecurity News](/news) · [markdown](/items/rackspace-spot-breached-nov-17-leaked-credentials-attackers-read-customer-kubernetes-secrets-created-pods-rotate-cluster-secrets.md)

official (Rackspace customer notification as published by BleepingComputer, Nov 21, 2026; Spot co-creator statement on GitHub, Nov 20, 2026); number of affected customers not disclosed

2026-11-21 7:40 PM ET

### Rackspace Spot breach: attackers used leaked credentials on Nov 17 to act as users in some customer organizations, create pods and read Kubernetes Secrets; customers told to rotate everything in their clusters

- **If you use Spot:** reissue Spot API tokens, replace refresh tokens in automation, download fresh kubeconfigs, and rotate every credential stored in cluster Secrets.
- **Then check:** logs for databases, registries, Git, cloud storage and third-party services that those Secrets unlock, back to Nov 17.
- IOCs and hunt steps are in the hunt item below.

Sources: [BleepingComputer: Rackspace Spot breach let hackers access customer Kubernetes secrets (Nov 21, 2026), quoting Rackspace's customer notification](https://www.bleepingcomputer.com/news/security/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets/) · [rackerlabs/spot GitHub Discussion #510: Update On Spot Outage (Sirish Raghuram, Spot co-creator, Nov 20, 2026)](https://github.com/rackerlabs/spot/discussions/510)
