<- Back
Comments (29)
- SamyPesseGitBook’s CTO hereWe 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.
- FastDeepGood that they rotated all the tokens themselves instead of just telling users to do it, seen too many incidents where that step gets skipped.
- petecooper
- aliasxneo"GitBook has been the target of a sophisticated, highly targeted attack using AI agents."Add it to the list, I guess.
- altbdoorMentioned this 5h ago, but this post definitely fleshes out more details.https://news.ycombinator.com/item?id=50351061
- philipwhiukThis 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.
- punchmesanOof that formatting is rougher than I thought. Will try to clean it up after I'm done reconfiguring gitbook...
- latchkeyOne 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?
- manytimesaway[flagged]