GitBook urges token resets after AI-powered cyberattack

GitBook has urged customers to replace API tokens and integration secrets after an attack involving AI agents compromised infrastructure credentials and potentially exposed customer data. Summary GitBook said infrastructure credentials were accessed on Nov. 2, prompting service shutdowns and credential replacement. Potentially exposed data includes integration tokens, Git Sync secrets, API tokens, and visitors’ Assistant questions. Customers must rotate relevant credentials and reauthenticate connections to the GitBook MCP server. The app, API, and published documentation have returned, though some services could remain degraded. According to GitBook’s incident notice, the attacker gained unauthorized access to some infrastructure credentials at 7 p.m. CET on Nov. 2, equivalent to 6 p.m. UTC or 1 p.m. U.S. Eastern time. The documentation provider said it detected the attack immediately and moved to contain it. Its response included taking the application and documentation sites requiring authentication offline while securing its infrastructure. Publicly published material stayed available through cached data for as long as possible, the company said. By its Nov. 3 update at 4:21 p....