GitBook customers have a short to-do list after the documentation platform disclosed a security breach tied to AI agents. The company says an attacker gained access to some of its infrastructure credentials, and it is now asking users to replace digital keys connected to its service.
GitBook is widely used by cryptocurrency projects to publish guides, developer instructions, and technical explanations. The breach led decentralized exchange PancakeSwap to move its documentation to servers under its own control.
According to GitBook, the attacker gained unauthorized access at 19:00 Central European Time on November 2. The company described the incident as “a sophisticated, highly targeted attack using AI agents.”
GitBook said it detected the attack immediately and acted to block further impact. It has not said which AI systems were involved or how the credentials were obtained.
What GitBook Says Was Exposed
The company’s investigation found that the attacker may have accessed four types of data. These are integration tokens, Git Sync secrets, API tokens, and questions that site visitors asked GitBook Assistant.
Git Sync secrets connect documentation to code repositories. API tokens let software communicate with GitBook automatically, without a person logging in each time.
The inclusion of visitor questions means queries typed into GitBook’s AI assistant on customer sites may have been seen by the attacker. GitBook did not say how many questions or customers were affected.
GitBook said it has found no evidence that any customer content on its platform was modified. Its disclosure does not state that GitBook’s own AI products caused the intrusion.
To secure its systems, GitBook took its app and authenticated documentation sites offline. Public documentation stayed available through cached copies for as long as possible.
The Checklist for Customers
GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure. It also invalidated every customer’s API tokens on the platform.
Customers still have steps to complete. The first is to rotate any existing GitBook API tokens, since all personal API tokens were revoked during the incident.
Users must also rotate any third-party API tokens or secrets used to connect other tools to GitBook. Teams with published integrations that use secrets need to rotate those as well.
Anyone using the GitBook MCP server must re-authenticate it. MCP, or Model Context Protocol, is a system that lets AI assistants and other software connect to services like GitBook.
GitBook asked users to contact their organization’s admin for help with the process. It also pointed customers to its support team and its status page for updates.
PancakeSwap took its documentation offline as a precaution after news of the breach. The exchange said its “docs are not compromised” and that its app was not affected.
PancakeSwap reminded users that “docs never ask you to connect your wallet or approve tokens.” It later said its documentation was back online on its own infrastructure, with existing links still working.
As of 16:21 CET on November 3, GitBook said its app, API, and published docs were available again. Some services may remain degraded while restoration finishes, and the company says it will publish a full post mortem soon.
