The attacker could act inside affected clusters

According to a Rackspace notification obtained by BleepingComputer, an unauthorized party used leaked credentials to access parts of Rackspace Spot on 17 November, between about 00:20 and 22:00 UTC. Rackspace said the party could act as legitimate users in some customer organizations: creating pods, reading Kubernetes Secrets and listing nodes and volumes.

Rackspace told affected customers it had revoked tokens and sessions, removed unauthorized pods and rotated keys. It advised them to reissue Spot API and refresh tokens, download fresh Kubernetes configuration files and rotate credentials stored in cluster Secrets. The public report does not establish how many customers were affected or whether each possible Secret read occurred.

Treat a readable Secret as potentially exposed

A Kubernetes Secret may hold credentials for systems outside the cluster. For a notified customer, identify those downstream systems before deciding that rotation is complete.

Follow each credential to where it works

  1. 1

    Confirm whether your organization was affected. Review Rackspace's customer notification and account guidance. Preserve the incident window and the cluster identities it identifies.

  2. 2

    Replace access material. Reissue Spot API and refresh tokens, obtain fresh kubeconfigs and rotate credentials stored in Kubernetes Secrets. Include automation that holds copies of those tokens.

  3. 3

    Trace downstream use. Inspect cluster audit records for unexpected pods or reads. Check databases, registries, Git services, storage and other destinations unlocked by those Secrets for suspicious access from 17 November onward.

Rotation is a map, not a single button

The practical task is to connect each potentially exposed Secret to the service that accepts it, then replace it and check whether it was used. A public copy of the Rackspace customer notice was not available for independent inspection; the incident details here are attributed to the notice excerpts reported by BleepingComputer. Customers should follow their direct Rackspace guidance for their own scope.