Skip to content
NewA calmer, faster ZeroHour

Rackspace Spot breach let attackers read customer Kubernetes secrets

Original title: Rackspace Spot breach let hackers access customer Kubernetes secrets

BleepingComputerby Lawrence Abrams ()2 min read1 · 1 read
AI summary · x-ai/grok-4.7Summaries by Vani AI

Leaked credentials were used on November 17 to create pods and read cluster secrets; Spot service was restored on November 21.

Rackspace told affected customers that an unauthorized party used leaked credentials to access parts of Rackspace Spot on November 17, 2026, between about 00:20 and 22:00 UTC. The attackers could act as legitimate users in some organizations, create pods, read Kubernetes Secrets, and list nodes and volumes, including Spot API and refresh tokens. Rackspace revoked tokens and sessions, removed unauthorized pods, rotated keys, and restored the administration console on November 21 after an extended outage. It has not said how many customers were affected or whether data was stolen.

Unconfirmed: Rackspace has not said how many customers were affected or whether customer data was stolen.

Key facts
  • Rackspace learned of the intrusion on November 18 after a customer report.
  • Customers must reissue Spot API tokens, replace refresh tokens, and rotate cluster Secrets.
  • IOCs include IP 23.224.79.106, range 23.224.0.0/15, and pod prefixes i1, glm-, and probe.
  • Platform9 co-developed Spot and said access was disabled to sanitize the environment.
Security assessment · AI, from the article

Impact: Read Kubernetes secrets and Spot API tokens

ProductAffected
Rackspace Spot—
What to do
  1. 1.Reissue Spot API tokens, replace refresh tokens, and download fresh Kubernetes configuration files.
  2. 2.Rotate credentials stored in cluster Secrets and review logs back to November 17.
  3. 3.Check for IP 23.224.79.106 and pod prefixes i1, glm-, and probe.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
ipv423.224.79.106ators of compromise associated with the attack: IP address: 23.224.79.106 IP range: 23.224.0.0/15 Suspicious Kubernetes pod and objec

From the original article

2 min read at bleepingcomputer.com

Rackspace warned customers that hackers breached its Rackspace Spot cloud platform using compromised credentials, allowing them to deploy unauthorized workloads and access Kubernetes secrets in customer clusters. [...]

BleepingComputer

By Lawrence Abrams · bleepingcomputer.com

Read the full article at BleepingComputer

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.