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.
gkoberger 45 minutes ago [-]
Good luck... this isn't easy, so best of luck to you and the team.
latchkey 42 minutes ago [-]
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.
manytimesaway 2 hours ago [-]
FYI, Gitbook was made by the team behing friendco.de, which they killed without any announcement years ago.
SamyPesse 44 minutes 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.
viccis 42 minutes ago [-]
Not really relevant here.
altbdoor 45 minutes ago [-]
Mentioned this 5h ago, but this post definitely fleshes out more details.
"GitBook has been the target of a sophisticated, highly targeted attack using AI agents."
Add it to the list, I guess.
nsoam 53 minutes ago [-]
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.
SamyPesse 18 minutes ago [-]
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.
punchmesan 2 hours ago [-]
Oof that formatting is rougher than I thought. Will try to clean it up after I'm done reconfiguring gitbook...
verdverm 2 hours ago [-]
new lines between bullets, only italics available, not markdown
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.
latchkey 45 minutes ago [-]
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?
SamyPesse 23 minutes ago [-]
We’ll provide details in a long post-mortem. For now, it was important to notify our users as early as possible.
Rendered at 18:52:17 GMT+0000 (Coordinated Universal Time) with Vercel.
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.
https://news.ycombinator.com/item?id=50351061
Add it to the list, I guess.
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.
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.
"the attacker gained unauthorized access to some of our infrastructure credentials"
How? Which infrastructure?