Breach · high
Fireworks AI breach from cloud provider hack exposes customer data, including Notion AI chat transcripts
Tier B · Patch this week – Put it in the sprint
Who’s exposed: Limited Fireworks AI customer accounts; datasets, weights, billing data
Tier B because: Exploited in the wild OR public exploit
Reach
Attack
Damage
Fix
Exploited in the wild · Secrets exposed
What to do
- Check whether your Fireworks AI account was among those notified
- Rotate API keys and secrets if they may have been exposed to the attackers
- Treat Notion AI chat content as exposed if it contained passwords or API keys, as Notion recommends
- Review what sensitive data your team sends to third-party AI vendors
The Brief
- Fireworks AI says hackers accessed some customers' datasets, incomplete model weights, and billing information over the past month.
- The attackers breached Fireworks' development machines after compromising a third-party cloud provider that hosted its research infrastructure.
- Fireworks says a limited number of customer accounts were affected, all of whom have been notified; it is the company's second known hack in weeks.
Why it matters
Teams that send training data, model weights, secrets or billing details to Fireworks AI should check whether their account was notified and review what they shared with the vendor.
The checklist behind the tier
Checklist · 3 of 10 yes
| Yes | Hits tech teams | Judgment: Fireworks AI is a developer-facing AI model hosting and inference platform that teams build with and run on. |
| No | Core infrastructure | Judgment: a single AI infrastructure vendor's breach, not software nearly every team runs. |
| No | Popular tool | Judgment: Fireworks is a known startup but a niche AI platform, not a mainstream framework or OS. |
| Yes | Exploited in the wild | BleepingComputer: attackers accessed Fireworks' development machines after breaching a third-party cloud provider. |
| No | Public exploit | No source says exploit code or a proof-of-concept was published. |
| No | Remote, no login | No source describes the initial access method or whether it needed no credentials. |
| No | Full takeover | Sources describe data access and theft; none report code execution, root or admin takeover. |
| Yes | Secrets exposed | The Hacker News: breach exposed account and billing data, secrets, datasets and incomplete models for a limited set of accounts. |
| No | Supply chain | No source reports malicious code shipped through a package, update, build pipeline or signing key. |
| No | No fix yet | No source says the underlying flaw remains unpatched; the reports describe a breach response. |
Timeline
Full coverage · 8 sources
- 5h ago ↗
- 1d ago ↗
The Record from Recorded Future News
AI company Fireworks says hackers stole data, billing info during October breaches - 1d ago ↗
The Hacker News
Fireworks AI Breach Widens to Expose Customer Billing Data and Incomplete Model Weights - 1d ago ↗
www.theregister.com - Articles
Fireworks AI gets burned twice as customer data exposure widens - 2d ago ↗
BleepingComputer
Fireworks AI discloses new breach after cloud provider hack - 2d ago ↗
Hacker News: Front Page
Fireworks AI security breach impacts Notion and their customers - 2d ago ↗
- 2d ago ↗
Bloomberg Technology
Nvidia-Backed Fireworks AI Notifies Customers of Its Second Hack in Weeks
What developers are saying
Based on 64 comments · Mostly critical
Commenters mostly focus on Notion's disclosure, calling its response vague and frustrating, especially since admins say they cannot see which members were affected without an Enterprise plan. Several question how Fireworks, which is listed as zero data retention, could have stored Notion data at all. Others use the thread to stress third-party AI vendor risk and self-hosting.
- Vague breach response30%
- Doubts over zero data retention20%
- Unclear per-user exposure25%
- Vendor risk and AI data handling25%
In favour
- + Limit the data shared with external AI vendors to reduce risk
- + Self-hosted tools reduce reliance on third-party services
Concerns
- − Notion's notice is vague, with phrases like may have been accessed and no per-user answers
- − Fireworks is listed as zero data retention, so retained Notion data raises questions
- − Checking which members were affected requires the Enterprise plan
“Notion is bs, they can't tell me which of my 330 employees have data in this breach, only 133 of them.”
“Forcing us to the Enterprise plan to see which members are affected huh? Classy move Notion.”
“So how come notion discovered that they actually stored the data?”
First seen · 8 sources · 64 comments · Full story page · How tiers are decided