cd /news/ai-safety/fireworks-ai-gets-burned-twice-as-cu… · home › topics › ai-safety › article
[ARTICLE · art-167079] src=machinebrief.com ↗ pub= topic=ai-safety verified=true sentiment=↓ negative

Fireworks AI gets burned twice as customer data exposure widens

Fireworks AI disclosed a second October cyberattack, reporting that a compromised third-party cloud provider hosting its research and development machines on October 23 gave attackers access to Fireworks development systems the following day, where they ran an unauthorized workload. The company said the incident exposed customer resource metadata, billing and shipping addresses, invoice and payment histories, account balances and credit usages, plus a subset of incomplete model weights and datasets for certain customers; payment card numbers were not stored and were unaffected. Fireworks co-founder and CEO Lin Qiao said "From what we see attackers are not after weights" and that "Most downloads were partial and stopped," while Notion notified Render CEO Anurag Goel that Render was among the under 1 percent of Notion workspaces that may have been affected, with some unattributable Notion AI chat sessions possibly exposed.

by read3 min views3 publishedNov 10, 2026
Fireworks AI gets burned twice as customer data exposure widens
Image: Machinebrief (auto-discovered)

The Register Inference biz pins latest breach on cloud provider and LLMJacking miscreants

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

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. Attackers used that access the following day to reach Fireworks development systems and run an unauthorized workload.

Fireworks suspects links to financially motivated criminals involved in LLMJacking – selling unauthorized access to AI models through illicit gateways.

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. Payment card numbers are not saved and therefore unaffected
  • Model weights and datasets: For certain customers, a subset of incomplete model weights and datasets were accessed, Fireworks said

Lin Qiao, Fireworks co-founder and CEO, said the apparent motive was not stealing model weights in response to concerns raised by Cantina Security CEO Hari Mulackal.

"From what we see attackers are not after weights," said Qiao. "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.

"Following an investigation by the Notion security team, we have determined that your workspace, Render, was among the <1 percent of Notion workspaces that may have been affected by the Fireworks security incident," the email sent to Goel stated.

"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. As Reddit users pointed out, however, the conversations themselves could contain identifying details.

"Beyond what's in the chat transcript itself, there's no information tying the chat back to your workspace, users, or company," the email added. "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.

Fireworks' update confirmed that it worked with Palo Alto Networks' Unit 42 team to remediate the attack, which included rotating credentials, isolating affected systems from the network, and tightening up data storage access and monitoring systems.

The update did not state how many customers were affected by either of the two attacks in October.

Fireworks first disclosed an incident on October 9 after detecting unauthorized use of internal credentials on October 6. Attackers accessed environment variables in evaluation jobs, including API keys and tokens belonging to some customers.

At the time, Fireworks said it had found no evidence of access to models, datasets, training data, inference traffic, or personal information. Monday's update substantially broadens the disclosed impact. ®

Get AI news in your inbox

Daily digest of what matters in AI.

── more in #ai-safety 4 stories · sorted by recency
── more on @fireworks ai 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/fireworks-ai-gets-bu…] indexed:0 read:3min 2026-11-10 · —