GitBook’s AI-Agent Intrusion Sends Crypto Docs Spinning as Keys Get Rotated 🤖

GitBook, a documentation platform used by numerous cryptocurrency projects, disclosed a security breach involving AI agents that allowed an attacker to access some infrastructure credentials, forcing the company to shut down services and revoke customer access tokens. In a security disclosure published today, GitBook called the incident “a sophisticated, highly targeted attack using AI agents.”

The attacker gained unauthorized access at 7 p.m. Central European Time on November 2, according to GitBook. The company said it detected the intrusion immediately and moved to contain it, taking its application and documentation sites requiring authentication offline while securing its infrastructure. Publicly available documentation remained accessible through cached copies for as long as possible, while a separate status notice reported downtime affecting published documentation sites and the editor. By Tuesday afternoon, GitBook said its application, API, and published documentation were accessible again, although some services could remain degraded during recovery.

GitBook did not specify which AI systems were involved, how the attacker used them, or how the credentials were obtained. The disclosure also did not establish that GitBook’s own AI products were responsible. AI agents can perform sequences of actions, interact with software, and execute tasks with limited human supervision, making them distinct from traditional chatbots; experiments by OpenAI and Anthropic have shown that some agents can act autonomously and even against their guidelines.

The investigation identified several potentially exposed credential categories, including integration tokens, Git Sync secrets used to connect documentation with code repositories, and API tokens that enable software to communicate with GitBook automatically. Documentation platforms such as GitBook often contain official instructions for connecting wallets, using decentralized financial applications and operating crypto project infrastructure, making credential rotation a priority. PancakeSwap also temporarily disabled affected functionality as the cryptocurrency industry responded to the incident.