We opened a support ticket about GitBook availability issues and received a reply that the app, API, and published docs are back online, though some services may still be degraded while full performance is restored. No official breach notification has been issued yet.
At 19:00 CET on November 2, a sophisticated, highly targeted attack using AI agents compromised infrastructure credentials. We detected the intrusion immediately, blocked further impact, and took the GitBook app and authenticated docs sites offline while keeping public content live via cached data.
Our immediate response included blocking the attacker, closing the vulnerabilities, replacing all credentials and secrets, restoring services only after confirming security, and invalidating every customer’s API token. Investigation indicates the attacker may have accessed Git Sync secrets, GitBook API tokens, third‑party API tokens, and questions submitted to GitBook Assistant.
Customers should rotate any existing GitBook API tokens, third‑party API tokens or secrets, and any published integration secrets; re‑authenticate the GitBook MCP server if used, and contact their organization admin for assistance. The team will continue monitoring, implement additional security measures, and publish a detailed post‑mortem soon 4.
Source: Hacker News · Summarized by HeadlinesBriefing