Notion
Incident posture
Timeline
Summary
Notion notified a small set of customers that their information was compromised after Fireworks AI was hacked through compromised internal credentials and a third-party cloud provider hosting R&D machines. The second breach led to unauthorized access of AI chat transcripts used for the Insights feature, affecting fewer than 1% of workspaces, with most transcripts unattributable to specific customers or workspaces. The company stated that beyond the chat transcript content, no information tied the data back to workspaces, users, or companies, and it contacted affected customers with instructions to securely retrieve and review the data.
Motives
Detailed motive labels are available to members.
TTPs
Detailed technique labels are available to members.
Description
Notion began notifying a small set of customers that their information was compromised in a data breach involving Fireworks AI, a cloud platform for running and fine-tuning open source AI models. Fireworks AI experienced two separate hacks in October. The first incident involved compromised internal credentials. The second incident occurred through a third-party cloud provider that was hosting Fireworks research and development machines. This second breach was linked to a recent rise in LLMJacking activity and took place on October 24. During that incident, attackers executed an unauthorized workload that led to the compromise of customer data. Fireworks contained the incident on the same day. Fireworks notified Notion on November 2 that Notion AI data had been accessed. Before the breach, Notion had used Fireworks as a general inference provider for delivering open-weight models. The notification from Fireworks initiated Notion's own investigation into the scope of the exposure.
Notion's investigation determined that the hackers accessed Notion AI chat transcripts used for the Insights feature, which helps customers understand their AI usage. Fewer than 1 percent of Notion workspaces were affected by the exposure. Most of the compromised transcripts were unattributable to a specific customer or the workspace they originated from. Notion stated that beyond what is contained in the chat transcript itself, there is no information tying the chat back to workspaces, users, or companies. The company contacted the affected customers with instructions on how to securely retrieve and review the data in their workspaces. Notion did not disclose the total number of customers affected. Notion advised affected customers to treat the exposed data as compromised. The company specifically noted that customers who pasted sensitive information, passwords, API keys, or other credentials into Notion AI during the incident should rotate any exposed credentials. SecurityWeek contacted Notion for additional information on the data breach and indicated it would update its reporting if the company responded. The timeline spans from the October compromises at Fireworks AI through the November 2 notification to Notion and the subsequent customer outreach.
Sources
Sources available to members: 1 source.