Cyber

Rackspace Spot breach exposes customer Kubernetes secrets to hackers

Hackers breached the Rackspace Spot cloud platform using compromised credentials, deploying rogue pods and accessing Kubernetes secrets.

·2 min read
Rackspace Spot breach exposes customer Kubernetes secrets to hackers

Rackspace has notified customers of a significant security breach affecting its Rackspace Spot container management platform. Attackers utilized leaked credentials to access parts of the environment, deploy unauthorized workloads, and view sensitive Kubernetes secrets stored within client clusters.

  • Attackers abused compromised credentials to gain unauthorized access to Rackspace Spot.
  • Malicious actors were able to deploy rogue pods and read Kubernetes Secrets.
  • The Spot administration console was taken offline for several days to sanitize the environment.
  • Customers are instructed to reissue Spot API tokens and rotate all cluster credentials immediately.

Unauthorized Access to Kubernetes Secrets

Rackspace Spot is designed to let organizations manage and orchestrate containerized applications using Kubernetes. According to an advisory sent to affected customers, the unauthorized party gained access to the platform and impersonated legitimate users across several customer environments. The intrusion was initially identified after a report from an impacted user.

With valid credentials in hand, the intruders were able to enumerate cluster nodes and storage volumes, launch unauthorized pods, and read Kubernetes Secrets. Because Secrets typically store critical production data such as API access keys, authentication tokens, and database passwords, compromised organizations face potential secondary breaches across integrated services.

Read alsoChainalysis confirms data and live token breach for all customers

Administrative Console Outage and Remediation

Following the discovery, Rackspace revoked exposed tokens, terminated active sessions, deleted rogue pods, and applied tighter access controls. To safely remediate the infrastructure, the company completely disabled the Rackspace Spot administration console for several days, which temporarily prevented administrators from accessing their workloads.

Sirish Raghuram, co-founder of Platform9, which co-developed the platform, acknowledged the disruption in an online discussion, stating that shutting down the environment entirely was necessary to purge the threat and protect customers. Access to the management console was later restored after thorough sanitization.

Action Items for DevOps and Cloud Security Teams

Rackspace disclosed indicators of compromise, revealing that the unauthorized workloads and objects carried prefixes such as i1, glm-, and probe. Organizations utilizing Rackspace Spot must reissue all API and refresh tokens, download new Kubernetes configuration files, and immediately rotate any credentials stored within cluster Secrets.

Furthermore, security teams should inspect audit logs across connected databases, third-party APIs, and code repositories for any suspicious activity stemming from potentially compromised secrets.

Source: BleepingComputer

Related articles