News for hackers. Stuff that matters.
Re:Gitbook Breached by SamyPesse on Tuesday November 03, 2026 @01:05PM (#50355659)
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.

Re:Gitbook Breached by gkoberger on Tuesday November 03, 2026 @01:07PM (#50355695)
Good luck... this isn't easy, so best of luck to you and the team.
Re:Gitbook Breached by gk1 on Tuesday November 03, 2026 @02:09PM (#50356681)
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.

Re:Gitbook Breached by latchkey on Tuesday November 03, 2026 @01:10PM (#50355756)
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.
Re:Gitbook Breached by xmcp123 on Tuesday November 03, 2026 @02:08PM (#50356659)
Nice to see someone not fucking up outreach during a security incident.

Good work.

Re:Gitbook Breached by throwrioawfo on Tuesday November 03, 2026 @03:08PM (#50357466)
Did you read the body of this post?
Re:Gitbook Breached by john_strinlai on Tuesday November 03, 2026 @03:10PM (#50357487)
>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."

Re:Gitbook Breached by MrZander on Tuesday November 03, 2026 @02:20PM (#50356835)
[delayed]
Re:Gitbook Breached by conartist6 on Tuesday November 03, 2026 @02:29PM (#50356970)
Maybe there was a level-of-stupidity tip-off, like trying to break in and access something that's already public...
Re:Gitbook Breached by ipsum2 on Tuesday November 03, 2026 @02:31PM (#50356978)
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.
Re:Gitbook Breached by michaelscott on Thursday November 05, 2026 @03:07AM (#50376470)
Generally the speed of breaking through components of the tech stack. They chain exploits and they move through the system at a rate that's far faster than even a team of humans could pull off
Re:Gitbook Breached by michaelscott on Thursday November 05, 2026 @02:55AM (#50376385)
Experienced this with a client as well, all my thoughts to you guys and the team. One thing we struggled with was determining the effective blast radius of compromised credentials. Blocking access was one thing, but the other critical component was whether activity could be reconstructed from independent logs (for this event and in future). Intereseted in whether the postmortem covers how you guys have established those boundaries, would make for some good learnings in general.

Feels like a new normal