Rackspace Spot Breach: Compromised Credentials And Kubernetes Secrets

Rackspace Spot breach: compromised credentials let attackers deploy unauthorized workloads and access Kubernetes secrets in customer clusters.

Threat AdvisoryLast updated

What Happened In The Rackspace Spot Breach

The Rackspace Spot breach is a credential compromise that reached customer Kubernetes environments. Rackspace warned customers that hackers breached its Rackspace Spot cloud platform using compromised credentials, according to BleepingComputer. The attackers were able to deploy unauthorized workloads and access Kubernetes secrets in customer clusters.

For an MSP, the cost is not abstract. A cloud platform breach can mean lost client trust, emergency engineering hours, and a recovery bill you cannot pass on. When a control plane is reached, the attacker may not need to break into every client system. One set of valid credentials can unlock workloads and secrets across multiple clusters.

The source does not say how many customers were affected, how long the attackers had access, or whether data was exfiltrated. It says compromised credentials were used. That is enough to start checking your own client base.

Timeline

  • 2026-11-21: BleepingComputer publishes a report that Rackspace warned customers about the breach of Rackspace Spot, including unauthorized workloads and access to Kubernetes secrets in customer clusters.

Who Is Affected

The source names the Rackspace Spot cloud platform, customer clusters, and Kubernetes secrets in customer clusters as affected.

If you are an MSP, check whether any client runs workloads on Rackspace Spot. That includes clients who use it directly and clients whose applications are hosted there by another provider. The source does not list affected industries, company sizes, or regions.

Kubernetes secrets often hold database passwords, API tokens, and cloud credentials. If an attacker accesses those secrets, they can move into other systems that trust those credentials. That is a general risk in any Kubernetes environment, not a claim about this specific incident beyond what the source states.

Why This Matters To MSPs

MSPs carry the blame when a client is hit. Even if the breach starts at a cloud provider, the client calls you first. The practical work is discovery, credential rotation, and recovery.

Credential compromise is a common path into cloud platforms. Attackers do not need a software flaw if they can buy, guess, or steal a valid login. General hardening, such as multi-factor authentication and least privilege, reduces that path but does not remove it.

You should also expect questions from clients. Have a clear answer about which clients use Rackspace Spot and what you are doing to verify their clusters.

Technical Details

Product: Rackspace Spot cloud platform. Versions: the source does not list affected versions. CVE: the source does not name a CVE. Attack vector: compromised credentials. The source states that attackers deployed unauthorized workloads and accessed Kubernetes secrets in customer clusters.

No other technical details about the incident are given in the source. Do not assume a software vulnerability is involved. The stated vector is credentials.

What MSPs Should Do

Treat this as a credential and secret exposure event. The steps below are standard practice for any cloud platform breach where credentials are involved.

  1. Find every client that uses Rackspace Spot. Check billing records, infrastructure inventories, and any cloud accounts you manage.
  2. Follow Rackspace's customer guidance. If Rackspace sent a notice, read it and act on the instructions.
  3. Rotate credentials for affected clusters. Change passwords, API keys, service account tokens, and any secrets stored in Kubernetes.
  4. Review Kubernetes audit logs. Look for unauthorized pods, deployments, jobs, or service accounts created around the time of the breach.
  5. Check for exposed secrets. Kubernetes secrets can hold database passwords, cloud keys, and tokens. Assume any secret in an affected cluster is compromised.
  6. Enable MFA and least privilege. For any cloud account, turn on multi-factor authentication and remove standing admin rights.
  7. Isolate and rebuild if needed. If you find unauthorized workloads, isolate the cluster and rebuild from known good images.
  8. Restore from clean backups. If data or configuration was changed, restore from a backup taken before the breach.
  9. Monitor for follow-on activity. Watch for new logins, new API calls, and unusual outbound traffic.
  10. Document and communicate. Keep a record for your client and for any insurance or regulatory needs.

How EnterProtect Helps

EnterProtect backup keeps clean restorable copies of client systems and data. When an attacker changes workloads or deletes resources, those copies are what you restore from.

EnterProtect recovery helps get a client running again after an incident. The goal is to bring back known good state, not to rebuild under pressure.

EnterProtect vulnerability scanning finds exposed versions as a standing practice. That helps MSPs reduce the window on known flaws in the environments they manage.

EnterProtect does not detect, block, or prevent this threat or attack. It is not a replacement for credential hygiene, logging, or incident response. It is the backup and recovery layer you rely on after a breach.

Frequently Asked Questions

What Is the Rackspace Spot Breach?

Rackspace warned customers that hackers breached its Rackspace Spot cloud platform using compromised credentials, according to BleepingComputer. The attackers were able to deploy unauthorized workloads and access Kubernetes secrets in customer clusters. The source does not say how many customers were affected or how long the attackers had access.

Was a CVE Assigned to the Rackspace Spot Breach?

No CVE is named in the source. The stated attack vector is compromised credentials, not a software vulnerability. If a CVE is published later, it would change the technical details.

What Are Kubernetes Secrets and Why Do They Matter After This Breach?

Kubernetes secrets are objects that store sensitive data such as passwords, API tokens, and certificates. If an attacker accesses them, they can use those credentials to reach other systems that trust them. The source says Kubernetes secrets in customer clusters were accessed.

What Should MSPs Do If a Client Uses Rackspace Spot?

Find out which clients use Rackspace Spot, follow any guidance Rackspace has sent, and rotate credentials for affected clusters. Review Kubernetes audit logs for unauthorized workloads and assume secrets in an affected cluster are compromised. Restore from clean backups if you find changes.

Does This Breach Affect All Rackspace Customers?

The source says the Rackspace Spot cloud platform, customer clusters, and Kubernetes secrets in customer clusters were affected. It does not say that all Rackspace customers are affected. Check with Rackspace and your own client inventory.

How Do Compromised Credentials Lead to Unauthorized Workloads?

Valid credentials can let an attacker log in as a legitimate user or service. From there, they can create pods, deployments, or jobs that run in the cluster. That is how the source describes the unauthorized workloads in this breach.

Sources

  • Rackspace Spot breach let hackers access customer Kubernetes secrets (Bleepingcomputer)

Check Your Clients' External Exposure

EnterProtect Vulnerability Scanning checks your clients' domains, addresses and exposed services. A critical CVE pages you like any critical alert, with the fix named.

Join the WaitlistJoin before it launches to get the Founding Partner Rate.

More Threat Advisories

See All Threat Advisories

Priya Nair

Partner Specialist

Priya Nair said: Hi, I'm Priya, EnterProtect's AI partner specialist. Ask me what a product does, what it costs, or what you'd keep per client.

Priya · Just now

Privacy