🔍 Read the full analysis: Fireworks AI Breach Expands: A Checklist For AI Customers on ThorstenMeyerAI.com
Get hardware and tech essentials 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 disclosed in October reached account and billing information, and that secrets, datasets and incomplete models were affected for a limited set of accounts. The company describes two routes of access, while customer Notion says chat transcripts from its AI Insights feature may have been in an accessed dataset affecting fewer than 1% of workspaces. The cloud provider’s identity, the total number of affected customers and what happened to accessed data remain unknown.
Fireworks AI said in a November 9 security update that an incident it first disclosed in October reached account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. The update describes an additional access route through a third-party cloud provider hosting Fireworks research and development machines, expanding the scope previously reported to customers.
Fireworks’ October 9 bulletin said someone had used internal Fireworks credentials to read environment variables from a limited number of customer evaluation jobs. At the time, the company said it had not detected unauthorized access to customer models, datasets, training data, inference traffic or personal information. In the November 9 update, Fireworks said it later discovered impacts to account and billing information and, for some accounts, to secrets, datasets and incomplete models.
The company described two stages of activity. It says it identified the first activity on October 6 and began containment, then started notifying affected customers on October 7. Fireworks says a third-party provider hosting its R&D machines experienced a security incident on October 23. On October 24, an unauthorized party used that access to reach development machines and run an unauthorized workload that led to further customer-data impact. Fireworks says it detected that activity the same day and has not detected further successful unauthorized access to the customer platform since October 25.
Fireworks lists exposed information as resource metadata; billing and shipping addresses, invoice and payment history, account balances and credit usage; and, for certain customers, a subset of incomplete model weights and datasets. The company says it does not store payment-card numbers and reports no detected impact to its Inference, Training SDK or Nexus products, which it says are zero-data-retention by default. It has disabled self-service dataset uploads and downloads used by Batch Inference and dataset-based training while its investigation continues.
Fireworks AI breach expands A checklist for AI customers
Fireworks AI’s November 9 update reports access to account and billing information, plus secrets, datasets and incomplete models for a limited set of accounts. Customers should check direct notices and assess what data and credentials may be involved.
What the update says
Reported impact varies by account; the total number of affected customers remains unknown.
Business records
Resource metadata, billing and shipping addresses, invoices, payment history, balances and credit usage were listed.
Sensitive assets
Fireworks reported impact to secrets, datasets and a subset of incomplete model weights for some accounts.
Possible transcripts
Notion said AI Insights chat transcripts were in a dataset attackers may have accessed; the figure does not mean every transcript was accessed.
Two reported access routes
Fireworks describes activity involving internal credentials and a third-party provider hosting its R&D machines.
Fireworks says activity identified October 6 involved reading environment variables from a limited number of customer evaluation jobs.
After a provider incident on October 23, an unauthorized party reached development machines on October 24 and ran an unauthorized workload.
What customers can do
Use direct notices and your own records to determine whether your organization is affected.
- Check Fireworks notices and ask whether your account or data was involved.
- Review credentials and secrets connected to affected services.
- Assess datasets and model artifacts for sensitive or business critical material.
- Notion users should review the company’s advisory and assess possible AI Insights transcript exposure.
What remains unclear
The November 9 account reflects findings to date; Fireworks says its investigation continues.
- No payment card numbers are stored by Fireworks.
- No detected impact to Inference, Training SDK or Nexus, which Fireworks says are zero data retention by default.
- No further successful unauthorized customer platform access detected after October 25.
- Identity of the third-party cloud provider and total affected customers.
- Whether accessed data was copied or further used.
- How many secrets, datasets or model artifacts were involved.
Risks for AI Platform Customers
The disclosure matters because Fireworks provides infrastructure companies use to run and fine-tune AI models. A breach involving a platform provider can expose information held in customer accounts beyond the provider’s own business records. Secrets and datasets may contain access credentials or business-sensitive material, while model weights can embody work customers have invested in training or fine-tuning.
The reported scope varies by account, and Fireworks has not supplied a total number of affected customers. Its description of weights as incomplete also leaves open how useful or sensitive the accessed material was. Customers using the platform may need to check notices from Fireworks, review credentials and data connected to affected services, and determine whether their own records or models were involved. Those are prudent incident-response steps, not evidence that every customer was affected.
Notion’s disclosure shows how the consequences may reach companies using services built on Fireworks. Notion says transcripts from its Notion AI Insights feature were in a dataset attackers may have accessed, and that fewer than 1% of workspaces were affected. That figure is Notion’s reported share of workspaces; the source material does not provide a count of affected workspaces or establish that every transcript in the dataset was accessed.
Products Worth Considering
Trezor Safe 7 Crypto Hardware Wallet with Bluetooth and Color Touchscreen
LG UltraGear 27G640A-B 27-Inch QHD IPS Gaming Monitor, 300Hz, 1ms, G-SYNC Compatible, FreeSync Premium, DisplayHDR 400
LG UltraGear 32GX850A-B 32-inch 4K UHD OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From October Bulletin to Expanded Scope
Fireworks’ first public bulletin, dated October 9, described misuse of internal credentials to read environment variables from customer evaluation jobs. Environment variables can contain configuration values such as API keys or tokens, but Fireworks’ initial statement said it had not detected access to customer models, datasets, training data, inference traffic or personal information. The November update changes that account by reporting additional impacts found during the investigation.
Fireworks says it rotated employee API keys on October 9 and revoked more user API keys and rotated service-account tokens on October 10. It says it notified law enforcement and engaged Palo Alto Networks Unit 42 for forensic work. Notion’s advisory describes a separate notification timeline: Fireworks contacted it on November 2 about a dataset then understood to be synthetic test data, said on November 6 that malicious actors may have accessed potential customer data, and confirmed the dataset on November 8.
The incident concerns a service used by companies to operate and customize AI models, rather than a single consumer-facing application. Fireworks says its investigation is ongoing, so the November 9 account is a statement of the company’s findings to date, not a final accounting of every affected record or customer.
“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 Fate Remain Unknown
Fireworks has not named the third-party cloud provider or said how many customers were affected. Its update also does not explain how the internal credentials used in the first stage were obtained, or whether the two access routes were connected. The company’s account says evidence indicated links to a cybercriminal actor, but the source material does not identify a group or provide enough detail to independently establish attribution.
It is also not clear what happened to the data accessed, whether it was copied or further used, or how many secrets, datasets and model artifacts were involved. Fireworks has not defined what it means by incomplete model weights, and Notion’s reported workspace percentage does not give a total count or clarify how many transcripts may have been accessed. Fireworks says its investigation may reveal additional information.
Further Findings and Customer Notices
Fireworks says its investigation is continuing, with forensic support from Unit 42, and that it has not detected further successful unauthorized access to the customer platform after October 25. The company says it has disabled certain dataset upload and download functions while it investigates. Its next material updates would be further findings about the affected accounts, the accessed data and any changes to its assessment of product impact.
Customers should rely on direct notices from Fireworks and their own security teams to establish whether their accounts, datasets or credentials were involved. Notion users can also refer to Notion’s advisory for the company’s account of the AI Insights dataset. The available source material does not provide a date for a final investigation report or a timeline for restoring the disabled functions.
Key Questions
What did Fireworks AI say was accessed?
Fireworks said the incident reached account and billing information. For a limited set of accounts, it also found impacts to secrets, datasets and incomplete models, along with resource metadata.
Were payment-card numbers exposed?
Fireworks says it does not store payment-card numbers and that they were not impacted. The company separately lists billing records and account details among the information affected.
Did the incident affect Notion AI users?
Notion said transcripts from its AI Insights feature were in a dataset attackers may have accessed. It reported that fewer than 1% of workspaces were affected; the source material does not give a total number or say that every transcript in the dataset was accessed.
Which Fireworks products were not reported as affected?
Fireworks said it had detected no impact to Inference, Training SDK or Nexus, which it describes as zero-data-retention by default. The company’s investigation remains ongoing.
What is still unknown about the breach?
Fireworks has not named the third-party cloud provider, given the total number of affected customers, explained how the internal credentials were obtained, or said what happened to the accessed data. It also has not detailed what it means by incomplete model weights.
Source: ThorstenMeyerAI.com
