GitBook says AI-agent attack exposed infrastructure credentials, invalidates every customer API token

TLDR

• GitBook says an AI-agent attack gave an attacker access to some infrastructure credentials on 2 November.¹
• It replaced every credential and invalidated every customer's API tokens; customers must rotate connected secrets.¹³
• Integration tokens, Git Sync secrets, API tokens and Assistant visitor questions may have been accessed; no evidence content changed.¹

GitBook said on 3 November that it was the target of "a sophisticated, highly targeted attack using AI agents", and that the attacker gained unauthorised access to some of its infrastructure credentials at 19:00 CET on 2 November.¹ The company says it detected the attack immediately and acted to block further impact.¹ It then took the GitBook app and authenticated docs sites offline, while keeping publicly published content live on cached data for as long as possible.¹ Decrypt describes GitBook as a documentation platform widely used by cryptocurrency projects.²

GitBook says it blocked the attacker, closed the vulnerabilities involved, replaced every credential and secret across its infrastructure and invalidated every customer's API tokens.¹ Its investigation shows the attacker may have accessed integration tokens, Git Sync secrets, API tokens and questions that site visitors asked GitBook Assistant.¹ GitBook says it has found no evidence that any content in GitBook was modified.¹ crypto.news reports that the notice describes possible access and gives no customer count or volume of potentially exposed records.³ By its 16:21 CET update on 3 November, GitBook said the app, the API and published docs were available again, although a few services might still be degraded.¹

Customers are told to rotate any existing GitBook API tokens (all personal API tokens were revoked during the incident), rotate third-party tokens or secrets used to connect other tools to GitBook, rotate secrets used by published integrations, and re-authenticate the GitBook MCP server.¹ The guidance changed during the day. GitBook's earlier 13:15 CET notice said no action was required at that time and that instructions would follow once services were restored.¹³

How the attack worked is not yet public. Decrypt reports that GitBook has not explained how the attacker used AI tools, which AI systems were involved or how the credentials were obtained, and that the disclosure does not establish that GitBook's own AI products were responsible.² Altcoin Buzz also says how the attacker obtained the credentials and which AI systems were involved are not confirmed.⁴ GitBook says it is writing a full post mortem that will be published soon.¹ Downstream, Decrypt reports that PancakeSwap temporarily took its documentation offline as a precaution, saying its docs were not compromised and its app was not affected, and later said the docs were back online after moving off GitBook.² Altcoin Buzz, in an article published later, says whether PancakeSwap has permanently moved its docs is not confirmed.⁴ crypto.news separately reports that Trade.xyz identified unauthorised activity on its GitBook pages on the morning of 2 November, and says neither announcement established that the two incidents shared an attacker or entry point.³

Why it matters: the tokens and secrets that connect customers' documentation to other tools may have been exposed, so customers must rotate them even though GitBook has found no evidence that content was changed.¹