Fireworks AI Breach Reached Billing Data, Secrets and Datasets, and Exposed Notion AI Transcripts From Under 1% of Workspaces

Verdict: if you stored secrets with Fireworks AI, rotate them now instead of waiting for a notice email. If your team uses Notion AI, check today whether your workspace is in the affected group. Fireworks says the attackers sell stolen access to language models, which makes any API key stored with Fireworks the obvious prize. Neither Fireworks AI nor Notion AI is in our directory yet.

What happened

Fireworks AI. Its incident update ("Last updated November 9, 2026") says a third-party cloud provider hosting Fireworks R&D machines had a security incident on 23 October. On 24 October, unauthorized actors used that access to reach Fireworks development systems and "run an unauthorized workload that led to additional customer data impact".

What Fireworks now lists as hit:

• Account and billing information (addresses, invoices, payment history, account balances). Fireworks says payment card data was not stored or impacted.
• "For a limited set of accounts, we also discovered impact to secrets, datasets, and incomplete models."

What Fireworks says was not hit: "We have not detected any impact to Inference, Training SDK and Nexus, which are all zero data retention (ZDR) by default." Self-serve dataset uploads and downloads for Batch Inference and dataset-based training are disabled while the investigation runs.

Notion. Notion's help-center notice names Fireworks AI as the vendor and says "fewer than 1% of Notion workspaces" were affected. The exposed data is Notion AI chat transcripts, meaning the input to and output from the model, used for the Insights feature. Notion says it disconnected from Fireworks on 3 November, deleted its data in the Fireworks system and stopped sending traffic there.

Why it matters

Fireworks attributes the attack to "a cybercriminal threat actor group, which is financially motivated and aimed at selling tokens from unauthorized access to Large Language Models (LLMs) to illicit routing gateways, known as 'LLMJacking'." For that kind of group, a stored provider key converts straight into resale revenue, and the bill lands on you.

The Notion side is the quieter risk. Chat transcripts hold whatever people typed into Notion AI, and Notion tells teams to rotate any passwords or API keys pasted into it. A breach at an inference vendor you never signed up with still reached your data through a tool you did.

Fireworks says it is notifying affected customers with impact details and recommended actions. The public bulletin lists no specific steps, so do not wait for the email. We did not read Fireworks' original October notice, and none of the sources we read names other affected Fireworks customers, so we name none.

What changes for you

• Fireworks customers: rotate every secret stored with Fireworks and review billing for usage you did not make.
• Notion workspace owners: open the sidebar, choose "?", then "Security incident review". It offers CSV downloads of affected members and content (desktop browser, latest Notion version).
• Anyone who used Notion AI: Notion's advice is direct: "If you or anyone on your team pasted sensitive information like passwords, API keys, or other credentials into Notion AI during this timeframe, we recommend rotating them right away."