GitBook Revokes All Personal API Tokens After Attack

According to an official GitBook announcement on November 4, its infrastructure credentials were accessed without authorization on November 2. The platform has revoked all personal API tokens and requested that users rotate third-party tokens and keys connected to other tools.

GitBook stated that the attack utilized AI agents, and attackers may have accessed integration tokens, Git Sync keys, API tokens, and questions submitted by visitors to GitBook Assistant. Currently, there is no evidence that customer content has been modified. The company confirmed it has blocked the attacker and patched the relevant vulnerabilities; its applications, APIs, and published documentation have resumed normal access, although some services may still be affected.