🔍 Read the full analysis: Reviewing AI Data After The Fireworks AI Breach Widens 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 October security incident reached account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. Notion says transcripts from its AI Insights feature may have been in an accessed dataset, affecting fewer than 1% of workspaces. The number of affected Fireworks customers and the identity of the third-party cloud provider remain unknown.
Fireworks AI said on November 9 that an October security incident affected more information than it had disclosed initially, including account and billing details and, for a limited set of accounts, secrets, datasets and incomplete models. Notion separately said transcripts from its Notion AI Insights feature may have been included in a dataset attackers could access, with fewer than 1% of workspaces affected, according to the company.
Fireworks, which provides infrastructure for companies to run and fine-tune AI models, described two routes of access. In October, an unauthorized party used internal Fireworks credentials to read environment variables from customers’ evaluation jobs. Later, a security incident at an unnamed third-party cloud provider hosting Fireworks research and development machines gave an attacker access to development machines and enabled an unauthorized workload on October 24. Fireworks said it detected that activity the same day.
The company’s November update says the affected internal application provided access to resource metadata and billing information, including billing and shipping addresses, invoices, payment history, account balances and credit usage. For some customers, a subset of datasets and incomplete model weights was accessed. Fireworks did not say how many customers were affected or explain what “incomplete” means in this case.
Fireworks said it does not store payment-card numbers and that they were not affected. It also said it had detected no impact to its Inference, Training SDK and Nexus products, which it describes as zero-data-retention by default. The company said it disabled self-service dataset uploads and downloads used by Batch Inference and dataset-based training while its investigation continues. It has notified law enforcement and engaged Palo Alto Networks’ Unit 42 for forensic work.
Fireworks AI breach scope widens
A November 9 update added account and billing details to the reported exposure. Some accounts may also have had secrets, datasets, or incomplete models accessed.
What may have been accessed
The reported exposure varies by account; the statements do not establish that every customer or product was affected.
Billing and resource details
Fireworks reported access to billing records and resource metadata.
Secrets and development data
Some accounts may have had secrets, datasets, and incomplete model weights accessed.
AI Insights transcripts
Notion said transcripts were in a dataset attackers may have accessed.
How the account changed
Fireworks described two access routes and revised its initial assessment as the investigation progressed.
In October, an unauthorized party used Fireworks credentials to read environment variables from customer evaluation jobs.
A later incident at an unnamed cloud provider enabled access to development machines and an unauthorized workload on October 24.
On November 9, Fireworks reported additional potentially exposed information; the investigation continues.
What remains unclear
The available statements leave key questions about the incident’s reach and consequences unanswered.
- Notion says fewer than 1% of its workspaces may be affected.
- Fireworks says payment-card numbers are not stored and were not impacted.
- Fireworks detected no further successful access to its customer-facing platform after October 25.
- How many Fireworks customers were affected.
- The third-party cloud provider’s identity.
- Whether accessed data was copied, retained, published, or used.
Risks for AI Customer Data
The incident matters because companies using AI infrastructure providers may entrust them with proprietary datasets, model-development materials and account records. Exposure of those materials could create commercial, privacy or security concerns for customers, although the available information does not establish that the data was used or shared after access.
Notion’s disclosure gives the incident a concrete customer impact: it says Notion AI Insights chat transcripts were in a dataset that attackers may have accessed. Notion put the share of potentially affected workspaces below 1%. That figure applies to Notion workspaces, not to Fireworks customers overall, whose number has not been disclosed.
The widening account also shows why the scope of a breach can change as an investigation proceeds. Fireworks’ first bulletin said it had not detected unauthorized access to customer models, datasets, training data, inference traffic or personal information. The later update added account and billing information and limited access to secrets, datasets and incomplete models. The change is a revised account of the same incident, not confirmation that every customer or product was affected.
Products Worth Considering
DJI Osmo Action 4 Essential Combo Waterproof 4K Action Camera
Jackery Solar Generator 1000 V2 with 100W Solar Panel, 1024Wh LiFePO4 Battery
DJI Osmo Mobile 7P Gimbal Stabilizer with Mic Mini Transmitter, Infinity Black
As an affiliate, we earn on qualifying purchases.
From Initial Notice to Update
Fireworks said it identified suspicious activity on October 6 and began containment. It started notifying affected customers on October 7 and published its first bulletin on October 9, after rotating employee API keys. The company revoked more user API keys and rotated service-account tokens on October 10.
In that initial notice, Fireworks said it had not detected evidence that customer models, datasets, training data, inference traffic or personal information had been accessed. The later cloud-provider incident occurred on October 23, according to Fireworks; the unauthorized workload ran on October 24. Fireworks said it had detected no further successful access by the threat actor on the customer-facing platform after October 25.
Notion said Fireworks contacted it on November 2 about a small dataset initially described as 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. Fireworks published its broader update on November 9. Its account and Notion’s advisory establish the dates and reported findings; they do not identify the cloud provider or the attacker.
“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 Unresolved
Several central details remain unknown. Fireworks has not named the third-party cloud provider, said how many customers were affected, or explained how the internal credentials used in the first access were obtained. It has also not disclosed what happened to any information attackers accessed, including whether it was copied, retained, published or used.
The company has not specified which customers’ datasets or secrets were involved, nor what kinds of secrets were exposed. Its description of model weights as “incomplete” does not establish whether they were partial copies or unfinished training outputs. Fireworks said its investigation may reveal more information, so the reported scope could still change.
Fireworks’ statement that it had detected no further successful unauthorized access to its customer platform after October 25 does not answer every question about the separate development-machine access or the fate of previously accessed data. The available statements do not provide an independent forensic report or a named attribution for the attackers.
Investigation and Customer Notices
Fireworks says its investigation is ongoing, with Unit 42 conducting forensic work and law enforcement notified. The company has not announced a date for a final report. Its temporary restriction on self-service dataset uploads and downloads remains a precaution while the investigation proceeds, according to its update.
Customers should look for direct notices from Fireworks about whether their accounts or data were involved. Notion has identified a possible effect on fewer than 1% of its workspaces, but the source material does not detail what steps it has asked affected users to take. Further disclosures from Fireworks, Notion or investigators may clarify the affected customer count, data handling and security changes.
Key Questions
What information does Fireworks say was affected?
Fireworks reported access to account and billing information and, for a limited set of accounts, secrets, datasets and incomplete model weights. It also listed resource metadata such as identifiers, names, descriptions and creation times.
Were payment-card numbers exposed?
Fireworks said it does not store payment-card numbers and that they were not impacted. This is the company’s account in its November 9 update.
What did Notion say was affected?
Notion said transcripts from its AI Insights feature were in a dataset attackers may have accessed. It said fewer than 1% of workspaces were potentially affected.
How many Fireworks customers were affected?
Fireworks has not disclosed an overall customer count. Its description of a “limited set” of accounts does not specify a number or percentage.
Who carried out the attack?
Fireworks has not named a group or identified the third-party cloud provider. The supplied statements do not establish who was responsible or what happened to the accessed data.
Source: ThorstenMeyerAI.com
