• Sources: primary, discussion
  • Summary: GitBook says an attacker using AI agents gained access to some infrastructure credentials at 19:00 CET on 2026-11-02, after which it took the app and authenticated docs offline, replaced all secrets and revoked every customer API token. The attacker may have accessed integration tokens, Git Sync secrets, API tokens and questions visitors asked GitBook Assistant, and GitBook found no evidence that content was modified.
  • Why it matters: Teams that sync docs from Git or connect tools to GitBook should rotate GitBook API tokens, third-party tokens, integration secrets and re-authenticate the GitBook MCP server.
  • Follow-up: GitBook's promised full post mortem.
  • Comments: The HN poster received the breach details through a support ticket before any customer notice, and a commenter notes the status page summary did not at first mention unauthorized access.