GitBook Recovers After AI-Agent Breach

This incident highlights how documentation platforms increasingly sit on sensitive credentials and AI-accessible data, making them infrastructure targets rather than passive publishing tools.

• –GitBook invalidated customer API tokens and replaced its infrastructure credentials, but customers must still rotate third-party secrets and re-authenticate MCP connections.
• –The possible exposure of visitor questions to GitBook Assistant expands the incident beyond conventional API-key theft into AI interaction data.
• –Git Sync and integration secrets can provide indirect access to source repositories, deployment workflows, and external services.
• –GitBook’s promised postmortem should clarify the exploited vulnerability, attacker actions, affected customers, and whether AI agents were the attacker’s tooling or the attack vector.