GitBook said attackers used AI agents to access some infrastructure credentials at 1 p.m. EST on November 2. The company detected and blocked the attack, temporarily suspending some services. Potentially exposed data includes integration tokens, Git Sync secrets, API tokens and questions submitted to GitBook Assistant. GitBook said it found no evidence that content had been modified.
Why it matters
Crypto projects rely on documentation platforms to connect users with project guidance and services. The incident also prompted trade[XYZ] to report unauthorized activity involving its GitBook documentation and PancakeSwap to take its docs offline as a precaution.
Market impact
GitBook rotated infrastructure credentials and secrets, revoked all customer API tokens, and advised users to rotate third-party credentials and re-authenticate GitBook MCP connections. Its app, API and published docs were accessible again by 10:21 a.m. EST on November 3, though some services remained degraded. GitBook plans to publish a full post-incident report.
Source: [Security incident | November 2026](https://www.gitbook.com/status/security-incident-2026-11-03)
Frequently asked questions
-
What information may have been exposed in the GitBook incident?
Potentially exposed data includes integration tokens, Git Sync secrets, API tokens and visitor questions submitted to GitBook Assistant.
-
Did GitBook find evidence that attackers changed documentation?
GitBook said it found no evidence of content modification.
-
What steps did GitBook take after blocking the attack?
It rotated infrastructure credentials and secrets, revoked all customer API tokens, and advised users to rotate third-party credentials and re-authenticate GitBook MCP connections.
-
Why did PancakeSwap take its documentation offline?
PancakeSwap took its documentation site offline as a precaution following the GitBook security incident and redirected documentation links to its official homepage.
-
Were GitBook's services available again after the incident?
By 10:21 a.m. EST on November 3, GitBook's app, API and published docs were accessible again, though some services remained degraded.
WuBlockchain