🔍 Read the full analysis: Fireworks AI Breach: How To Check For Possible Exposure 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 reached 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 affected dataset, involving fewer than 1% of workspaces. Fireworks has not disclosed the number of affected customers or named the cloud provider involved.
Fireworks AI said in a November 9 security update that an incident it first disclosed in October exposed account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. Notion separately said chat transcripts from its AI Insights feature may have been included in a dataset attackers could access, affecting fewer than 1% of its workspaces, according to the company.
Fireworks, which provides infrastructure for companies running and fine-tuning AI models, described two routes into its systems. In the first, identified on October 6, someone used what the company called internal Fireworks credentials to read environment variables from customers’ evaluation jobs. Such variables can contain configuration information, including keys or tokens, though Fireworks has not said exactly what information was obtained through this route.
The company later reported a separate incident involving a third-party cloud provider that hosted Fireworks research and development machines. Fireworks said the provider had a security incident on October 23, and that an unauthorized party used the access on October 24 to reach development machines and run an unauthorized workload that led to additional customer-data impact. Fireworks said it detected that activity the same day.
Fireworks lists resource metadata, billing details and, for certain customers, a subset of incomplete model weights and datasets among the information accessed. It says payment card numbers were not affected because it does not store them, and that it has detected no impact to its Inference, Training SDK and Nexus products. The company said those products are zero data retention by default. As the investigation continues, it has disabled self-service dataset uploads and downloads used by Batch Inference and dataset-based training.
Fireworks AI Breach What customers should check
A November 9 update expanded the reported exposure from account and billing information to secrets, datasets and incomplete models for a limited set of accounts.
What may have been exposed
The reported categories do not apply to every customer; datasets and incomplete model weights were limited to certain accounts.
Accounts and billing
Fireworks said account and billing information was accessed. Payment card numbers were not affected because Fireworks does not store them.
Secrets and data
Secrets, datasets and incomplete models were affected for a limited set of accounts. The exact materials exposed remain unclear.
Notion AI Insights
Notion said chat transcripts may have been in a dataset attackers could access. This does not confirm that transcripts were taken.
How the incident expanded
Fireworks described two routes into its systems, with later findings broadening the October account.
Internal Fireworks credentials were used to read environment variables from customer evaluation jobs.
An unauthorized party accessed development machines hosted by a third-party cloud provider and ran an unauthorized workload.
Fireworks reported additional impact to customer data. Its investigation remains ongoing.
What customers can review
Check your organization’s use of Fireworks during the relevant period and seek account-specific details.
- Review Fireworks notices and identify accounts, projects and datasets hosted there.
- Ask whether specific secrets or credentials in affected environments were exposed; replace them following Fireworks guidance.
- Ask which resources and data were affected and whether stored secrets need rotation.
- Notion users should follow notices about potentially affected workspaces.
What remains unsettled
The available disclosures leave important questions open for customers.
- The number of affected customers
- The third-party cloud provider’s name
- How the internal credentials were obtained
- What happened to data attackers could access
- Whether potentially accessible data was taken or shared
- Whether every transcript in the Notion dataset was accessed
- The complete customer-by-customer scope
- When dataset upload and download limits will end
What Customers May Need to Review
The reported exposure matters because Fireworks operates infrastructure that businesses use to process data and develop AI models. Information on the platform can include not only account records but also datasets and model materials tied to a customer’s products. The company’s description does not establish that every listed category was accessed for every customer; it says datasets and incomplete weights were affected only for a limited set of accounts.
Customers using Fireworks may want to check communications from the company and review which accounts, projects and datasets were hosted there during the relevant period. If credentials or secrets were stored in affected environments, customers should ask Fireworks whether those specific materials were exposed and follow its guidance on replacing them. This is a precaution, not confirmation that any particular customer’s credentials were stolen.
Notion’s disclosure offers a concrete example of possible downstream exposure: it said transcripts from Notion AI Insights were in a dataset that attackers may have accessed, and that fewer than 1% of workspaces were involved. That statement does not establish that the transcripts were taken, published or used. It does show why customers should seek details about the contents and handling of any affected datasets rather than relying only on broad product-level assurances.
Products Worth Considering
Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, White Silver
Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB‑C Charging, Up to 2X More Active Noise Cancelling, Transparency Mode, Adaptive
Jackery Explorer 1000 v2 Portable Power Station, 1070Wh, 1500W
As an affiliate, we earn on qualifying purchases.
How the Disclosures Expanded
Fireworks’ October 9 bulletin described misuse of internal credentials and access to environment variables in a limited number of customer accounts. At that point, the company said it had not detected unauthorized access to customer models, datasets, training data, inference traffic or personal information. Its November 9 update changed that account, reporting later-discovered impacts to account and billing information and, for some customers, secrets, datasets and incomplete models.
Fireworks’ timeline says it began containment on October 6 and started notifying affected customers on October 7. It rotated employee API keys on October 9 and later revoked additional user keys and rotated service-account tokens. The company said it detected the October 24 activity on the same day and had found no further evidence of successful unauthorized access on the customer-facing platform after October 25.
Notion said Fireworks first contacted it on November 2 about a dataset believed to contain synthetic test data. On November 6, Fireworks told Notion that malicious actors may have accessed potential customer data; Notion said the dataset was confirmed on November 8. Fireworks said it notified law enforcement and engaged Palo Alto Networks Unit 42 for forensic work.
“For a limited set of accounts, we also discovered impact to secrets, datasets, and incomplete models.”
— Fireworks AI, November 9 security update
What the Investigation Has Not Settled
Fireworks has not named the third-party cloud provider, disclosed how many customers were affected, or explained how the internal credentials used in the first activity were obtained. It also has not said what happened to information the attackers could access, whether they retained or shared it, or what “incomplete” means in the description of model weights.
The company’s statement that it has not detected further successful access since October 25 is limited to its investigation and the systems it describes; it does not establish what attackers did with data already accessed. Fireworks has also not identified a responsible group. The source material says the company described evidence as indicating links to a cybercrime group, but the provided account ends before naming or explaining that assessment. Attribution and the full scope remain unsettled.
Notion’s disclosure concerns potential access to a dataset, not confirmation that every transcript in it was accessed or extracted. Neither company has published a complete customer-by-customer inventory in the material available here. It is also unclear whether further categories of information or affected accounts will be identified.
Customer Notices and Forensic Findings
Fireworks says its investigation is ongoing, with law enforcement and Unit 42 involved. Customers should watch for direct notices from Fireworks and consult its security updates for any revised scope or instructions. The temporary limits on self-service dataset uploads and downloads are in place while the company investigates; Fireworks has not given a date for restoring those functions.
For organizations that used the service, the next useful information would be a clear account of which resources and data were affected, whether stored secrets require rotation, and what safeguards apply to the affected cloud and development systems. Notion users should follow notices from Notion about potentially affected workspaces. Until the companies provide more detail, the number of affected customers and the fate of accessed data remain unknown.
Key Questions
What did Fireworks AI say was exposed?
Fireworks said attackers accessed account and billing information and, for a limited set of accounts, secrets, datasets and incomplete model weights. It also listed resource metadata among the information available through the affected application.
Were payment card numbers affected?
Fireworks said it does not store payment card numbers and that they were not impacted. It did report exposure of other billing information, including billing and shipping addresses, invoice and payment history, account balances and credit usage.
Was Notion AI data involved?
Notion said chat transcripts from its AI Insights feature were in a dataset attackers may have accessed. It reported that fewer than 1% of workspaces were involved, but did not say that every transcript was accessed or taken.
How can a customer check for possible exposure?
Check for direct security notices from Fireworks or Notion and ask the relevant provider whether your account, projects, datasets or secrets were affected. Review credentials used in affected environments and rotate them if the provider advises it or if your security team determines they may have been exposed. A general notice alone does not confirm that a specific account was affected.
What remains unknown about the breach?
Fireworks has not disclosed the cloud provider’s identity, the total number of affected customers, how the internal credentials were obtained, or what happened to data the attackers accessed. Its investigation is ongoing.
Source: ThorstenMeyerAI.com
![Android Auto Tests Quick Settings And Hilarious ‘Jimothy’ Weather Easter Egg [Gallery]](https://techtrendtrove.com/wp-content/uploads/2026/09/android-auto-tests-quick-settings-and-hilarious-jimothy-weather-easter-egg-galle-featured-560x300.jpg)
