---
title: "Rackspace Spot Kubernetes credential incident"
description: "Leaked credentials enabled access to Rackspace Spot customer environments and potentially Kubernetes Secrets; recovery interrupted console access."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-11-22"
canonical_url: "https://www.ally.security/incidents/rackspace-spot-kubernetes-credential-incident-2026"
markdown_url: "https://www.ally.security/incidents/rackspace-spot-kubernetes-credential-incident-2026.md"
stix_url: "https://www.ally.security/incidents/rackspace-spot-kubernetes-credential-incident-2026/stix.json"
---

# Rackspace Spot Kubernetes credential incident

Rackspace Spot investigated credential abuse affecting customer clusters and shut down access while securing its infrastructure.

Last modified Nov 22, 2026 · 2 sources

## Summary

- **Environment:** Rackspace Spot cloud platform and customer Kubernetes clusters
- **Operational impact:** Console access interrupted during recovery; restoration reported November 21.
- **Financial impact:** No verified financial-loss total has been disclosed.

## What happened

A [Rackspace Spot](https://spot.rackspace.com/) notice obtained by [BleepingComputer](https://www.bleepingcomputer.com/news/security/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets/) said an intruder used leaked credentials to act as legitimate users in some customer organizations on November 17. [1](#source-1)

In the [Spot support discussion](https://github.com/rackerlabs/spot/discussions/510), operator Sirish Raghuram attributed the incident to a compromised credential used against an observability system. He said intrusive infrastructure changes prolonged recovery. The complete path from that system to customer-cluster access remains unexplained publicly. [2](#source-2)

## Impact

The notice described permission to create pods, read Kubernetes Secrets and list nodes and volumes. Rackspace warned that cluster Secrets and affected users' Spot tokens could have been read; this does not prove every accessible secret was extracted. Console unavailability also prevented cluster management. [1](#source-1)

## Timeline

### November 17, 2026 — Unauthorized access reported

The notice places access at approximately 00:20–22:00 UTC. [1](#source-1)

### November 18, 2026 — Customer alerts Rackspace

A customer report prompted discovery. [1](#source-1)

### November 20, 2026 — Operator explains extended outage

Raghuram described ongoing changes to infrastructure clusters while revising the restoration estimate. [2](#source-2)

### November 21, 2026 — Restoration reported

BleepingComputer reported Rackspace's restoration announcement. [1](#source-1)

### November 22, 2026 — Briefing updated

This briefing was last reviewed and updated on November 22, 2026.

## Threat Group & Attack Vector

Credential abuse is corroborated by the operator's account. Whose credential was compromised and how it was obtained remain undisclosed. [2](#source-2)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- [T1078 — Valid Accounts](https://attack.mitre.org/techniques/T1078/): leaked credentials enabled activity as legitimate Spot users. [1](#source-1)

## Response

Rackspace reported revoking tokens and sessions, removing unauthorized pods and rotating keys. It advised customers to replace tokens and Kubernetes configuration files, rotate cluster credentials and review dependent-service logs from November 17. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/rackspace-spot-kubernetes-credential-incident-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Rackspace Spot breach let hackers access customer Kubernetes secrets

news · BleepingComputer · Nov 21, 2026

<https://www.bleepingcomputer.com/news/security/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets/>

<a id="source-2"></a>

### Update On Spot Outage — operator replies

official · Rackspace Spot support community · Nov 20, 2026

<https://github.com/rackerlabs/spot/discussions/510>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Occurred At · 100% confidence · current**  
   Service restoration reported: 2026-11-21
2. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Reported unauthorized Spot access
3. **Occurred At · 100% confidence · current**  
   Customer report alerts Rackspace: 2026-11-18
4. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Rackspace warned that any Secret in an affected user’s clusters and Spot API or refresh tokens held by that user could have been read; the notice does not establish that every accessible secret was extracted.
5. **Used Attack Technique · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: https://attack.mitre.org/techniques/T1078/
6. **Occurred At · 100% confidence · current**  
   Reported unauthorized Spot access: 2026-11-17
7. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Service restoration reported
8. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: BleepingComputer reported on November 21 that the Spot administration console outage prevented cluster management and that Rackspace had announced service restoration that day.
9. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: In a November 20 reply on Rackspace’s Spot support repository, Sirish Raghuram said a compromised credential was used to breach an observability system.
10. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Rackspace advised affected customers to replace Spot tokens and Kubernetes configuration files, rotate cluster credentials, and examine dependent-service logs from November 17.
11. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Rackspace said it revoked affected tokens and sessions, removed unauthorized pods, rotated keys and strengthened access controls and monitoring.
12. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Raghuram said intrusive changes to infrastructure clusters prolonged the service outage; the public reply does not explain the full path from observability access to customer-cluster permissions.
13. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Rackspace’s customer notice, obtained by BleepingComputer, said an intruder used leaked credentials to access Spot and act as legitimate users in some customer organizations.
14. **Discovered At · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: 2026-11-18
15. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Operator explains observability-system compromise
16. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: The notice placed unauthorized access at approximately 00:20–22:00 UTC on November 17 and discovery on November 18 following a customer report.
17. **Occurred At · 100% confidence · current**  
   Operator explains observability-system compromise: 2026-11-20
18. **Affected Organization · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Rackspace
19. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: The notice said the intruder could create pods, read Kubernetes Secrets, and list nodes and volumes in affected customer environments.
20. **Resulted In · 100% confidence · current**  
   Rackspace Spot Kubernetes credential incident: Customer report alerts Rackspace

</details>
