• Sources: primary, discussion
  • Summary: FulcrumSec published a leak post and a 128 GB first release. It claims it exfiltrated TiDB Cloud data from early September to 2026-09-30 using GCP and Azure credentials committed in PingCAP repositories, and that it exported the control plane metadb every six hours for 22 days without being detected. The claimed data includes 180,046 tenant organisations, 42,612 active console API keys, 20.6 million SQL Editor statements, gateway logs with customer client IPs, 413 private repositories, and customer database credentials pasted into Jira tickets.
  • Why it matters: TiDB Cloud customers should rotate console API keys, cluster root passwords and any credentials ever shared with PingCAP support, then check access logs from client IPs they do not recognise.
  • Comments: HN commenters quote a PingCAP statement that says an external firm found no evidence the attacker ran commands or kept persistent access in the systems it reviewed, and no evidence that data stored in TiDB was affected. Commenters say this conflicts with the published material. Others point out the leak covers control plane metadata, SQL logs and connection strings, not bulk customer table data.