how it happened
- whoan intrudera compromised GitHub account; how is unknown
- the targetkeys in Git historyservice-account keys in commits and plaintext Terraform state
- thencloud data warehouserights reached across cloud projects
- the resultinternal and customer data copied6,458 tables exported, per NebuSec
- how it stoppedcredentials revokedfrom 7 October 2026
what everyone assumed
No PingCAP statement describes what the company believed beforehand, so the belief in the title is an inference from what the investigation found. It is a common and reasonable one. A private repository feels like a locked room: only employees can see it, access goes through the company’s code-hosting accounts, and the cloud keys used to build infrastructure seem to sit inside the same perimeter as the infrastructure itself. A key that was removed in a later commit feels gone. A Terraform state file feels like plumbing, a record the tool keeps for itself.
what happened
PingCAP builds TiDB, a distributed SQL database, and runs it as a cloud service. Its incident report of 19 October 2026 says that between 9 September and 7 October 2026 an unauthorized party used stolen service account credentials to reach internal systems, copy data and obtain source code.
The investigator PingCAP engaged, NebuSec, published the mechanism on 21 October 2026:
- The entry point was one GitHub account. NebuSec says the intruder got in through a compromised GitHub account that exposed private repositories. No source says how that account was compromised, whose it was, or whether it had a second factor.
- The keys were in the history. NebuSec’s technique table records “Service account private keys retained in Git commit history” and in plaintext Terraform state files, plus a plaintext Jira API token and a bot key in code or configuration.
- The keys became identities. NebuSec records direct sign-in with eight compromised Google Cloud service accounts. PingCAP says that by 10 October it had removed excessive permissions between cloud projects, which means those identities reached further than one project.
- The warehouse left in two days. NebuSec reports bulk exports from the BigQuery data warehouse on 23 and 24 September 2026, writing 6,458 tables to Cloud Storage, then downloads with an ordinary sync tool on several days up to 5 October.
- Support tickets held more keys. Through Jira, NebuSec says, the intruder collected credentials customers had shared during routine support, including AWS keys that reached storage buckets holding customers’ TiDB diagnostic data. PingCAP’s own 19 October report still describes the attacker’s claims about credentials in support materials as not verified; the investigator’s report treats them as fact, and the CEO’s note of 23 October asks customers to act as if they were.
PingCAP and NebuSec both say they found no evidence that the intruder ran commands or kept access in production systems, or touched data stored in customers’ TiDB databases. What was copied came from internal analytics, storage and support systems: account records, SQL editor history, contacts, contracts, billing, support tickets, chat history and source code, per NebuSec’s table. NebuSec also notes that the cloud operations used are the same ones administrators run every day, which is why they blended in.
step by step
- infrastructure code lives in private repositoriesService-account private keys stay in Git commit history and plaintext Terraform state files, per NebuSec.
- 9 September 2026one GitHub account opens the repositoriesThe keys found there work, and the intruder signs in to Google Cloud as eight service accounts.the assumption breaks here
- 23 and 24 September 2026the data warehouse is exportedNebuSec counts 6,458 tables written to Cloud Storage, followed by downloads into early October.
- 7 October 2026PingCAP becomes awareIt starts disabling credentials the same day and removes cross-project permissions by 10 October.
- 19 to 23 October 2026reports and a customer instructionThe investigator's report names the GitHub entry point, and the CEO tells customers to rotate anything they shared with support.
how it surfaced
PingCAP says it became aware on 7 October 2026 and began disabling the affected credentials that day. Neither PingCAP nor NebuSec says how it noticed, or why about a month of discovery, exports and downloads went unflagged. What the record does show is that PingCAP enabled additional storage access logging in an affected project on 10 October and lists alerts for unusual access and large data exports as work still to do.
The costs on the record so far:
- Customers had to act. On 20 October PingCAP asked every customer to replace active TiDB Cloud management API keys and to watch for targeted phishing, since contacts and billing details were in the exported records. The keys in the exported table were encrypted and NebuSec says the encryption key was not exposed.
- Support credentials became the customers’ problem. The CEO’s note of 23 October tells customers to “Rotate anything you have shared with PingCAP support”, including keys, connection strings and logs with secrets in them.
- Japan counted. PingCAP’s Japanese notice, amended on 21 October 2026, says up to about 50,000 personal records in Japan leaked and that the company reported to law enforcement and to supervisory authorities. No global count has been published.
- The attacker’s numbers are bigger and unproven. A group calling itself FulcrumSec claimed 10.6 TB of stolen data, as reported by InfoQ on 25 October 2026, which notes the claims have not been independently verified.
- Four flaws found in the stolen code. NebuSec reviewed the exposed source code, reported four vulnerabilities on 12 and 13 October, and PingCAP fixed them by 14 October. NebuSec found no evidence they were exploited before the fix; PingCAP’s 19 October report still lists that check as open.
The contrast with Toyota’s key on a public GitHub repository is the point: here the repositories were private, and that held only until one account fell. Klue in June 2026 is the same family, an old GitHub credential at a vendor reaching customers’ systems. The support-ticket half of this case is the lesson of Okta’s support files in 2023.
A private repository is as private as its least protected account, and a key in its history works until someone rotates it.
The service accounts guide covers why these keys never expire and nobody owns them, GitHub as your identity surface covers who can read your repositories today, and the log export guide covers whether a two-day bulk export would show up anywhere you look.
picture it at a company like yours
The company here is made up. The other two paths are not: they happened, and each links to the story.
- in this storythe day it mattersOne developer's code-hosting login is taken, and the history is read in an afternoon.what it costs youThe key still works, it reaches more than one project, and your customer records leave quietly for weeks.
- or it goes like thisit happenedMicrosoft AI data exposure, 2023howA share link meant for one folder opens the whole storage account.what leavesbackups, passwords and private messageswho ends up with itanyone who finds the link
- or it goes like thisit happenedPower Apps misconfiguration, 2021howA default on a no-code app leaves its data readable without logging in.what leavespersonal records you collectedwho ends up with itanyone who looks
sources
- PingCAP: Security Incident Report: Unauthorized Access to PingCAP Cloud Resources, 19 October 2026
- PingCAP: Security Update, Customer Actions, 20 October 2026
- NebuSec: Investigating the PingCAP Security Incident: Credential Exposure and Cloud Data Collection, 21 October 2026
- PingCAP: A Note from Our CEO on Our Security Incident, 23 October 2026
- PingCAP Japan: notice of information leak due to unauthorized access (in Japanese), amended 21 October 2026
- InfoQ: PingCAP Breach Exposes Customer Records and Source Code, 25 October 2026
your turn
what you can do about it
this week
Scan the full history of your private repositories for cloud keys, and rotate every one still valid.
Ask whoever runs your code hosting to run a secret scan across the whole commit history of every private repository, including infrastructure folders and any Terraform state files, and to list each key with the account it belongs to and what that account can reach. Rotate every key that still works, even the ones deleted in a later commit, because PingCAP's keys sat in history and in state files. Then search your support tickets with vendors for keys you pasted in. If one GitHub login at your company were taken tomorrow, which cloud accounts could it sign in as?
go deeper
if you're not sure where to start
Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.
open the checklist →
