GitBook Hit by AI Agent Attack, PancakeSwap Takes Docs Offline

GitBook, the documentation platform behind many project docs sites, says it was hit by "a sophisticated, highly targeted attack using AI agents." It has revoked every customer's API tokens and is asking teams to rotate their keys.

The fallout reached DeFi quickly. PancakeSwap temporarily took its documentation offline as a precaution and said its docs were not compromised and its app was unaffected.

How the GitBook Breach Unfolded

According to GitBook's incident notice, the attacker gained unauthorized access to some of its infrastructure credentials at 19:00 CET on November 2. GitBook says it detected the attack immediately and moved to block further impact.

Its response was blunt. The company took the GitBook app and authenticated docs sites offline. Publicly published content stayed up for as long as possible on cached data, so a visitor might still have seen a page that was being served from a saved copy.

GitBook's status page first reported downtime affecting published documentation sites and the editor on November 3. A later update said both the app and public content should be back online, and a further update noted problems for some customers with published sites.

The company now says the app, the API and published docs are available again, though a few services may still be degraded.

What the Attacker May Have Reached

GitBook lists four kinds of data the attacker may have accessed:

• Integrations tokens
• Git Sync secrets
• API tokens
• Questions that site visitors asked GitBook Assistant

That last item is the easiest to overlook. It isn't a key or a password, but it's a record of what a project's users were asking about.

On the content itself, GitBook says it has "found no evidence that any of your content in GitBook was modified" at this stage. That matters for crypto projects, where a docs page is often where users go to find the right contract address or app link.

The Key Rotation GitBook Is Asking For

GitBook says it replaced every credential and secret across its own infrastructure and invalidated every customer's API tokens. That clears its side. The rest falls on customers, who are asked to:

1. Rotate any existing GitBook API tokens, since all personal API tokens were revoked during the incident.
2. Rotate any third-party API tokens or secrets used to connect other tools to GitBook.
3. Rotate secrets used by any published integrations.
4. Re-authenticate the GitBook MCP server, if they use it.

The design choice here is a broad reset rather than a targeted one. Revoking every token means some working integrations break until teams reissue them, but it removes the guesswork about which tokens were exposed.

PancakeSwap Pulls Its Docs as a Precaution

PancakeSwap temporarily removed its documentation from public access after the incident, describing the move as a precaution. The decentralized exchange said its documentation was not compromised and its app was unaffected.

It also stressed that its documentation never asks users to connect a wallet or approve tokens. That's a useful line to remember while hosted docs are going on and offline: a docs page asking for a wallet connection would be a red flag.

Whether PancakeSwap has permanently moved its docs off GitBook is not yet confirmed.

The Questions GitBook Hasn't Answered Yet

The biggest gaps are how the attacker obtained the credentials and which AI systems were involved. Neither detail is confirmed so far.

GitBook says it is writing a full post mortem with more detail and will publish it soon. That report should show whether "AI agents" describes a new kind of attack or a familiar one run faster, and whether any customer token was actually used after it was taken.