🔍 Read the full analysis: Fireworks AI Breach Widens: Reviewing Customer Data Risks 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 exposed 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 workspaces. The number of affected customers, the cloud provider involved and what happened to accessed data remain unknown.
Fireworks AI said on November 9 that an October security incident exposed account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models—a broader impact than the company described in its initial October notice. Notion separately said chat transcripts from its Notion AI Insights feature may have been included in a dataset attackers could access, affecting fewer than 1% of workspaces.
Fireworks’ update describes two routes into its systems. In the first incident, identified on October 6, someone used what the company called internal Fireworks credentials to read environment variables from customer evaluation jobs. Those variables can contain configuration information such as API keys or tokens. Fireworks began notifying affected customers on October 7, then said it rotated employee API keys and revoked additional user keys and service-account tokens.
A second development involved a third-party cloud provider hosting Fireworks R&D machines. Fireworks says the provider experienced a security incident on October 23. On October 24, an unauthorized party used that access to reach Fireworks development machines and run an unauthorized workload that led to additional customer-data impact. The company says it detected that activity the same day and has not detected further successful unauthorized access by the actor on the customer platform since October 25.
Fireworks lists exposed information as resource metadata; billing details, including addresses, invoice and payment history, account balances and credit usage; and, for certain customers, a subset of datasets and incomplete model weights. It says it does not store payment card numbers and they were not affected. It also says it has detected no impact to Inference, Training SDK or Nexus, which it describes as zero-data-retention by default. As a precaution, it disabled self-service dataset uploads and downloads used by Batch Inference and dataset-based training while the investigation continues.
Fireworks AI breach widens Customer data risks
A November update says an October incident exposed account and billing information, plus secrets, datasets and incomplete models for some accounts. The full scope and fate of accessed data remain unknown.
What data was involved
Reported exposure varied by account; the statements do not say every category was accessed for every customer.
Metadata and billing
Resource metadata and billing details, including addresses, invoices, payment history, balances and credit usage.
Secrets and AI assets
Fireworks reported impact to secrets, datasets and incomplete model weights for a limited set of accounts.
AI Insights transcripts
A dataset attackers may have accessed included chat transcripts from Notion AI Insights.
How access unfolded
Fireworks described two routes into its systems during October.
On October 6, internal credentials were used to read environment variables from customer evaluation jobs.
After a cloud provider incident on October 23, an unauthorized party reached Fireworks R&D machines on October 24 and ran an unauthorized workload.
Fireworks rotated or revoked keys and tokens, began customer notices and paused specified dataset uploads and downloads during its investigation.
What remains unclear
Customers and readers do not yet have a complete account of the incident.
- Fireworks reported account and billing data impact.
- Payment card numbers are not stored by Fireworks and were not impacted.
- Fireworks says it detected no impact to Inference, Training SDK or Nexus.
- Total affected Fireworks customers and records.
- The cloud provider’s identity and how internal credentials were obtained.
- Whether accessed data was copied, retained, published or misused.
Risks for AI Customers
The expanded scope matters because Fireworks provides infrastructure companies use to run and fine-tune AI models. Customer evaluation jobs, datasets and model artifacts may contain sensitive business information or support products built on a company’s own data. Exposure of credentials could also create risks beyond the initial access, although Fireworks has not said whether any accessed secrets were used elsewhere.
Notion’s disclosure gives the incident a direct connection to a widely used workplace product. Notion says a dataset that may have been accessed included chat transcripts from Notion AI Insights, and that fewer than 1% of workspaces were affected. That figure is Notion’s account of its own exposure; it does not establish the total number of Fireworks customers or records involved. Customers may need to review notices from both providers and determine whether their own data or credentials were included.
Products Worth Considering
Bose QuietComfort Headphones (2nd Gen), Wireless Over-Ear Noise-Cancelling Headphones, Black
Bose Lifestyle Ultra Wireless Home Speaker, White Smoke
Bose QuietComfort Earbuds (2nd Gen) – True Wireless Bluetooth Earbuds with Active Noise Cancellation
As an affiliate, we earn on qualifying purchases.
From Initial Notice to Expanded Scope
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—including prompts and outputs—or personal information. Its November 9 update revised that picture, reporting impact to account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models.
Notion says Fireworks contacted it on November 2 about a small dataset initially understood to contain synthetic test data. On November 6, Fireworks told Notion that malicious actors may have accessed potential customer data; the dataset was confirmed on November 8, according to Notion. Fireworks says it notified law enforcement and engaged Palo Alto Networks’ Unit 42 for forensic work. The company has not named the third-party cloud provider or a threat group in the supplied statements.
“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 Unknown
The companies have not disclosed how many Fireworks customers or records were affected. Fireworks has not identified the cloud provider involved, explained how the internal credentials were first obtained, or said whether accessed data was copied, retained, published or misused. It also has not defined what “incomplete” means for the model weights, leaving unclear whether they were partial files, unfinished training outputs or another form of artifact.
The companies’ statements do not establish that every category was accessed for every customer. Fireworks says some impacts applied only to a limited set of accounts or certain customers, while Notion describes a dataset that may have included transcripts. The investigation remains ongoing, and Fireworks says it may reveal additional information. Its statement that it detected no further successful access after October 25 describes the company’s current findings, not a final determination of what occurred before that date.
Investigation and Customer Notices
Fireworks says its investigation with Palo Alto Networks Unit 42 is continuing and that law enforcement has been notified. The company has also suspended specified self-service dataset uploads and downloads while it examines the incident. Customers should look for direct communications from Fireworks or Notion about affected accounts and the data categories involved; the available statements do not give a date for a final report or restoration of the paused functions.
Further updates will need to clarify the number of affected customers, the cloud provider’s role, the status of accessed datasets and model files, and whether any credentials require additional action. Until those details are released, the confirmed account is limited to the companies’ disclosures and their stated findings so far.
Key Questions
What did Fireworks AI say was accessed?
Fireworks said account and billing information were affected and that, for a limited set of accounts, the incident also involved secrets, datasets and incomplete models. It also listed resource metadata among the information accessible through the affected application.
Were payment card numbers exposed?
Fireworks says it does not store payment card numbers and that they were not impacted. The company did report access to other billing information, including addresses, invoice and payment history, balances and credit usage.
Were Notion AI conversations involved?
Notion said chat transcripts from its Notion AI Insights feature were in a dataset attackers may have accessed. It said fewer than 1% of workspaces were affected; the statement does not identify a total number of workspaces or transcripts.
How many customers were affected?
Fireworks has not disclosed a total number of affected customers. Its update describes some impacts as applying to a limited set of accounts or certain customers, and the investigation is ongoing.
What happens next?
Fireworks says it is continuing its investigation with Unit 42, has notified law enforcement and has temporarily disabled specified dataset upload and download functions. No final investigation timeline or date for restoring those functions has been announced in the supplied material.
Source: ThorstenMeyerAI.com
