GitBook Security Incident Post-Mortem: Attack Targeted at Trade.xyz, SSO Vulnerability Led to Production Environment Compromise
TechFlame
2026-11-05 12:03
TechFlame2026-11-05 12:03
English
TechFlame news: GitBook released a post-mortem of the November 2 security incident, stating that attackers exploited a vulnerability in its single sign-on flow to forge an employee login session, then queried improperly configured GitHub App credentials within the organization, gained access to internal code repositories, obtained a Cloudflare API key, and ultimately used a service account to gain full production environment access.
GitBook disabled the relevant internal service account within hours to cut off the attack, taking the platform offline for approximately 16 hours and fully restoring it by 11:56 UTC on November 3. Attackers spent a cumulative total of about 3 hours and 25 minutes in the production environment. GitBook has rotated all infrastructure and hosted customer keys and revoked API tokens.
GitBook stated that current indicators suggest the attack targeted a single customer rather than the platform as a whole, and no evidence of tampering with other customers' content has been found. However, because attackers could reach customer data within the platform, GitBook has treated all customer data as potentially exposed, including API tokens, integration keys, session signing keys, assistant Q&A records, and GitHub and GitLab app permissions for authorized repositories. Billing information, passwords, and IP addresses were not affected.
GitBook said the speed and precision of the attack relied heavily on automation and AI. SlowMist Chief Information Security Officer 23pds shared the post-mortem, noting that the named target is Trade.xyz. Trade.xyz previously stated that the documentation anomalies stemmed from a compromise of GitBook's infrastructure, that no signs of compromise were found in its own infrastructure, and that it will migrate away from GitBook within days.