Documentation Service GitBook Discloses Unauthorized Access

Overview: In a Hacker News post, GitBook's CTO said the company was “experiencing a security incident” and that the team was handling the response. To prioritize user protection, the operator took parts of the service offline and is now restoring them in phases. Updates have been posted on the official status page and another status domain, and the company said it would also use email and Slack to notify users.

Community reaction: In the thread, commenters criticized inconsistencies between the different status pages and noted the status pages’ heavy reliance on many external domains. Skepticism was expressed about the description that the attack was “sophisticated and targeted” and that an AI agent was used, and there was discussion about the company’s accountability. Some responses directly addressing the operator’s post praised the way the incident was handled.

Handling of announcements and primary sources: Links to the status pages on gitbookstatus.com and gitbook.com were shared in the thread, and contributors pointed out differences in the content between the two. Because current information depends on intermittent updates from the operator, the precise scope of the impact and details of affected data have not been specified. An official postmortem is planned.

Notes: This article is a summary based on a Hacker News discussion page; it is recommended to confirm primary information from GitBook’s official announcements (status pages and the forthcoming postmortem). Users should watch notifications and status updates and take steps to protect their accounts if needed (for example, verifying two-factor authentication).