1. News
  2. Alerts
  3. PingCAP · Data breach
AlertPingCAP · Data breach3 min read

Database company PingCAP confirms hackers stole code and customer data

PingCAP says hackers stole its source code and customer records, including names, emails and query text. TiDB Cloud users should swap access keys now.

By the Dashline deskSource: InfoQ
Database company PingCAP confirms hackers stole code and customer data
Photo: InfoQ
Act this week
What happenedPingCAP confirmed an attacker got into its internal systems and stole source code and customer-related records, including names, emails and query text.
Who is affectedCustomers of TiDB Cloud, PingCAP's hosted database service, and any business whose staff or data sit in those accounts.
What to do
  1. 1Replace your active TiDB Cloud management API keys, as PingCAP advises.
  2. 2Change any database passwords you ever shared with PingCAP support or in tickets.
  3. 3Be wary of emails about your account, billing or contract, even if they use real details.
  4. 4Ask your technical team to review recent logins and connections for anything unfamiliar.

PingCAP, the company behind the TiDB database, has confirmed that an attacker got into its internal systems and stole source code and customer-related data. If your business uses its hosted service, TiDB Cloud, PingCAP advises replacing your management access keys. Phishing emails that look real are the bigger risk to watch for.

What PingCAP has confirmed

PingCAP says the stolen records include user names, email addresses, and which organizations and projects people belong to. They also include text typed into its SQL editor, plus error messages. SQL is the language used to ask a database for information. Some records also contained organization, project and cluster identifiers.

An outside incident response firm found no sign that the attacker ran commands or kept access in the systems it reviewed. PingCAP also says it has no evidence that data stored inside customers' TiDB databases was affected.

What is only a claim

A cyber extortion group called FulcrumSec says it took 10.6 TB of data and 413 private code repositories. It also claims it took API keys, billing information and four years of connection logs. None of this has been independently verified. The group says it was inside for many weeks and that some of the credentials could open customer systems.

It also claims about 115,000 access key pairs were taken, with over 40,000 still active. It says it took roughly 1,800 database addresses, some with admin logins, and that engineers pasted customer passwords into support tickets. These are allegations, not findings.

Big brand names have been linked to the data, but that does not mean those companies were hacked. One crypto exchange named in the reports, Bitget, said it found no evidence its user data was exposed.

Who it affects

The main group is customers of TiDB Cloud, along with any staff or data tied to those accounts. Companies that run TiDB on their own servers, and only that, are not described as affected in the material so far. Even customers whose databases were untouched can be exposed, because support tickets and query history can hold sensitive details.

What to do

The alert box above lists the steps. The most urgent is replacing active TiDB Cloud management API keys, which are like passwords that let software control your account. Your technical team should also review recent logins for anything unfamiliar.

What to watch for

Security expert Kim Barthel of 42Sec warns that the leaked details could be enough for a convincing phishing email. That means a message that knows who your engineers are, when a contract renews and what you pay. Treat any unexpected email about your account, billing or contract with suspicion, even if it uses accurate details. Check with PingCAP through a known contact before clicking or replying.

The takeaway

If you use TiDB Cloud, replace your management API keys now and distrust unexpected emails about your account, billing or contract.

More articles

You should really read these.

Next step

Let’s talk