Fireworks AI widened its breach: billing data, datasets and model weights in attackers' hands

Direct answer

On November 9, 2026, Fireworks AI, an inference and fine-tuning platform with more than 10,000 customers — including Notion and Cursor — widened its October breach report: attackers reached billing data from its accounts and, in a limited set of accounts, stored secrets, datasets and incomplete model weights. The company says it does not store payment card numbers and that those were not affected. Inference, Training SDK and Nexus services were not affected, according to the company, because they retain no data by default. The update changes the story: the first bulletin on October 9 said there was no evidence of access to models, datasets or training data.

How the breach unfolded

What was affected and what stayed out

What to demand from your AI vendor after this case

Note: this article summarizes Fireworks AI's security bulletins of October 10 and November 9, 2026 and coverage in Silicon Report, AI Secure Platform, Breach History and Vanda Team. Customer figures are the company's published figures. The number of affected accounts and the volume of data have not been published. Fireworks' conclusions are provisional according to the company itself.

Want AI that works for your business?

Message us on WhatsApp and let's talk about automation and AI agents for your business.

WhatsApp inicIA

Related articles

Frequently asked questions

What data was affected in the Fireworks AI breach?

Billing data (addresses, invoice and payment history, balances and credit usage) and, in a limited set of accounts, stored secrets, datasets and incomplete model weights. Card numbers were not affected because Fireworks says it does not store them.

Why does the November 9 update matter so much?

Because it changes the first report: the October 9 bulletin said there was no evidence of access to models, datasets or training data. Five weeks later, the company confirmed there was access to datasets and incomplete weights in some accounts.

What is LLMJacking?

It is a scheme in which financially motivated actors steal access to language models and resell it through illicit routing gateways. Fireworks links its breach to this scheme, citing research by Google Threat Intelligence Group and Mandiant.

Are my models safe if I use an inference vendor?

It depends on what the vendor retains. In this case, the services with zero retention by default (Inference, Training SDK and Nexus) were not affected. Ask your vendor what data it stores and demand breach notice in writing in the contract.