Huo Xing Cai Jing reports that on November 5, GitBook released a post-mortem of the security incident on November 2, stating that the attacker exploited a vulnerability in its single sign-on process to forge employee login sessions, thereby querying improperly configured GitHub App credentials within the organization, gaining access to internal code repositories, and obtaining Cloudflare API keys. The attacker ultimately used a service account to acquire full production environment privileges. GitBook disabled the relevant internal service accounts within hours to halt the attack, resulting in a platform outage of approximately 16 hours, with full restoration achieved at 11:56 UTC on November 3. The attacker remained in the production environment for a total of approximately 3 hours and 25 minutes. GitBook has rotated all infrastructure and customer-hosted keys and revoked all API tokens. GitBook stated that current evidence suggests the attack targeted a single customer rather than the platform as a whole, with no indication that other customers’ content was altered. However, since the attacker had access to customer data within the platform, all customer data is being treated as potentially exposed, including API tokens, integration keys, session signing keys, assistant Q&A logs, and GitHub and GitLab app permissions for authorized repositories. Billing information, passwords, and IP addresses were unaffected. GitBook noted that the speed and precision of the attack heavily relied on automation and AI. 23pds, Chief Information Security Officer at SlowMist, shared this post-mortem, indicating that the targeted entity was Trade.xyz. Trade.xyz previously stated that the document anomalies originated from a compromise of GitBook’s infrastructure, with no signs of compromise to its own infrastructure, and plans to migrate away from GitBook within several days.
GitBook Security Incident: Attack Targeted Trade.xyz; SSO Vulnerability Led to Production Compromise
MarsBitShare
On November 2, 2026, GitBook announced a security breach after attackers exploited a vulnerability in its SSO system to impersonate employees and gain access to internal credentials. The vulnerability exposed unauthorized access to code repositories and Cloudflare API keys, granting full production access for over three hours. GitBook contained the incident by disabling compromised accounts and restoring services by 11:56 UTC on November 3. The attack appeared targeted at Trade.xyz, with no evidence of impact on other clients. As a precaution, GitBook revoked all API tokens, integration keys, and other secrets. Trade.xyz confirmed no breach on its end and plans to migrate away from GitBook shortly.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.
