Post

GitBook security incident

GitBook’s CTO confirmed a security attack and service disruption in this HN thread. The submitter posted what they described as a GitBook support response saying infrastructure credentials were accessed on November 2 and Git sync secrets, GitBook API tokens, third-party integration tokens and assistant questions may have been exposed.

That pasted notice says GitBook revoked personal API tokens and recommends rotating third-party integration secrets and re-authenticating MCP access. The pasted notice’s detailed scope has not been independently verified here; affected users should consult GitBook directly. Readers questioned the timing and clarity of public communications and the claim that AI agents were involved.