GitBook infrastructure breached in AI agent-driven attack
Security & Exploits ·
Attackers used automated AI agents to gain unauthorized entry into parts of GitBook's backend, prompting credential resets and temporary outages across the documentation platform used by crypto projects.
GitBook disclosed that the intrusion began at 1:00 p.m. EST on November 2, when AI-driven attackers obtained unauthorized access to a portion of its infrastructure credentials, according to wublockchain.xyz. The company said it identified and halted the breach, pulling some services offline temporarily while it assessed the damage.
Data potentially exposed in the incident includes integration tokens, Git Sync secrets, API tokens, and questions users had submitted to the GitBook Assistant tool. GitBook stated it found no sign that any documentation content had been altered during the breach. In response, the platform reset all infrastructure credentials and secrets, invalidated every customer API token, and urged users to refresh any linked third-party credentials and reconnect their GitBook MCP integrations as a precaution.
Recovery followed within roughly a day: by 10:21 a.m. EST on November 3, GitBook's application, API, and public-facing documentation pages were back online, though the company acknowledged some services were still running in a degraded state. GitBook said a detailed post-incident report would follow.
The breach had knock-on effects for projects relying on the platform. trade[XYZ] flagged suspicious activity tied to its own GitBook-hosted documentation, later restoring it and cautioning users not to click links while the matter was under review, per wublockchain.xyz. PancakeSwap took a more cautious route, pulling its documentation site down entirely as a preventive measure once the GitBook incident became known, and rerouting its documentation links to its main homepage until the situation cleared.
The episode underscores a growing risk vector in which AI agents are deployed not just defensively but offensively, to probe and exploit infrastructure credentials at scale — a dynamic that complicates response times for platforms serving many downstream clients simultaneously. Because GitBook hosts documentation for numerous crypto projects, a single infrastructure compromise can cascade into reputational and security concerns for products that had no direct vulnerability of their own.
What remains unclear is the scope of data actually exfiltrated versus merely exposed, whether any integration tokens were used maliciously before rotation, and which other projects beyond trade[XYZ] and PancakeSwap may have been affected. GitBook's promised post-incident report is expected to clarify the attack's technical details and the full extent of customer impact.