AnswersPublished22 sources
How the Fireworks AI Breach Reached Notion AI Chats
Attackers used a breach at a cloud provider hosting Fireworks AI’s development machines to run an unauthorized workload and access customer data, including Notion AI Insights transcripts. Notion’s timeline ran from an initial warning on November 2 to revoking exposed API keys on November 11; the first dataset it rev...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer
Key takeaways
- Attackers used a breach at a cloud provider hosting Fireworks AI’s development machines to run an unauthorized workload and access customer data, including Notion AI Insights transcripts.
- Notion’s timeline ran from an initial warning on November 2 to revoking exposed API keys on November 11; the first dataset it reviewed appeared to contain synthetic test data, but a later review found real chat transc...
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: How did the October 23–24 breach of Fireworks AI’s third-party cloud provider lead to unauthorized workloads on its development machines and. Article summary: The reported attack followed an AI supply-chain path: a breach of Fireworks AI’s cloud provider gave attackers access to a Fireworks development system and, through it, customer data—including Notion AI transcripts store. Topic tags: general, general web. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers, clic
A breach at a third-party cloud provider gave attackers a path into Fireworks AI’s development machines, where they ran an unauthorized workload that led to additional customer-data exposure. One affected dataset included Notion AI chat transcripts used for the Insights feature. Notion said fewer than 1% of its workspaces were affected and clarified that the incident was at its vendor, not in Notion’s own systems. 4
8
How the intrusion unfolded
Fireworks said the cloud provider hosting its research-and-development machines experienced a security incident on October 23. On October 24, an unauthorized party used that path to reach Fireworks development machines and run a workload. Fireworks detected the activity that day. 4
14
The available disclosures describe the route through the cloud provider and development environment, but do not establish the precise technical exploit or every step by which the attackers reached particular data. The key point is that access to a vendor’s development environment led to additional customer-data impact. 14
What data was exposed
Fireworks’ expanded disclosure included resource metadata and billing information, including billing and payment history. It also said datasets and incomplete model weights were affected for some customers. Fireworks said it does not store payment card numbers. 4
9
34
For Notion, the affected material was chat transcripts used in classification jobs for Insights, a feature designed to help customers understand their AI usage. Notion reported that fewer than 1% of workspaces were affected; for the vast majority of those, the transcripts were not attributable to a specific user or workspace. 3
4
Notion’s response timeline
- November 2: Fireworks told Notion that a small dataset had been accessed. Notion’s initial review found synthetic testing data, not customer chats.
8
- November 3: Notion disconnected from Fireworks and deleted its data held in the vendor’s systems.
5
- November 6: Fireworks warned Notion that customer data might also have been accessed.
- November 8: Fireworks confirmed that the dataset included Notion AI chat transcripts used for Insights.
- November 9: Notion began contacting affected customers.
15
- November 11: Notion revoked exposed API keys found in affected user messages.
Notion also disabled Insights and stopped serving open-weight models through Fireworks, according to reports on the company’s response. 10
11 Affected customers were advised to treat passwords, API keys, and other credentials entered into the assistant as potentially exposed and rotate them.
21
Investigation and attribution
Fireworks engaged Palo Alto Networks’ Unit 42, notified law enforcement, and restricted some affected functionality. 34 The company said it believed the attackers sought to resell unauthorized model access through illicit routing gateways, a practice known as “LLMJacking.” That is Fireworks’ assessment of the motive, not conclusive identification of an attacker.
7
The cloud-provider incident was disclosed as a second Fireworks breach in October, following an earlier incident identified on October 6. 7 The two incidents should not be conflated: the later route described here began with a third-party provider and reached development machines on October 24.
4
7
What the incident shows about AI supply-chain risk
A company’s security exposure can extend beyond its own systems. When an AI service sends data to an outside provider for processing, the provider’s infrastructure and development environment become part of the broader risk picture. Notion’s disclosure is an example: the reported entry point was at Fireworks’ cloud provider, while the affected conversations belonged to a Notion feature. 4
8
For teams evaluating AI services, the incident is a reminder to ask what data a vendor or subprocessor retains, where it is processed, and how quickly access can be cut off. Avoid putting credentials into prompts when possible; if a secret may have appeared in an exposed transcript, revoke or rotate it. The reported exposure also reinforces the value of limiting access to datasets, credentials, and development systems to what is needed for a task.
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "How the Fireworks AI Breach Reached Notion AI Chats"?
Attackers used a breach at a cloud provider hosting Fireworks AI’s development machines to run an unauthorized workload and access customer data, including Notion AI Insights transcripts.
What are the key points to validate first?
Attackers used a breach at a cloud provider hosting Fireworks AI’s development machines to run an unauthorized workload and access customer data, including Notion AI Insights transcripts. Notion’s timeline ran from an initial warning on November 2 to revoking exposed API keys on November 11; the first dataset it reviewed appeared to contain synthetic test data, but a later review found real chat transc...
Sources
tenbrief.comFireworks AI breach widens — Notion AI chats exposed in under 1% of workspaces
aicassindra.comFireworks AI Says Its Breach Reached Datasets and Unfinished Models, a Month After Finding No Sign of It
plainenglish.ioFireworks AI Widens October Breach Disclosure as LLMJacking Threat Grows