GitBook 遭 AI 智能體定向攻擊，部分基礎設施憑證遭未授權存取

Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Gitbook Breached 20 points by punchmesan31 minutes ago | hide | past | favorite | 4 comments We opened a ticket with support about Gitbook availability issues and got this in reply. We have yet to see any official customer communication or breach notification. Apologies for the formatting, did the best I could as it's a mobile paste. Update: GitBook security incident update Hey <$name>, The GitBook app, the GitBook API, and published docs are available again. A few services may still be degraded as we finish restoring everything to full performance. What happened GitBook has been the target of a sophisticated, highly targeted attack using AI agents. At 19:00 CET, November 2, the attacker gained unauthorized access to some of our infrastructure credentials. We detected the attack immediately and acted swiftly to block further impact. To make sure our infrastructure was fully secure, we then took the GitBook app and authenticated docs sites offline. We kept publicly published content live for as long as possible, using cached data. What we did immediately * Blocked the attacker and closed the vulnerabilities involved * Replaced every credential and secret across our infrastructure * Brought services back only once we were confident they were secure * Invalidated every customer’s API tokens on our platform Your data Our investigation shows that the attacker may have accessed the following: * Git Sync secrets. * GitBook API tokens. * Third-party API tokens used to connect external tools to GitBook. * Questions asked to GitBook Assistant by your site visitors. At this stage, we have found no evidence that any of your content in GitBook was modified. What you need to do now * Rotate any existing GitBook API tokens. We revoked all personal API tokens during the incident. * Rotate any third-party API tokens or secrets you use to connect other tools to GitBook. * If you have published integrations that use secrets, rotate those secrets. * If you use the GitBook MCP server, re-authenticate it. Please contact your GitBook organization’s admin to assist with this process. What we are doing next * Monitoring the situation in case of further attacks. * Introducing further security measures to our platform. * Writing a full post mortem that will be published soon with more detailed information about the incident. * If you have any further questions, please reach out to your account manager or our support team. You can also check status.gitbook.com for updates Thank you for your patience, and we apologize again for the disruption The GitBook team help petecooper8 minutes ago | next[–] https://www.gitbook.com/status/security-incident-2026-11-03 reply punchmesan15 minutes ago | prev | next[–] Oof that formatting is rougher than I thought. Will try to clean it up after I'm done reconfiguring gitbook... reply verdverm0 minutes ago | parent | next[–] neines between bullets, only italics available, not markdown reply philipwhiuk9 minutes ago | prev[–] This is the public disclosure: https://www.gitbookstatus.com/incidents/01M6FXDDGQRWHMYYWXY2... Note that the summary at the top of https://www.gitbookstatus.com at time of writing does not mention the unauthorized access and the incident details does not mention the contents disclosed above. reply Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact Search: