Fireworks AI discloses second breach exposing billing data and incomplete model weights
According to RuntimeWire, Fireworks AI told customers on November 9 that an intrusion dated October 24 reached its billing records and, for a limited set of accounts, stored secrets, customer datasets and incomplete model weights. The second intrusion began at a third-party cloud provider that hosted Fireworks' research and development machines. That provider had a security incident on October 23. A day later, the intruder used the foothold to reach Fireworks development machines and run an unauthorized workload.
The billing data covers billing and shipping addresses, invoices, payment history, account balances and credit usage. Fireworks says it does not store payment card numbers, so those were not affected. The company reports no further successful access to its customer platform since October 25, and no impact on Inference, Training SDK or Nexus, which run with zero data retention by default. Silicon Report says Fireworks lists more than 10,000 customers on its website.
The November 9 notice updates an earlier October incident. On October 6, Fireworks detected unauthorized use of internal credentials, which exposed environment variables including API keys and tokens for a limited number of accounts. The company revoked credentials, rotated employee keys, notified law enforcement and brought in Palo Alto Networks' Unit 42 for forensic analysis. Bloomberg described the latest disclosure as the company's second known hack in a matter of weeks.
Why it matters
For companies building on hosted inference or fine-tuning, the platform's exposure is also the exposure of its vendors. API keys, uploaded training sets and partly trained weights can sit with a provider whose own cloud host was breached. Teams should rotate keys and tokens, list which datasets and checkpoints they uploaded, and check whether their contract sets a notice deadline measured in hours. Enterprise buyers will likely ask the same questions.
For investors and sellers of AI infrastructure, the story is about trust in the data path. The reported impact excludes the zero-retention products, which matters for customers who chose those settings, while accounts that stored data on the platform face a different risk. Diligence should cover subprocessors, breach notice terms, default data retention and how quickly a vendor can replace credentials. A second incident within weeks raises the bar for those answers.
Key points
- 1The October 24 intrusion entered through a third-party cloud provider hosting Fireworks' development machines.
- 2Billing data exposed includes addresses, invoices, payment history, account balances and credit usage.
- 3For a limited set of accounts, stored secrets, customer datasets and a subset of incomplete model weights were reached.
- 4Fireworks says payment card numbers are not stored on its systems and were not affected.
- 5
