Bitget Claims TiDB Cloud Breach Only Involved Deprecated Public Data with No User Impact
Bitget's Greater China head, Xie Jiayin, stated that hackers breached and obtained data from PingCap's TiDB Cloud database product. Bitget had previously collaborated with TiDB solely for storing publicly available transaction log data, which did not involve any sensitive business data, and the partnership was officially terminated about two months ago.
The public data refers to information that all users can view in the transaction channel. This incident did not involve user data, nor was there any leakage of sensitive information such as passwords, thus having no impact on Bitget or its users.
PingCAP officially confirmed that between September 9 and October 7, unauthorized parties accessed some internal systems using stolen service account credentials and copied data and source code. External investigators found no evidence that the attackers executed commands or maintained persistent access in the reviewed production systems, nor did they find any impact on user data stored in TiDB.
The hacker group FulcrumSec claimed to have stolen about 10.6TB of data and listed companies including Bitget and Pionex, but some claims have not been independently verified. PingCAP has taken containment measures and hired an external cybersecurity firm to investigate.
It is common in the industry for companies to collaborate with multiple cloud and data infrastructure service providers to store different types of data. Bitget stated it will continue to monitor relevant developments with security partners and strengthen cybersecurity and supply chain protection.
The supply chain security incident prompted customer clarifications, driven by unauthorized access to PingCAP's internal systems; Bitget only stored public logs and has discontinued the service, with no impact on user assets or sensitive data, while the cloud database provider and related customers face pressure for credential rotation and ongoing monitoring.
Source: Public Information
ABAB AI Insight
Bitget previously stored some public transaction logs on TiDB Cloud, and the collaboration was terminated about two months ago; the model involves exchanges using external cloud databases to store non-sensitive public data, as historically, encryption platforms often rely on multiple infrastructure service providers rather than building all storage in-house.
PingCAP confirmed unauthorized access to internal systems and copying of data and source code, but the investigation found no impact on user data stored in TiDB; Bitget clarified that it only involved public logs, with no user privacy or password leakage, motivated by responding to the hacker list and isolating its own risks.
This is similar to the path taken by other cloud database or SaaS providers after supply chain incidents, where customers quickly clarify the scope of data; the investigation is ongoing, and customers need to rotate credentials and monitor, while the boundary between public and sensitive data becomes a key distinction.
Essentially, this represents supply chain risks under industry chain restructuring: outsourcing data storage means that incidents affecting a single service provider can impact multiple customers, with pricing and control partly remaining with customers regarding data classification and contract termination rights; Bitget mitigated impact through public data and discontinued services, while PingCAP and customers relying on its services must bear the costs of investigation and protection upgrades.
ABAB News · Cognitive Law
Public logs do not equal sensitive data; boundaries determine the scope of impact.
Discontinued services equate to keeping supply chain risks at bay.
After external database breaches, customer clarifications become the first line of defense.