Rackspace Spot Breach: Leaked Credentials Let Attackers Read Customers' Kubernetes Secrets for 22 Hours — Rotate API Tokens, Kubeconfigs and Every Stored Secret

Cyber · 2026-11-22 · By H.A

Rackspace Spot Breach: Leaked Credentials Let Attackers Read Customers' Kubernetes Secrets for 22 Hours — Rotate API Tokens, Kubeconfigs and Every Stored Secret

Attackers used leaked credentials to act as legitimate users in some Rackspace Spot customer organisations on 17 November, creating pods and reading Kubernetes Secrets, and customers must now rotate every token and secret.

Rackspace has told customers that attackers used leaked credentials to get into its Rackspace Spot managed Kubernetes platform. For most of a day, the intruders could act as legitimate users inside some customer organisations, start their own pods and read the Kubernetes Secrets stored in those customers' clusters. The company's customer notice says the unauthorised access ran on 17 November 2026 from about 04:20 Mauritius time (00:20 UTC) until about 02:00 Mauritius time on 18 November (22:00 UTC on 17 November). Rackspace only learned of it on 18 November, when a customer reported it.

The admin console then stayed down for days while the platform was cleaned up, so affected customers could not rotate the credentials they now had to assume were exposed. Rackspace says service was fully restored on 21 November. It has not said how many customers were affected or whether data was taken from them.

What Happened

Rackspace Spot sells spare cloud capacity through an auction and runs managed Kubernetes clusters (called cloudspaces) on top of it. It is popular with developers, start-ups and teams running batch or CI workloads cheaply. According to the notification sent to customers, "an unauthorized party used leaked credentials to access parts of Rackspace Spot."

Rackspace has not said whose credentials leaked or how. It has not said whether they belonged to a customer, a staff member or a platform service account, or where they were exposed. That matters, because the access the attacker got was broad. They were not confined to one tenant. They could act as legitimate users across "some customer organisations".

Rackspace's response, as described to customers, was to:

An executive at Platform9, which built Spot together with Rackspace, explained the outage in a public community thread. He said the team chose to shut off all access and "sanitize the entire environment" to protect users, rather than leave the console running during the investigation.

Technical Details

According to the notice, the attacker could do the following inside affected organisations:

The ability to read Secrets is the most serious part. By default, a Kubernetes Secret is only base64-encoded in the API, not encrypted, so anyone who can read it gets the plain value. A single cluster often holds the keys to a whole company's systems: the production database, the container registry, the Git deploy key, the S3 bucket and the payment or email provider. Leaked Spot refresh tokens could also have let an attacker get back in after the first sessions were killed, which is why Rackspace is asking customers to replace them as well.

Rackspace shared indicators with customers. Defanged:

Rackspace has not said what the unauthorised pods actually did. Unexpected pods on a hijacked cluster are often used for cryptomining, scanning or stealing more credentials, but that has not been confirmed here.

Who Is Affected

Any Rackspace Spot customer whose organisation was accessed on 17 November should treat every secret in those clusters as compromised. Rackspace has notified the affected organisations directly. If you use Spot and are unsure whether you were affected, contact Rackspace support. Given that the attacker could also read API and refresh tokens, it is safer to rotate anyway.

Rackspace's other managed hosting and cloud services are not mentioned in the notice.

What To Do Now

Rackspace asks affected customers to do the following, and they are good practice for any Spot user:

On the clusters themselves, look for workloads you did not deploy and for changed Secrets. The read-only commands below are a starting point:

# Pods whose names match the reported prefixes, across all namespaces
kubectl get pods -A -o wide | grep -E '\s(i1|glm-|probe)'

# Recently created pods, newest last
kubectl get pods -A --sort-by=.metadata.creationTimestamp

# Secrets and when they were last changed
kubectl get secrets -A -o custom-columns='NS:.metadata.namespace,NAME:.metadata.name,CREATED:.metadata.creationTimestamp'

If you export Kubernetes audit logs, search them for get and list requests on secrets and create requests on pods during the 17 November window. Use this incident to get a full list of where your secrets live, so that next time rotation takes minutes, not days. Longer term:

Why It Matters

The incident shows a risk of managed Kubernetes that is easy to forget: whoever controls the platform's identity layer can read your Secrets. Customers did nothing wrong here. One set of leaked credentials at the provider was enough to reach the Secrets in their clusters. Shutting the console during cleanup also locked customers out of the console they needed to rotate those credentials.

Teams can't control a provider's credential hygiene, but they can limit the damage. Keep long-lived keys out of cluster Secrets where possible, have a tested rotation runbook ready, and keep logs for databases and cloud services long enough to look back at least a week. Rackspace still has to say how the credentials leaked, how many organisations were affected and whether any data left their clusters.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.