IPCRIME | November 22, 2026. Rackspace has warned customers that someone using leaked credentials accessed parts of its Rackspace Spot managed-Kubernetes service, with potential exposure of application credentials and other secrets inside affected clusters. A customer notification obtained by BleepingComputer places the unauthorized activity on November 17, between approximately 00:20 and 22:00 UTC. Rackspace says it learned of the issue after a customer report on November 18. The incident was followed by an extended shutdown of the Spot administration console.
A stolen login became cluster-level access
According to Rackspace’s notice, the intruder operated with permissions associated with legitimate users in some customer organizations. That allowed the creation of Kubernetes pods, the listing of nodes and storage volumes, and reading Kubernetes Secrets. Secrets are Kubernetes objects used to store credentials such as passwords, service tokens and API keys. They should be protected by tight access policies rather than their name alone.
Rackspace warned that an unauthorized user could have read any Secret accessible to an affected user, as well as Spot API and refresh tokens held by that user. This is serious but precise language matters: accessibility is not proof that every possible Secret was copied or subsequently abused. Rackspace had not provided a verified affected-customer count or total stolen-data volume in the public reporting reviewed here.
The console outage slowed customer response
The Spot administration console was unavailable for an extended period while the service was sanitized, making it harder for customers to manage clusters or rotate credentials through the normal interface. Platform9, which co-developed Spot, described the shutdown as a protective decision. Rackspace announced restoration on November 21; that does not by itself mean that every external database password or cloud API token held by customers was replaced.
Response actions and next steps
The notification says Rackspace revoked affected sessions and tokens, removed unauthorized pods, rotated platform keys and strengthened monitoring. It told affected customers to issue fresh Spot API tokens, replace automation refresh tokens, download new Kubernetes configurations and rotate credentials stored as cluster Secrets.
- Identify which Secrets were readable by affected identities, including those used by automated deployments.
- Rotate exposed database passwords, registry credentials, cloud access keys and API tokens at the destination service, not only in Kubernetes.
- Replace compromised kubeconfig files and credentials in authorized CI/CD tools; revoke outdated access where practical.
- Review logs for databases, Git hosting, container registries, cloud storage and third-party integrations from November 17 onward.
- Preserve suspicious Kubernetes object details and account-activity records before cleanup where evidence preservation is necessary.
Why downstream services matter
A cluster secret can grant access to another system whose data is not hosted at Rackspace Spot. Consequently, possible exposure of a token creates a reason to review the downstream service, not proof that the downstream service was actually entered. Equally, reissuing one platform login without rotating accessible third-party credentials may leave lingering risk. Cloud platforms and customers each control different parts of this chain.
What remains unknown
Neither the initial source of the leaked credentials nor the full number of affected customers has been publicly established. The reviewed notice does not prove that all customer clusters were accessed or that every available secret was downloaded. No reliable public attribution identifies a ransomware operation or individual responsible. This is a documented unauthorized-access incident with an uncertain final scope.
Sources and methodology
BleepingComputer — November 21 report based on Rackspace’s customer notification; Kubernetes official documentation on Secrets. The notification was obtained by the reporting outlet rather than published as a complete public forensic report. IPCRIME has not accessed any customer Kubernetes cluster or validated private credentials. This article separates observed access, possible data exposure and outstanding investigative questions.
[…] 22, 2026 · 2:34 AMGL.iNet Confirms Cloud-Flaw Malware Infections on Some Routers and KVM DevicesPOSTEDNov 22, 2026 · 2:33 AMRackspace Spot Intrusion Put Customer Kubernetes Secrets at RiskPOSTEDNov 21, 2026 · 6:17 PMSonicWall Warns Unsupported Gen 6 Firewalls Will Receive No Further […]