Latest / Decrypted: The UK Cyber Briefing / A breach at an AI supplier's supplier exposed Notion users' chat transcripts
Transcript
- 0:03Good morning, and welcome to Decrypted.
- 0:05I'm Belinder. It's Thursday, the twelfth of November, twenty twenty-six, and this is the morning edition.
- 0:12A breach at an AI supplier's supplier exposed Notion users' chat transcripts.
- 0:18Last month, the AI infrastructure firm Fireworks was breached twice.
- 0:24This week, one of its customers, Notion, confirmed that the fallout reached some of its users' AI chat transcripts.
- 0:31Their conversations sat somewhere they couldn't see, held by a supplier of a supplier.
- 0:36Fireworks is a San Mateo company that runs AI models for more than 10,000 customers.
- 0:42It says a financially motivated criminal group got in on 6 October.
- 0:46They took account and billing information, plus secrets, meaning stored credentials.
- 0:51On 23 October, a third-party cloud provider hosting its research machines was attacked.
- 0:57The next day, Fireworks says, the intruder used that provider to reach development machines and run an unauthorised
- 1:04workload. That exposed billing records, datasets and other AI data.
- 1:09Notion used Fireworks to run open-weight models and to classify chats for its Insights feature, which shows
- 1:15workspace administrators how their teams use AI.
- 1:18Notion says transcripts were exposed in a small number of workspaces, fewer than 1% of users.
- 1:24It says most were unattributable, meaning not labelled with an author or workspace.
- 1:30So how did data end up in a place Notion's users never knew about?
- 1:34Imagine posting confidential letters through a courier who, unknown to you, rents shelf space in another firm's
- 1:41warehouse. The courier promised not to keep copies.
- 1:44Notion's own notice says Fireworks had contractually committed to zero data retention.
- 1:49Yet when someone breaks into the warehouse, the shelves aren't empty.
- 1:53A promise on paper is not a control.
- 1:56And nothing on the sender's side would have shown the break-in.
- 2:00So what did the defenders actually see?
- 2:02Nothing on their own network.
- 2:04Notion learned of a problem from Fireworks on 2 November.
- 2:08It cut off traffic and deleted its data by 3 November, then received confirmation that customer data had been
- 2:14accessed. Notion has switched off Insights.
- 2:17It tells workspace owners to review the affected data, and to rotate any passwords or A P I keys, the way one
- 2:24program talks to another, that anyone typed into a chat.
- 2:27That last instruction is the real lesson.
- 2:30People paste secrets into AI assistants as freely as they once did into email.
- 2:34What's the Secure by Design lesson here?
- 2:37The cheapest data to protect is data that no longer exists.
- 2:42Two decisions would have shrunk this incident.
- 2:44First, don't store prompts and transcripts longer than the job needs, and make deletion automatic rather than
- 2:51contractual. Second, give each supplier narrowly scoped credentials that expire, so a stolen key opens one door
- 2:58for an hour. For a UK organisation, the practical step this week is three questions to every AI supplier.
- 3:06Where do our prompts and transcripts rest?
- 3:08For how long? And which cloud provider holds them behind you?
- 3:12Under data protection law, you stay answerable for what your suppliers do with personal data.
- 3:17And a chat log full of client names is personal data.
- 3:21If the answers are vague, assume your staff's secrets may live there indefinitely.
- 3:26As always, this is opinion, not advice.
- 3:30That was Decrypted, with me, Belinder.
- 3:34The written version and every source are linked in the show notes.
- 3:37Thanks for listening. Stay patched, and stay sceptical.