frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Tell HN: Gemini trains on chat history, even for subscribers (personal accounts)

548•jameslk•10h ago•139 comments

Tell HN: Don't use Postman, they proxy your info without your permission

92•neya•17h ago•3 comments

OpenAI seems to be silently re-enabling model training on Codex chats

512•user052919•1d ago•152 comments

Ask HN: Which agent harness do you use for working with multiple Models?

4•avucenovic•2h ago•0 comments

Gitbook Breached

162•punchmesan•1d ago•38 comments

Ask HN: Which TV do you recommend for privacy?

728•LecroJS•3d ago•877 comments

Ask HN: What's on Your Learning List?

3•carlos-menezes•5h ago•1 comments

Ask HN: Who is hiring? (November 2026)

247•whoishiring•2d ago•248 comments

Ask HN: Is AI good enough for math exercises?

3•Qision•5h ago•1 comments

Ask HN: Is it worth reading The Art of Computer Programming now?

7•weavie•11h ago•2 comments

Ask HN: What's your current AI agentic setup?

62•eggbrain•5h ago•72 comments

Ask HN: Does anyone have a contact with Cleveland-area Ham club?

164•stockresearcher•1d ago•23 comments

WorkOS reports security breach

77•werrett•1d ago•11 comments

Tell HN: GitHub Is Down

29•yuvadam•10h ago•16 comments

Tell HN: Scribd Breached

359•x______________•4d ago•123 comments

Ask HN: Impact of US Elections on AI?

6•talmr•12h ago•9 comments

Ask HN: How to Keep the Edge as an Engineer?

8•spacebuffer•12h ago•3 comments

Tell HN: You now need a government id in order to create an Anthropic account

19•I_am_tiberius•1d ago•9 comments

Ask HN: What is the best non mainstream programming language or stack in 2026?

4•kbrannigan•19h ago•5 comments

Ask HN: Will cheap high-quality AI end this December?

7•amichail•1d ago•3 comments

Ask HN: Design My YouTube Feed

4•mrkn1•1d ago•8 comments

Ask HN: Does anyone enjoy work anymore?

27•jackmalpo•1d ago•25 comments

Ask HN: What is Google Flights' business model and has it changed recently?

7•lastofthemojito•22h ago•6 comments

Google reCAPTCHA on archive.is asking to scan a QR with a mobile device

4•linuxhdr•22h ago•1 comments

Getting hit with "Prove you are a human" at every other website

84•shmde•1d ago•46 comments

How did we end up with Frontier Lab oligopoly rather than a monopoly?

3•bdhe•1d ago•2 comments

Can the Cloudflare employee that just blocked Route53 Health Checks undo it

7•ferngodfather•1d ago•3 comments

Anthropic's HackerOne bot lawyered me out of a bounty

3•francesco_m•1d ago•0 comments

Ask HN: What to do about incorrectly suspended GitHub account, no notice?

7•sshah03•2d ago•3 comments

Tell HN: X is opening any tweet link in a webview whether you press it or not

40•stillatit•4d ago•3 comments
Open in hackernews

Gitbook Breached

162•punchmesan•1d ago
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

Comments

punchmesan•1d ago
Oof that formatting is rougher than I thought. Will try to clean it up after I'm done reconfiguring gitbook...
verdverm•1d ago
new lines between bullets, only italics available, not markdown
philipwhiuk•1d ago
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.

petecooper•1d ago
https://www.gitbook.com/status/security-incident-2026-11-03
philipwhiuk•1d ago
It's bizarre they have both this and gitbookstatus.com and they contain different info.
SamyPesse
•
1d ago
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...).
sitzkrieg•22h ago
the classic failure mechanism in the status page
eddythompson80•1d ago
Does a security incident page really need to connect to 11 3rd party domains. smh
Panino•19h ago
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.

MonstraG•11h ago
I wanna note that some (52) of those are "css property corner-shape doesn't exist", and it does, just isn't supported in all browsers yet.
manytimesaway•1d ago
FYI, Gitbook was made by the team behing friendco.de, which they killed without any announcement years ago.
SamyPesse•1d 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.
manytimesaway•1d ago
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.

viccis•1d ago
Not really relevant here.
aliasxneo•1d ago
"GitBook has been the target of a sophisticated, highly targeted attack using AI agents."

Add it to the list, I guess.

nsoam•1d 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•1d 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.
eichin•23h ago
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"...
SamyPesse•1d ago
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.

gkoberger•1d ago
Good luck... this isn't easy, so best of luck to you and the team.
gk1•1d ago
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•1d 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.
xmcp123•1d ago
Nice to see someone not fucking up outreach during a security incident.

Good work.

throwrioawfo•1d ago
Did you read the body of this post?
john_strinlai•1d ago
>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."

MrZander•1d ago
> 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.

conartist6•1d ago
Maybe there was a level-of-stupidity tip-off, like trying to break in and access something that's already public...
ipsum2•1d ago
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.
latchkey•1d 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•1d ago
We’ll provide details in a long post-mortem. For now, it was important to notify our users as early as possible.
altbdoor•1d ago
Mentioned this 5h ago, but this post definitely fleshes out more details.

https://news.ycombinator.com/item?id=50351061

FastDeep•1d ago
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.
tom1337•21h ago
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?
morserer•20h ago
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...
Panino•19h ago
I think the timing is perfect for someone to create a simple, clean, breach link aggregator site.
ahoog42•19h ago
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

FearNotDaniel•14h ago
> sophisticated, highly targeted attack

I love the way all incident reports tell you the attack was sophisticated and highly targeted, as if those words actually mean anything. Nobody wants to admit they were DDOSed by a script kiddie just randomly trying exploits. The subtext is: well, we expected hackers; just not really good ones.

SamyPesse•6h ago
A quick update to this thread that the incident is resolved, and we'll be publishing a post-mortem in the next 24 hours covering what happened, the impact it had, what we did to resolve, and what'll we do next. You can get an update when this is out on GitBook status page.