Gitbook Breached
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
GitBook’s CTO here
We have been dealing with a security attack since yesterday. Our team has been all hands on deck since the start, and we took a large portion of our services offline to prioritize user security.
Our service is progressively coming back online (most of it already is), and we are actively monitoring the situation.
We’ll continue to actively keep our users updated through emails, Slack, and our status page as we monitor the situation and learn more.
Good luck... this isn't easy, so best of luck to you and the team.
Classy response.
With the spate of attacks on infra providers over the past few weeks, it's been interesting to see how different competitors respond. The confidence some of the founders seem to have that they won't/can't be next is telling.
After turning on 2FA, the page doesn't update to say it is turned on. It still has a configure button. Reloading the page fixes this.
Nice to see someone not fucking up outreach during a security incident.
Good work.
Did you read the body of this post?
>Nice to see someone not fucking up outreach
it is sort of funny to see this on a post submitted by a gitbook user that starts off by saying "We have yet to see any official customer communication or breach notification.", and where the company's status page (https://www.gitbookstatus.com/incidents/01M6FXDDGQRWHMYYWXY2...) doesn't mention the customer data that was potentially accessed by the attackers or mention that credentials/tokens should be rotated.
in fact, that status page (which is linked to at the top of the gitbook site) still says "You don’t need to do anything right now."
> GitBook has been the target of a sophisticated, highly targeted attack using AI agents
Serious question: How do you know it was using AI agents? What logs distinguish it from a human?
I see this claim a lot and while I don't doubt AI is being used for this, I have a hard time believing every breach has a smoking gun showing it to be an AI assisted attack.
Maybe there was a level-of-stupidity tip-off, like trying to break in and access something that's already public...
My guess is the speed of exfiltration/exploration of the environment is probably impossible for a human, or even a small team. But I'm also curious what their evidence is.
Good that they rotated all the tokens themselves instead of just telling users to do it, seen too many incidents where that step gets skipped.
I think the timing is perfect for someone to create a simple, clean, breach link aggregator site.
I built this incident tracker a few years ago [1] but currently focus on SEC, State AG, and HHS posted incidents. There's a lot of noise if you go with news, blog, and company posts but I process them occasionally.
[1] https://www.board-cybersecurity.com/incidents/tracker
https://www.gitbook.com/status/security-incident-2026-11-03
It's bizarre they have both this and gitbookstatus.com and they contain different info.
We summarized more information on this page from recent learnings, than what has been posted as updates on the status page (https://www.gitbookstatus.com/incidents/01M6FXDDGQRWHMYYWXY2...).
the classic failure mechanism in the status page
Does a security incident page really need to connect to 11 3rd party domains. smh
If it was made by a web designer, then yes. It's also nice to have 151 HTML warnings and errors:
https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.gitbook.c...
And images that are 4x larger than necessary on the main page (nevermind whether the images add value to begin with):
https://webspeedtest.cloudinary.com/results/261104_YiDc1V_1W
There are maybe 10 websites that look good "inside and out" because web design is a broken field run by non-technical people.
What's happening currently that every other a day a major service is breached? Is it really just all AI Agents being blasted on those targets?
I have to suspect it's the aftermath of the many, many CVEs from this last month: https://en.wikipedia.org/wiki/Black_October_(information_sec...
"GitBook has been the target of a sophisticated, highly targeted attack using AI agents."
Add it to the list, I guess.
Is this what they mean when they talk about accountability laundering?
Oh, you see, we had the best security ever, but they used AI agents, and there's no defence for that, you can't secure a system against those spooky AI agents.
This is not what we meant. We will be accountable and will post a complete post-mortem. But it’s important to understand that the attack was a lot more developed than what we’ve been used to with humans, especially in terms of pace and adaptability.
For a lot of places, handling this kind of incident response was "eating your vegetables" preparation that has just in the last couple of months turned into "for me it was Tuesday"...
FYI, Gitbook was made by the team behing friendco.de, which they killed without any announcement years ago.
I’m genuinely sorry the end of friendco.de impacted you. It was 12-13 years ago; the service had little usage at the time, and we probably didn’t handle the end perfectly. I don’t recall exactly, but I can assure you that the team today is more experienced.
To be fair, I don't recall exactly the end of it either (I did not think it was that long ago!), but I remember being severely disappointed by the sudden disappearance of it (AFAIK I was trying to set it up inside a community project), and as such not trusting GitBook afterwards.
Thanks for the honest answer, nonetheless. Good luck with the incident.
Not really relevant here.
Mentioned this 5h ago, but this post definitely fleshes out more details.
https://news.ycombinator.com/item?id=50351061
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.
Oof that formatting is rougher than I thought. Will try to clean it up after I'm done reconfiguring gitbook...
new lines between bullets, only italics available, not markdown
One thing that would be appreciated are more details in these sorts of reports.
"the attacker gained unauthorized access to some of our infrastructure credentials"
How? Which infrastructure?
We’ll provide details in a long post-mortem. For now, it was important to notify our users as early as possible.