A documentation service relied upon by numerous cryptocurrency ventures, GitBook revealed that on November 2 it suffered a focused cyber intrusion employing AI agents, resulting in an attacker gaining unauthorized entry to certain infrastructure credentials. The company detected the breach immediately and moved to contain it, revoking personal API tokens and urging customers to replace connected credentials.

The incident matters because GitBook hosts documentation that serves as official instructions for crypto projects, and the data potentially compromised spans API tokens, integration secrets, and queries users submitted to the platform's AI assistant. The breach forced the company to shut down services temporarily and has already prompted at least one major crypto exchange to migrate its documentation away from the platform.

Attack Timeline and Detection

In a security disclosure published Wednesday, GitBook characterized the event as a sophisticated and highly targeted operation utilizing AI agents. According to the company, the attacker achieved unauthorized access at 7 p.m. Central European Time on November 2, and GitBook said it detected the intrusion immediately and moved to contain it.

TokenPost reported the access began at 1 p.m. ET November 2, corresponding to 2 a.m. Beijing time November 3. The company has yet to detail precisely how the attacker deployed these tools, which AI systems were involved, or the method used to obtain the credentials. The disclosure does not indicate that GitBook's own AI products caused the breach.

AI agents differ from conventional chatbots that merely answer queries; they can execute sequences of actions, engage with software, and complete tasks with minimal human oversight, which makes them potentially valuable to attackers seeking to automate portions of a cyberattack. Some are even capable of acting autonomously and against their guidelines, as experiments by OpenAI and Anthropic have shown.

Exposed Credentials and Customer Impact

GitBook's probe uncovered several categories that may have been affected, such as integration tokens, Git Sync secrets that link documentation to code repositories, and API tokens enabling automated software communication with the platform. The company said some credentials that are supposed to remain secret may have been exposed.

The potentially exposed information includes API tokens, integration secrets, and questions submitted to GitBook's AI assistant, according to Decrypt. TokenPost reported the compromised data encompassed integration tokens, Git Sync keys, API tokens and queries visitors sent to the AI assistant. GitBook said it found no evidence that hosted content was modified.

While securing its infrastructure, the company took offline its application and documentation sites requiring authentication. It maintained access to publicly available documentation via cached copies for as long as possible, so visitors could keep reading previously saved page versions even when the underlying systems were down. A separate status notice acknowledged downtime affecting published documentation sites and the editor.

GitBook announced Tuesday afternoon that its application, API, and published documentation were back online, though some services might stay degraded during recovery. TokenPost reported service was restored at 10:21 a.m. ET November 3.

GitBook Response and Remediation

GitBook said it blocked the attacker, fixed the vulnerabilities involved, swapped out its own infrastructure credentials, and invalidated customer API tokens. The company revoked personal API tokens and urged customers to replace connected credentials.

Customers using GitBook with other services still face additional tasks. The company's guidance starts with rotating any existing GitBook API tokens, which means replacing old digital access keys with newly generated ones. GitBook also told customers to swap out third-party API tokens and secrets used to link external tools to its platform, including credentials tied to published integrations.

Users of its Model Context Protocol, or MCP, server must authenticate again. MCP is a system that allows AI assistants and other software tools to connect to services such as GitBook. TokenPost reported the company told users to rotate GitBook and third-party API tokens and keys, then reauthenticate the MCP server.

PancakeSwap Migration and Industry Response

The incident has prompted a response from the cryptocurrency industry, where documentation websites often serve as an important source of official instructions. Decentralized exchange PancakeSwap temporarily disabled its documentation following news of the incident, although it said its own systems had not been compromised.

In a public statement, PancakeSwap said its docs are not compromised and the PancakeSwap app is not affected. The exchange nevertheless took its documentation offline as a precaution and redirected visitors to its homepage. PancakeSwap reminded users that its documentation does not require them to perform wallet transactions, warning that docs never ask you to connect your wallet or approve tokens.

PancakeSwap subsequently announced that its documentation was back online after being moved from GitBook to infrastructure under its own control, with existing documentation links continuing to work. TokenPost reported PancakeSwap temporarily took down its GitBook-hosted documentation after the incident.

Platform Role in Crypto Ecosystem

GitBook is effectively an online instruction manual for software products. Cryptocurrency projects use platforms like it to publish technical explanations, developer instructions, and guides that help users understand everything from connecting software to interacting with decentralized financial applications.

The documents themselves are often public, but the systems that maintain them can connect to private accounts and external services. Those connections depend on credentials that are supposed to remain secret. GitBook hosts documentation used by crypto projects, placing publishing credentials and visitor interactions within the scope of the response.

Coinfomania reported that GitBook serves as a crucial documentation platform for various crypto projects, providing resources for developers and users alike. The platform's significance in the crypto ecosystem makes it a target for malicious attacks, according to the outlet.

Conclusion

GitBook has restored its core services and blocked the attacker, but the company has not disclosed how the AI agents were used or which systems were involved. Customers must still rotate their API tokens and reauthenticate MCP connections to secure their integrations. PancakeSwap has already migrated its documentation to infrastructure under its own control. GitBook is preparing a full post-incident report, according to Coinfomania.

Frequently Asked Questions

What happened in the GitBook AI agent attack on November 2?

GitBook disclosed a targeted cyberattack involving AI agents that gave an attacker unauthorized access to some of its infrastructure credentials on November 2. The company detected the intrusion immediately and moved to contain it, revoking personal API tokens and urging customers to replace connected credentials.

What credentials were potentially exposed in the GitBook breach?

Potentially exposed information includes API tokens, integration secrets, Git Sync secrets used to connect documentation with code repositories, and questions submitted to GitBook's AI assistant. The company said some credentials that are supposed to remain secret may have been exposed.

How did PancakeSwap respond to the GitBook security incident?

PancakeSwap temporarily disabled its documentation following news of the incident, although it said its own systems had not been compromised. The exchange subsequently announced that its documentation was back online after being moved from GitBook to infrastructure under its own control, with existing documentation links continuing to work.

What should GitBook customers do after the AI agent attack?

GitBook instructed customers to rotate any existing GitBook API tokens, replace third-party API tokens and secrets used to connect external tools to its platform, and reauthenticate the GitBook MCP server. The company revoked personal API tokens and urged customers to replace connected credentials.

When did GitBook restore service after the November 2 attack?

By Tuesday afternoon, GitBook said its application, API, and published documentation were accessible again, although some services could remain degraded during recovery. TokenPost reported service was restored at 10:21 a.m. ET November 3.