Fireworks confirms attackers accessed customer data, datasets and unfinished models
Prepared by Sintelligent with the help of SI. Published in SI: . Updated: .
The breach of development infrastructure affected not only service keys but also some customer data and models; the privacy of an SI service also depends on its external providers.
An update to the investigation into October's incident has expanded the initial assessment: resource metadata, billing addresses, invoice histories and balances were affected, along with secrets, datasets and incomplete model weights for some customers. Fireworks does not store payment-card numbers. On October 23, a security incident occurred at the third-party cloud provider hosting Fireworks research machines. The next day, the attacker used it to access development machines and run an unauthorized workload; the company detected the activity the same day and has recorded no further successful intrusions into the customer platform since October 25. Fireworks links the attack to a financially motivated group and LLMJacking, the sale of tokens providing unauthorized access to language models. The company brought in Palo Alto Networks Unit 42, replaced credentials, restricted network paths and temporarily disabled self-service dataset uploads and downloads for batch inference and training. According to Bloomberg, Notion and Cursor were among those notified. Notion said the incident affected fewer than 1% of its workspaces. The new dataset contained Notion AI chat transcripts used for the Insights feature; for the vast majority of affected workspaces, they contained no author or workspace labels and no tool-call results. Notion disabled Insights, stopped serving open-weight models through Fireworks and advised affected customers to rotate secrets they had entered into Notion AI during the incident period.