🔍 Read the full analysis: What AI Customers Should Review As The Fireworks Breach Grows on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Fireworks AI’s November 9 update says an incident first disclosed in October affected account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. Notion says chat transcripts from its AI Insights feature may have been in an accessed dataset, affecting fewer than 1% of its workspaces. The number of affected Fireworks customers, the cloud provider involved and what happened to accessed data remain unclear.
Fireworks AI said on November 9 that a security incident it first disclosed in October reached further than initially reported, exposing account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. The update matters to companies using the platform to run or fine-tune AI models because some customer data may have been accessed through two separate routes, including a third-party cloud provider hosting Fireworks research and development machines.
Fireworks’ first bulletin, published October 9, described misuse of internal Fireworks credentials to read environment variables from customer evaluation jobs. Those variables can contain settings such as API keys and tokens. At the time, Fireworks said it had not detected unauthorized access to customer models, datasets, training data, inference traffic or personal information. Its November update revised that account: it said the incident also affected account and billing information and, for some accounts, secrets, datasets and incomplete model weights.
Fireworks described a second route. A third-party cloud provider hosting its research and development machines experienced a security incident on October 23. Fireworks said an unauthorized party used that access on October 24 to reach development machines and run an unauthorized workload that led to additional customer data impact. The company says it detected the activity the same day and has detected no further successful access by the actor on the customer-facing platform since October 25.
The company lists exposed information as resource metadata, billing details and, for certain customers, a subset of datasets and incomplete model weights. Billing information could include addresses, invoice and payment history, account balances and credit usage. Fireworks says it does not store payment card numbers and they were not affected. It also says it has not detected an impact to its Inference, Training SDK or Nexus products. Fireworks says it notified law enforcement and brought in Palo Alto Networks Unit 42 for forensic work.
What AI Customers Should Review As the Fireworks Breach Grows
Fireworks AI’s November update expanded the scope of an incident first disclosed in October. Customers should review affected accounts, data and credentials while key details remain unknown.
What may be affected
Fireworks says impact varied by account; it has not said every category was accessed for every customer.
Metadata and billing
Billing details may include addresses, invoices, payment history, balances and credit usage.
Secrets and assets
Some accounts may have been affected through secrets, datasets and incomplete model weights.
Possible transcripts
Notion says chat transcripts were in a dataset attackers may have accessed; this does not establish they were read or shared.
How the incident expanded
Fireworks described two routes involving internal credentials and a third-party cloud provider.
What customers can review
Use direct provider notices and guidance to determine whether your own services and data may be involved.
- Check which accounts, datasets and services may fall within the affected scope.
- Review credentials and secrets associated with relevant customer evaluation jobs.
- Look for direct notices from Fireworks and follow its account-specific guidance.
- Note that self-service dataset uploads and downloads for Batch Inference and dataset-based training were disabled during the investigation.
Risks for AI Platform Customers
The expanded account matters because AI providers can hold sensitive material beyond prompts and outputs. Customers may use a platform to upload datasets, credentials and fine-tuned model files; access to any of those could expose business information or assets used to build a product. Fireworks has not said that every listed category was accessed for every customer, describing the impact to secrets, datasets and incomplete models as limited to certain accounts.
Notion has separately said that chat transcripts from its Notion AI Insights feature were in a dataset that attackers may have accessed. It estimates the share of affected workspaces at fewer than 1%. That statement gives customers one specific example of potential exposure, but it does not establish that every transcript was read or that the data was used or distributed. Companies using Fireworks may need to check their own records and follow direct notices from the provider.
The incident also highlights the reach of a supplier breach: customers can face exposure through a service they use to host or develop AI, even if their own systems were not reported compromised. At this stage, the public information does not establish the full scope or the consequences for affected customers.
Products Worth Considering
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
LG UltraGear 25G590B-B 25-Inch Full HD 1000Hz Gaming Monitor
Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, White Silver
As an affiliate, we earn on qualifying purchases.
From October Disclosure to Update
Fireworks said it identified activity and began containment on October 6, then started notifying affected customers on October 7. On October 9, it published its first bulletin and said it had rotated employee API keys. The company said it revoked more user API keys and rotated service-account tokens the following day. Its initial public account focused on credentials used to read environment variables from a limited number of customer accounts.
The later cloud-provider incident occurred on October 23, followed by unauthorized activity on Fireworks development machines the next day. Fireworks says it detected that activity on October 24. The company’s November 9 update therefore expanded the public account more than a month after its first detection, adding data categories and a second access route.
Notion said Fireworks contacted it on November 2 about a dataset initially understood to contain synthetic test data. On November 6, Fireworks told Notion that malicious actors may have accessed potential customer data, and it confirmed the dataset on November 8, according to Notion’s advisory. Fireworks says it disabled self-service dataset uploads and downloads used by Batch Inference and dataset-based training while investigating.
“For a limited set of accounts, we also discovered impact to secrets, datasets, and incomplete models.”
— Fireworks AI, November 9 security update
Scope and Data Use Still Unknown
Fireworks has not publicly identified the third-party cloud provider, said how many customers were affected, or explained how the internal credentials used in the first route were obtained. It has also not specified what “incomplete” means for the model weights, how much data was accessed, or whether the accessed material was copied, retained, shared or used.
Notion’s estimate addresses its own workspaces, not the total number of Fireworks customers or records involved. Fireworks says its investigation is ongoing and may reveal additional information. Its statement that it has detected no further successful access on the customer-facing platform since October 25 describes what its investigation has found so far; it does not resolve the questions about data accessed earlier.
Customer Notices and Investigation
Fireworks says it is continuing its investigation with help from Palo Alto Networks Unit 42 and has notified law enforcement. It says customer notifications began October 7, but the public update does not provide a complete customer count or a timetable for further findings. Customers should look for direct notices from Fireworks and review which accounts, datasets or credentials may fall within the affected services, using the provider’s specific guidance rather than assuming every account was exposed.
The company’s temporary suspension of self-service dataset uploads and downloads for Batch Inference and dataset-based training remains a stated precaution during the investigation. Fireworks has not announced when those functions will return. Further updates could clarify the affected customer set, the cloud-provider incident and the disposition of accessed data; those details are not established in the information currently available.
Key Questions
What did Fireworks AI say was affected?
Fireworks says the incident affected account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. It also lists resource metadata among the information the affected internal application provided access to.
Were payment card numbers exposed?
Fireworks says it does not store payment card numbers and that they were not affected. It says other billing information, including invoices, payment history and account balances, was impacted.
What did Notion say about its customers?
Notion said chat transcripts from its AI Insights feature were in a dataset attackers may have accessed. It put the share of potentially affected workspaces at fewer than 1%; that does not establish that every transcript was accessed.
What remains unknown about the incident?
Fireworks has not named the cloud provider, provided a total count of affected customers, explained how the initial credentials were obtained or said what happened to data that may have been accessed. The investigation is ongoing.
Source: ThorstenMeyerAI.com
