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.
- Record status: Developing record. Reviewed November 22, 2026; updated as evidence emerges.
What happened
A Rackspace Spot notice obtained by BleepingComputer said an intruder used leaked credentials to act as legitimate users in some customer organizations on November 17. [1]
In the Spot support discussion, 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]
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]
Timeline
Unauthorized access reported
The notice places access at approximately 00:20–22:00 UTC.
[1]Customer alerts Rackspace
A customer report prompted discovery.
[1]Operator explains extended outage
Raghuram described ongoing changes to infrastructure clusters while revising the restoration estimate.
[2]Restoration reported
BleepingComputer reported Rackspace’s restoration announcement.
[1]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]
Actors
- No threat actor group has been identified in the reviewed public evidence.
TTPs
- T1078 — Valid Accounts: leaked credentials enabled activity as legitimate Spot users. [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]
