Investigating the PingCAP Security Incident

In October 2026, NebuSec responded to a security incident affecting PingCAP’s internal systems. Between September 9 and October 7, 2026, an unauthorized party used a compromised GitHub account and exposed cloud credentials to access PingCAP internal systems, obtain source code, and copy records from internal analytics, storage, and support environments. PingCAP engaged NebuSec to conduct an independent investigation, assess the scope of the exposed information, and support the containment and remediation efforts outlined in PingCAP’s October 19 security update.

Throughout our review of PingCAP’s production environments, NebuSec found no evidence of attacker command execution or persistence, and no evidence that data stored in customer TiDB databases was accessed. Instead, the intrusion was confined to internal source repositories and credential-based access to internal analytics, storage, and operational tools.

PingCAP began disabling the affected credentials on October 7, 2026—the same day it became aware of the activity. All critical credentials were invalidated that day. By October 14, all identified compromised credentials had been invalidated, broad cross-project permissions had been removed, and several vulnerabilities identified by NebuSec during a proactive review of the exposed source code had been patched and verified.

The threat actor gained initial entry to the PingCAP environment via a compromised GitHub account, exposing private repositories. Utilizing compromised keys and tokens harvested from those repositories and Terraform state, the attacker pivoted into Google Cloud, Jira, and the enterprise internal IM used for TiDB alerts.

Through Jira support tickets, the attacker harvested additional credentials previously shared by customers during routine support workflows. This included AWS keys, which ultimately allowed the intruder to reach several S3 buckets containing customers’ TiDB diagnostic data.

Over several weeks in September and early October, the attacker used stored keys for Google Cloud service accounts, eventually exporting tables from PingCAP’s BigQuery data warehouse on September 23–24 and downloading data from Cloud Storage. The data taken includes copies of the TiDB Cloud control-plane metadata, customer SQL editor history, CRM records and billing data, along with source code, Jira issues and the chat history of the enterprise internal IM.

Based on the evidence available, the attacker did not access live customer TiDB clusters.

Figure 1: Credential access and data collection (UTC).

NebuSec correlated cloud activity logs, the incident file inventory and reviewed data samples to identify the exposed data and sources summarized below.

Table 1: Exposed data mapped to its source systems.

The TiDB Cloud API-key values in the exported table were encrypted, and the encryption key was not exposed. Without that key, the encrypted values could not be decrypted to recover usable API credentials.

Customer-related information was copied from PingCAP’s internal analytics, storage, and support systems. That exposure is distinct from accessing or extracting rows directly from production customer TiDB databases.

NebuSec supported PingCAP in containing the intrusion, identifying exposed credentials and verifying remediation. The response combined access revocation with measures to keep legitimate business services running.

NebuSec confirmed PingCAP has disabled compromised service accounts, revoked exposed keys, replaced affected identities and tightened access permissions. All identified compromised credentials were invalidated and the identified unauthorized access paths were closed.

NebuSec also reviewed PingCAP’s exposed data and code repositories, scanned for additional exposed credentials, and worked with PingCAP on credential rotation and verification.

Because the attacker obtained copies of internal source code, NebuSec conducted a focused security review of the affected services to look for flaws that an attacker with source-code access might try to exploit later. NebuSec reported four vulnerabilities with the potential to affect production data. PingCAP patched all four, and NebuSec retested each fix to verify remediation. A retrospective review of production logs found no evidence that any of these vulnerabilities had been exploited prior to being fixed.

Alongside these fixes, PingCAP expanded its logging and perimeter defenses, enabling additional Cloud Storage access logging in the affected project. PingCAP also confirmed that all 16 internet-facing services identified during the review were protected by a web application firewall (WAF). Broader credential rotation, cross-project IAM reviews and expanded secret scanning remain ongoing.

Our testing found that the TiDB Cloud API keys in the exported table are encrypted and could not be used directly. This does not apply to credentials recovered from support materials, including the AWS keys described above. We recommend that customers replace active TiDB Cloud management API keys now, following PingCAP’s published rotation guidance.

Customers who shared credentials with PingCAP support are advised to rotate them.

PingCAP is determining customer-specific impact and will contact affected customers directly. Customers should follow the published precautionary steps without waiting for individual notice.

For engineering and security teams, three practices can help reduce exposure and strengthen incident response:

The attacker used the following IP addresses to access PingCAP’s cloud environment between September 9 and October 7, 2026.

The following techniques and cloud operations were observed during the investigation. Because these APIs and tools also have routine administrative uses, their investigative value comes from correlating them with anomalous source IPs, user agents, and access patterns.

All event times are UTC. Findings reflect the state of the investigation as of October 21, 2026. Internal resource identifiers and credential values have been omitted.