AI & Tech

Fireworks AI gets burned twice as customer data exposure widens

Fireworks AI has disclosed another cyberattack in October and a wider customer data exposure involving billing records, datasets, and incomplete model weights.

✦ Extractive summary — built from the sources' own reporting•From 1 source•1 min read•Updated November 10, 2026, 3:28 PM UTC
Key points
  • "No other data from within your workspace is affected." Bloomberg reports that Fireworks is also working with customers including Cursor and Harvey to assess the impact.
  • At the time, Fireworks said it had found no evidence of access to models, datasets, training data, inference traffic, or personal information.
  • "Most downloads were partial and stopped." Render founder and CEO Anurag Goel shared a notification from Notion warning that some chats with its AI assistant may have been exposed through the Fireworks incident.

Fireworks grouped the affected data into three categories: Resource metadata: Resource identifiers, display names, descriptions, creation times, and more Billing information: Billing and shipping addresses, invoice and payment histories, account balances, and credit usages.

Additional details
  • Fireworks suspects links to financially motivated criminals involved in LLMJacking – selling unauthorized access to AI models through illicit gateways.
  • Fireworks first disclosed an incident on October 9 after detecting unauthorized use of internal credentials on October 6.
  • Attackers used that access the following day to reach Fireworks development systems and run an unauthorized workload.
  • "Following an investigation by the Notion security team, we have determined that your workspace, Render, was among the "Some unattributable chat sessions with Notion AI may have been exposed in this incident." Notion said the exposed transcripts lacked separate information linking them to particular users or workspaces.
  • The company, which lets customers train and run AI models, said a third-party cloud provider hosting its research and development machines was compromised on October 23.

How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →

Advertisement

Every article behind this summary — 1 article from 1 outlet