On November 2, an attacker used what GitBook described as a targeted attack involving “sophisticated AI agents” to access infrastructure credentials. Those credentials may have exposed integration API tokens and Git Sync secrets; GitBook also said questions submitted to GitBook Assistant could have been affected. The reports say there was no evidence that documentation content had been changed. GitBook’s incident notice, as relayed by Rickler Feed

On November 2, an attacker used what GitBook described as a targeted attack involving “sophisticated AI agents” to access infrastructure credentials. Those credentials may have exposed integration API tokens and Git Sync secrets; GitBook also said questions submitted to GitBook Assistant could have been affected. The reports say there was no evidence that documentation content had been changed. GitBook’s incident notice, as relayed by Rickler Feed

GitBook said it blocked the attacker, fixed the vulnerabilities, rotated its infrastructure secrets, and revoked all personal API tokens. It urged users to rotate their own secrets and re-authenticate MCP; reports also say the application was temporarily disabled before services returned. Rickler Feed’s incident update