<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0" -->

---
title: Rackspace Spot breach let hackers access customer...
description: Hackers breached Rackspace Spot using leaked credentials, gaining access to Kubernetes secrets in customer clusters. The intrusion occurred on November 17,...
canonical: https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Rackspace Spot breach let hackers access customer Kubernetes secrets | daily.dev
og:description: Hackers breached Rackspace Spot using leaked credentials, gaining access to Kubernetes secrets in customer clusters. The intrusion occurred on November 17,...
og:url: https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0
og:image: https://api.daily.dev/og/posts/wOompxeU0.png
og:image:alt: Rackspace Spot breach let hackers access customer Kubernetes secrets
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Rackspace Spot breach let hackers access customer Kubernetes secrets

**[BleepingComputer](https://daily.dev/sources/bleepingcomputer)** · 3 min read · 0 upvotes · 0 comments

## Summary

Hackers breached Rackspace Spot using leaked credentials, gaining access to Kubernetes secrets in customer clusters. The intrusion occurred on November 17, 2026, between roughly 00:20 and 22:00 UTC, and Rackspace learned of it on November 18 after a customer report. Attackers could create pods, read Kubernetes Secrets, and list nodes and volumes, potentially exposing Spot API tokens and refresh tokens. Rackspace revoked tokens, rotated keys, removed unauthorized pods, and told customers to reissue API tokens and rotate credentials. The admin console had an extended outage as access was deliberately disabled while the environment was secured; service was fully restored on November 21.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.bleepingcomputer.com/news/security/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets>

## Questions this post answers

### What happened in the Rackspace Spot security breach?

An unauthorized party used leaked credentials to access parts of Rackspace Spot on November 17, 2026, between about 00:20 and 22:00 UTC. Attackers could act as legitimate users in some customer organizations, creating pods, reading Kubernetes Secrets, and listing nodes and volumes, potentially exposing stored passwords, tokens, and API keys along with Spot API and refresh tokens.

_Teams running Kubernetes on managed platforms follow breach disclosures like this on daily.dev to catch credential risks early._

### What should I do if my organization used Rackspace Spot during the November 2026 breach?

Reissue Spot API tokens, replace refresh tokens used in automation tools, download fresh Kubernetes configuration files, and rotate any credentials stored in cluster Secrets. Also review logs for databases, container registries, Git repositories, cloud storage, and third-party services dating back to November 17 to check for abuse of exposed credentials.

_Developers managing incident response checklists use daily.dev to keep up with concrete remediation steps like these._

### What indicators of compromise did Rackspace share for the Spot breach?

Rackspace identified the IP address 23.224.79.106, the IP range 23.224.0.0/15, and suspicious Kubernetes pod and object name prefixes including 'i1', 'glm-', and 'probe' as indicators of compromise tied to the attack on its Spot platform.

_Security engineers hunting for intrusion indicators track disclosures like this on daily.dev._

## Similar posts on daily.dev

- [How your cloud could get hacked: an analysis of a real-world vulnerability chain](https://daily.dev/posts/how-your-cloud-could-get-hacked-an-analysis-of-a-real-world-vulnerability-chain-fpulkynl5) · Securelist · 0 upvotes · 0 comments
- [Leaked Kubernetes Secrets: Impact Assessment and Mitigation Strategies](https://daily.dev/posts/leaked-kubernetes-secrets-impact-assessment-and-mitigation-strategies-bs3m8i7md) · GitGuardian · 0 upvotes · 0 comments
- [Understanding Current Threats to Kubernetes Environments](https://daily.dev/posts/understanding-current-threats-to-kubernetes-environments-fxdltzw1h) · Unit 42 · 1 upvotes · 0 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes)

[View this post on daily.dev](https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Rackspace Spot breach let hackers access customer Kubernetes secrets","url":"https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0"},"datePublished":"2026-11-21T23:01:35.924Z","dateModified":"2026-11-21T23:02:06.832Z","description":"Hackers breached Rackspace Spot using leaked credentials, gaining access to Kubernetes secrets in customer clusters. The intrusion occurred on November 17,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/30aa9e17dd9bc1d1930e22691ada1956?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/30aa9e17dd9bc1d1930e22691ada1956?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"BleepingComputer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"BleepingComputer","logo":"https://media.daily.dev/image/upload/s--as8nJ3qy--/f_auto,q_auto/v1774959951/logos/bleepingcomputer?_a=BAMAMiWQ0","url":"https://daily.dev/sources/bleepingcomputer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"BleepingComputer","item":"https://daily.dev/sources/bleepingcomputer"},{"@type":"ListItem","position":3,"name":"Rackspace Spot breach let hackers access customer Kubernetes secrets"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-woompxeu0#faq","mainEntity":[{"@type":"Question","name":"What happened in the Rackspace Spot security breach?","acceptedAnswer":{"@type":"Answer","text":"An unauthorized party used leaked credentials to access parts of Rackspace Spot on November 17, 2026, between about 00:20 and 22:00 UTC. Attackers could act as legitimate users in some customer organizations, creating pods, reading Kubernetes Secrets, and listing nodes and volumes, potentially exposing stored passwords, tokens, and API keys along with Spot API and refresh tokens. Teams running Kubernetes on managed platforms follow breach disclosures like this on daily.dev to catch credential risks early."}},{"@type":"Question","name":"What should I do if my organization used Rackspace Spot during the November 2026 breach?","acceptedAnswer":{"@type":"Answer","text":"Reissue Spot API tokens, replace refresh tokens used in automation tools, download fresh Kubernetes configuration files, and rotate any credentials stored in cluster Secrets. Also review logs for databases, container registries, Git repositories, cloud storage, and third-party services dating back to November 17 to check for abuse of exposed credentials. Developers managing incident response checklists use daily.dev to keep up with concrete remediation steps like these."}},{"@type":"Question","name":"What indicators of compromise did Rackspace share for the Spot breach?","acceptedAnswer":{"@type":"Answer","text":"Rackspace identified the IP address 23.224.79.106, the IP range 23.224.0.0/15, and suspicious Kubernetes pod and object name prefixes including 'i1', 'glm-', and 'probe' as indicators of compromise tied to the attack on its Spot platform. Security engineers hunting for intrusion indicators track disclosures like this on daily.dev."}}]}
```

