TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Fireworks AI’s November 9 update says its October security incident 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 were in a dataset attackers may have accessed, affecting fewer than 1% of workspaces, according to the company. The cloud provider involved, total number of affected customers and fate of any accessed data remain unclear.
Fireworks AI said in a November 9 update that an October security incident reached further than the company first reported, affecting account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. Notion separately said chat transcripts from its Notion AI Insights feature were in a dataset attackers may have accessed, and that fewer than 1% of workspaces were affected.
Fireworks, which provides services for running and fine-tuning open AI models, described two routes into its systems. In October, someone used what the company called “internal Fireworks credentials” to read environment variables from customers’ evaluation jobs. Those variables can contain credentials such as API keys. Fireworks later said attackers used access through a third-party cloud provider hosting its R&D machines to reach development machines and run an unauthorized workload on October 24.
The company’s November update says the affected internal application could provide access to resource metadata, including identifiers and descriptions, and billing information, including addresses, invoice and payment history, account balances and credit usage. For certain customers, Fireworks says a subset of datasets and incomplete model weights was accessed. It has not explained 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 the company describes as zero data retention by default. Fireworks says it notified law enforcement and engaged Palo Alto Networks’ Unit 42 for forensic work. These are statements from the company; the provided material does not include an independent forensic report.
Risks for AI Platform Customers
The expanded scope matters because companies use Fireworks to run models and handle data used in model development. Affected datasets, secrets or model weights could have consequences beyond ordinary account administration, depending on what each customer stored and whether credentials remain usable. Fireworks has not disclosed the number of affected customers or the specific contents of the accessed datasets and secrets.
Notion’s disclosure shows that customer data handled through a downstream product may also be involved. The company says Notion AI Insights chat transcripts were in a dataset that attackers may have accessed, and puts the share of affected workspaces at fewer than 1%. That figure is Notion’s estimate; the source material does not give a workspace count or describe what the transcripts contained.
Customers who used the affected services may need to identify relevant credentials and data, check for unusual account activity, and follow any direct notices from Fireworks or their own vendors. The disclosures do not establish that accessed information was published, misused or used to access customer systems.
Products Worth Considering
Sony WH-1000XM6 Wireless Noise-Canceling Headphones, Black
Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB‑C Charging, Up to 2X More Active Noise Cancelling, Transparency Mode, Adaptive
DJI Osmo Action 4 Essential Combo Waterproof 4K Action Camera
As an affiliate, we earn on qualifying purchases.
From October Alert to Update
Fireworks’ first bulletin, dated October 9, described misuse of internal credentials and access to environment variables in a limited number of customer accounts. At that time, the company said it had not detected unauthorized access to customer models, datasets, training data, inference traffic or personal information. Its November 9 update added impact to account and billing information, as well as secrets, datasets and incomplete models for a limited set of accounts.
According to Fireworks’ timeline, the company identified the initial activity on October 6 and began notifying affected customers on October 7. It rotated employee API keys on October 9 and revoked more user API keys and rotated service-account tokens the following day. Fireworks says the third-party provider experienced a security incident on October 23; attackers used that access the next day to reach development machines and run an unauthorized workload. The company says it detected that activity on October 24 and has not detected further successful unauthorized access by the actor on its customer platform since October 25.
Notion says Fireworks contacted it on November 2 about a dataset initially described as synthetic test data. Fireworks later told Notion on November 6 that potential customer data may have been accessed, and confirmed the dataset on November 8, according to Notion. Fireworks published its expanded update the next day.
““For a limited set of accounts, we also discovered impact to secrets, datasets, and incomplete models.””
— Fireworks AI
Scope and Data Fate Remain Open
The disclosures do not identify the third-party cloud provider, explain how the internal credentials were first obtained, or state how many Fireworks customers were affected. Fireworks has not said what happened to the data after access, whether it was copied or shared, or whether any accessed secrets were used. The company says its investigation remains ongoing, so the reported scope may change.
Notion’s statement describes possible access to a dataset containing chat transcripts, rather than confirming that every transcript in it was viewed or taken. Its estimate of fewer than 1% of workspaces does not specify the number of workspaces involved. The source material also does not provide details on the content or sensitivity of those transcripts.
Fireworks says it detected no impact to the named zero data retention products, but the available information does not describe the forensic evidence or testing behind that finding. Customers should treat it as the company’s current assessment.
Customer Notices and Investigation
Fireworks says it is continuing its investigation with forensic support from Palo Alto Networks Unit 42 and has notified law enforcement. It may publish further information if investigators establish more about the access or affected data. Customers who receive a notice can compare the affected services and data categories with their own use and contact Fireworks for account-specific details.
Organizations using credentials stored in evaluation jobs or services tied to the incident can review whether those credentials require rotation and check relevant access logs. They should also identify whether they placed datasets, secrets or model weights in affected accounts. These are practical checks based on the categories Fireworks disclosed; the available material does not establish that every customer needs the same response.
Notion customers can look for communications from Notion about whether their workspace was among those affected. Further clarity depends on customer-specific notices and the results of the ongoing investigation. Neither company’s provided statement sets a date for another public update.
Key Questions
What data does 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 model weights. It also lists resource metadata among information the affected internal application could access.
Were payment card numbers exposed?
Fireworks says it does not store payment card numbers and that they were not affected. This is the company’s statement in its November 9 update.
Was Notion AI data involved?
Notion says chat transcripts from its AI Insights feature were in a dataset attackers may have accessed. Notion estimates fewer than 1% of workspaces were affected; it has not provided a workspace count in the supplied material.
What should Fireworks customers check?
Customers can review notices from Fireworks, identify whether they used affected accounts for credentials, datasets or model weights, and check relevant account activity. The disclosures do not establish that every customer was affected or that accessed data was misused.
Source: Thorsten Meyer AI
