GitBook reports targeted attack involving AI agents

GitBook said an attacker gained unauthorized access to some of its infrastructure credentials at 19:00 CET on November 2.[1] It reported detecting the attack immediately and acting to block further impact.[1] The company said it blocked the attacker and closed the vulnerabilities involved.[1] To check that its infrastructure was secure, GitBook took its app and authenticated documentation sites offline.[1] It kept publicly published content available as long as possible by serving cached data.[1]

GitBook told customers to rotate existing GitBook API tokens, noting that it had revoked all personal API tokens during the incident.[1] It also invalidated every customer’s API tokens on its platform.[1] Customers were asked to rotate third-party API tokens and secrets used to connect other tools to GitBook, and to rotate secrets used by published integrations.[1] Users of GitBook’s MCP server were told to authenticate it again.[1] GitBook advised customers who need help with these security steps to contact their organization administrator.[1] Teams can use this list to check which credentials and connections apply to their setup.

GitBook said it found no evidence that content stored in GitBook was modified.[1] It later reported that its app, API and published documentation were available again, while some services might be degraded during restoration.[1] The company’s notice names integration tokens, Git Sync secrets and API tokens, and refers to questions visitors asked GitBook Assistant.[1] GitBook said it was preparing a full post-mortem for publication soon.[1] Until that account is available, customers should distinguish the confirmed remediation steps from unanswered questions about the incident.

GitBook describes its platform as a documentation service used by software and Web3 projects.[2] Decrypt reported that crypto exchange PancakeSwap temporarily took its documentation offline before moving it away from GitBook.[3] That reported response illustrates why documentation availability and credential management matter to teams that rely on third-party platforms. The evidence does not establish that PancakeSwap’s action was a response to a specific compromise of its credentials or content.