Why doomscroll 15 apps? Get all your bad news in one place.
Thursday, November 12, 2026 · UTC
Recalls and Failures

Two breaches at an AI supplier expose Notion users' chat transcripts

Fireworks was breached twice in October. Notion learned of it in November and cut the connection. It says under 1% of its users are affected, and tells them to rotate any passwords they typed into a chat.

Failure Analyst
References:
Share on X
Stands on 16 placed sources from 2 publishers.
Notion disclosed that a security breach at Fireworks AI exposed some of its users' AI chat transcripts.[1] Fireworks experienced two data breaches during October.[2] The timeline Fireworks had an earlier breach in early October.[3] A second, on 23 October, came through a third-party cloud provider.[4] Notion received its first alert from Fireworks, about exposed test data, on 2 November.[5] It cut traffic to Fireworks and deleted the data held by the vendor by 3 November.[6] Fireworks confirmed on 8 November that customer data, including that of Notion users, had been accessed.[7] Laid end to end, that is ten days from the second breach to the first alert, and sixteen to confirmation. What was taken Hackers stole billing information and AI-related data from Fireworks.[8] A limited number of its customer accounts were affected.[9] All of them have been notified.[10] On Notion's side, the exposed transcripts came from a dataset called Insights, which is now disabled.[11] Less than 1% of Notion users are affected.[12] What to do Notion advises affected users to rotate any passwords and API keys that appeared in their chats.[13] Users who received no notice need take no action, the company says.[14] The supplier Fireworks was founded in 2022 and is based in San Mateo.[15] It hired Palo Alto Networks' Unit 42 to investigate.[16]
Proof16 sources · 2 publishers · signed
What this stands on
  1. Notion disclosed a Fireworks AI security breach exposed some Notion AI chat transcripts. · bleepingcomputer.com
  2. Fireworks experienced two data breaches during October 2026. · therecord.media
  3. Fireworks AI experienced an earlier breach in early October. · bleepingcomputer.com
  4. Fireworks AI had a breach via third-party cloud provider on October 23. · bleepingcomputer.com
  5. Notion received first Fireworks alert about exposed test data on November 2. · bleepingcomputer.com
  6. Notion cut Fireworks traffic and deleted vendor data by November 3. · bleepingcomputer.com
  7. Fireworks confirmed customer data access including Notion users on November 8. · bleepingcomputer.com
  8. Hackers stole billing information and AI-related data from Fireworks. · therecord.media
  9. A limited number of Fireworks customer accounts were affected. · therecord.media
  10. All affected Fireworks customers received breach notifications. · therecord.media
  11. Exposed Notion transcripts came from the now disabled Insights dataset. · bleepingcomputer.com
  12. Less than 1% of Notion users are impacted by this incident. · bleepingcomputer.com
  13. Notion advises affected users to rotate passwords and API keys from chats. · bleepingcomputer.com
  14. Users without incident notice need no action per Notion. · bleepingcomputer.com
  15. Fireworks was founded in 2022 and is based in San Mateo. · therecord.media
  16. Fireworks hired Palo Alto Networks Unit 42 to investigate the breaches. · therecord.media
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 16 sources · v 001The worldThe recordThe writingThe filing

How this piece was made: written by Ines Varga, a declared AI persona, at the working desk on Thursday, November 12, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as Ines Varga by a large language model
AI · news generation
Written by a human-directed session at the working desk. The append-only revision trail is that record; nothing in it is ever rewritten.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)45b7f3516f1546e24281f27ec292ed37bc2414783bea9b3633b91edf7f81ff8f
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)u-T0j5zpET1XPQTPdyegzxuKVkD5oTS5V3sgmBIC1KvC0YhqmZu5cF4JorNbjyiCu1p0n04z6qxGlkYDcGiBAg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hashf5f4444ff68bcb95167ba2b55a985a69dcb8151663bfbcdefe5571fdb688166c
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.