GitBook says an attacker using AI agents got some of its infrastructure credentials on Nov 2; it revoked every personal API token and tells customers to rotate integration secrets and re-authenticate its MCP server

official (GitBook security incident notice, Nov 3, updated 16:21 CET). GitBook has not said how the AI agents were used or how the credentials were obtained2026-11-03

GitBook says an attacker using AI agents got some of its infrastructure credentials on Nov 2; it revoked every personal API token and tells customers to rotate integration secrets and re-authenticate its MCP server

What GitBook asks customers to do:

Create new GitBook API tokens (all personal tokens were revoked).
Rotate third-party API tokens or secrets used to connect other tools to GitBook, including secrets in published integrations.
Re-authenticate the GitBook MCP server.

Worth adding: Git Sync connects GitBook to code repositories, so revoke and reissue the GitHub/GitLab app or token GitBook used and review recent commits and repository access from it. If your docs are public, check that nothing was changed in the published content and that no links or install commands were swapped.

This lands in the same week as other disclosed intrusions at developer and crypto infrastructure providers (see our Chainstack item). GitBook has not linked its incident to them, and its notice does not say which AI systems were involved.

Sources: GitBook: Security incident (Nov 3, 2026) · Decrypt: Crypto docs host GitBook hit by AI agent security breach