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.

▲

MrZander 6 minutes ago | parent | next [-]

> 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.

▲

xmcp123 18 minutes ago | parent | prev | next [-]

Nice to see someone not fucking up outreach during a security incident.

Good work.

▲

gkoberger an hour ago | parent | prev | next [-]

Good luck... this isn't easy, so best of luck to you and the team.

	▲	gk1 17 minutes ago \| parent [-]
		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.

▲

latchkey an hour ago | parent | prev [-]

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.