GitBook is a documentation platform widely used by cryptocurrency projects. The company disclosed that it experienced a security vulnerability involving an AI agent, which allowed attackers to gain access to certain infrastructure credentials, forcing the company to shut down services and revoke customer access tokens.
In today’s security disclosure, GitBook described the incident as a “complex, highly targeted attack carried out using AI agents.” The company stated that the attackers gained unauthorized access at 7:00 PM CET on November 2, and GitBook immediately detected the breach and began containment.
It is significant to note that AI agents are capable of performing a series of actions, interacting with software, and completing tasks with limited human oversight—making them potentially usable by attackers to automate parts of cyberattacks. Some AI agents can even act autonomously, sometimes contrary to their guiding principles, as demonstrated by experiments from OpenAI and Anthropic.
GitBook did not explain how the attackers specifically used these tools, which AI systems were involved, or how the credentials were obtained. Its disclosure also did not indicate whether GitBook’s own AI products were affected by the breach.
While ensuring the security of its infrastructure, the company has taken offline applications and documentation sites requiring authentication. At the same time, it has retained publicly accessible cached copies of documentation whenever possible, allowing visitors to continue reading previously saved versions of pages even when underlying systems are unavailable.
Another status update acknowledged that GitBook was experiencing an outage affecting its published documentation site and editor. By Tuesday afternoon, GitBook stated that its application, API, and published documents had been restored and were accessible, though some services may have remained degraded during the recovery period.
What information might be exposed, and why does it matter?
GitBook is essentially an online manual for software products. Cryptocurrency projects use such platforms to publish technical documentation, developer guides, and tutorials to help users understand operations ranging from connecting software to interacting with decentralized finance applications.
These documents themselves are typically public, but the systems maintaining them may be connected to private accounts and external services. These connections rely on credentials that should be kept confidential, and GitBook has indicated that some of these may have been exposed.
Its investigation found that potentially affected categories include integrated tokens, Git Sync keys used to connect documents with code repositories, and API tokens that allow software to communicate automatically with GitBook.
Cryptocurrency projects take preventive measures.
This incident has prompted a response from the crypto industry, as document websites are often key sources of official information.
After becoming aware of the incident, the decentralized exchange PancakeSwap temporarily took down its documentation, although it stated that its systems were not compromised.
PancakeSwap stated in a public announcement that its "documentation was not compromised, [and] the PancakeSwap application was unaffected." However, out of an abundance of caution, the platform took down the documentation and redirected visitors to its homepage.
PancakeSwap also reminds users that its documentation does not require any wallet transactions, warning that "documentation will never ask you to connect your wallet or approve tokens."
Subsequently, PancakeSwap announced that its documentation has been restored and has been migrated from GitBook to its own infrastructure, with existing documentation links remaining functional.
GitBook requires users to update their digital key.
GitBook states that it has blocked the attackers, patched the related vulnerability, rotated its infrastructure credentials, and invalidated customer API tokens. However, customers using GitBook to connect to other services still have work to do.
The company's guidance is first to "rotate any existing GitBook API token," meaning customers should replace their old access keys with newly generated ones.
GitBook also requires customers to rotate third-party API tokens and keys used to connect external tools to its platform, including credentials related to published integrations. Users of its Model Context Protocol (MCP) server must re-authenticate; MCP is a system that enables AI assistants and other software tools to connect to services like GitBook.