How To Check AI Customer Data After The Fireworks Breach
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: How To Check AI Customer Data After The Fireworks Breach on ThorstenMeyerAI.com

Before you orderOffer from Amazon

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
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Fireworks AI’s November 9 update says an incident disclosed in October also affected 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 included in accessed data, affecting fewer than 1% of workspaces. The number of affected Fireworks customers and what happened to accessed data remain unknown.

Fireworks AI said in a November 9 security update that an incident first disclosed in October also 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 in a dataset attackers accessed, affecting fewer than 1% of its workspaces, according to the company.

Fireworks’ account describes two routes into its systems. On October 6, the company identified misuse of internal Fireworks credentials and began containment. It said the credentials were used to read environment variables from customer evaluation jobs—settings that can contain keys or tokens. Fireworks began notifying affected customers October 7 and published its first bulletin October 9.

A second incident followed. Fireworks said a third-party cloud provider hosting its research and development machines had a security incident October 23. On October 24, an unauthorized party used that access to reach Fireworks development machines and run an unauthorized workload, causing additional customer data impact. The company said it detected the activity that day and has not detected further successful access by the threat actor on the customer platform since October 25.

The newly disclosed information includes resource metadata, such as identifiers and descriptions, and billing details including addresses, invoice and payment history, account balances and credit usage. Fireworks said some customers’ datasets and incomplete model weights were accessed. It said it does not store payment card numbers and has not detected impact to Inference, Training SDK or Nexus, which it describes as zero-data-retention by default. Fireworks also temporarily disabled self-service dataset uploads and downloads used for Batch Inference and dataset-based training while it investigates.

At a glance
updateWhen: Fireworks published the expanded update…
The developmentFireworks AI expanded its account of an October security incident, disclosing additional exposure of customer information and data.
AI Security · Briefing

How to Check AI Customer Data After the Fireworks Breach

Fireworks AI’s November 9 update expanded what it says was affected. The full scope and what happened to accessed data remain unknown.

<1%
of Notion workspaces reportedly affected
November 9
Fireworks expanded its disclosure

What Fireworks says was affected

The reported impact varies by account; these categories do not apply to every customer.

Account data

Records and billing

Resource details, addresses, invoices, payment history, balances and credit usage may have been accessed.

Limited accounts

Secrets and model data

Fireworks also reported impact to secrets, datasets and incomplete model weights for a limited set of accounts.

Notion AI Insights

Transcripts may be included

Notion said transcripts may have been in accessed data; it reported fewer than 1% of workspaces affected.

How the disclosure changed

Fireworks’ November update widened its October account of the incident.

October bulletin
  • No detected evidence of access to customer models, datasets, training data, inference traffic or personal information.
  • Fireworks said it began customer notifications October 7.
November update
  • Account and billing information were also affected.
  • Some accounts had impact to secrets, datasets and incomplete models.

What customers can check

Use direct notices and account-specific guidance to determine what applies to your organization.

1
Check for a direct notice

Review Fireworks’ message and follow its guidance for your account.

2
Review resources and billing

Check which resources and billing accounts you used with Fireworks.

3
Review credentials and datasets

Follow Fireworks’ instructions for any affected secrets, credentials or datasets.

4
Check connected products

Consult other providers’ incident notices; Notion users can check its AI Insights advisory.

Scope still unknownFireworks has not named the cloud provider or affected customer count, or said whether accessed data was copied, retained or misused. Its investigation is ongoing.
The takeaway
Check direct provider notices and account-specific guidance; the reported exposure varies, and the full impact is not yet settled.

Risks for AI Platform Customers

The incident matters because companies use Fireworks to run and fine-tune AI models, meaning information held by an AI infrastructure provider can include more than ordinary account records. Datasets may contain customer or business material, while model weights can reflect the results of fine-tuning. Fireworks described the accessed weights as incomplete, but has not defined what that means or said how useful the material could be outside its systems.

For affected organizations, exposed billing details can create a risk of targeted fraud or convincing impersonation attempts. Access to secrets could also matter if any credentials remained usable; Fireworks says it rotated employee API keys and revoked additional user keys and service-account tokens in October. Customers should rely on direct notices and guidance from Fireworks and their own security teams rather than assume every listed data category applies to their account.

Notion’s disclosure shows how a provider incident can affect data processed for a separate product. The company says the potentially included transcripts relate to Notion AI Insights, and estimates fewer than 1% of workspaces were affected. That figure is Notion’s report about its workspaces, not a count of all Fireworks customers or all affected records.

Products Worth Considering

Sony WH-1000XM5 Premium Noise Cancelling Wireless Headphones – Midnight Blue

Sony WH-1000XM5 Premium Noise Cancelling Wireless Headphones – Midnight Blue

Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB‑C Charging, Up to 2X More Active Noise Cancelling, Transparency Mode, Adaptive

Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB‑C Charging, Up to 2X More Active Noise Cancelling, Transparency Mode, Adaptive

Logitech MX Keys S Combo Wireless Keyboard and Mouse, Graphite

Logitech MX Keys S Combo Wireless Keyboard and Mouse, Graphite

As an affiliate, we earn on qualifying purchases.

From October Disclosure to Update

Fireworks’ October 9 bulletin said it had not detected evidence of unauthorized access to customer models, datasets, training data, inference traffic or personal information. The November 9 update widened that account, saying the investigation later found impacts to account and billing information and, for some accounts, secrets, datasets and incomplete models. This is a change in what the company says it found, not confirmation that every category was accessed for every customer.

Notion said Fireworks contacted it November 2 about a dataset initially described as synthetic test data. On November 6, Fireworks told Notion that malicious actors may have accessed potential customer data; Notion said the dataset was confirmed November 8. Fireworks said it notified law enforcement and engaged Palo Alto Networks Unit 42 for forensic work. Its update says the investigation remains ongoing.

“Since then, we discovered impacts to account and billing information.”

— Fireworks AI, November 9 security update

Scope and Data Use Still Unknown

Fireworks has not named the third-party cloud provider or said how many customers were affected. It has not explained how the internal credentials were first obtained, which specific secrets or datasets were involved, or whether accessed information was copied, retained or used after the incidents. The company’s description of model weights as “incomplete” also lacks detail about how much of any model was exposed.

Fireworks has not identified the threat actor. The source material says the company’s evidence indicated links to a cybercriminal group, but the supplied account cuts off before naming or substantiating that assessment. It is not possible from the available details to independently assess the attribution. The full results of the forensic investigation and any additional customer notifications are also not yet available.

Customer Notices and Investigation

Fireworks says it is continuing its investigation, working with Unit 42 and law enforcement, and has suspended certain dataset upload and download functions as a precaution. Customers should check for direct notices from Fireworks, review which resources and billing accounts they used, and follow the company’s published instructions on any affected credentials or datasets. Organizations that sent customer information through a connected product should also consult that provider’s incident advisory; Notion users can check Notion’s notice for the reported AI Insights exposure.

The next material updates would be a clearer customer count, a more precise account of which data and systems were accessed, and findings on whether information was taken or misused. Until Fireworks releases those details, the incident’s total scope and consequences remain unsettled.

Key Questions

What information does Fireworks say was affected?

Fireworks says the incident affected account and billing information. For a limited set of accounts, it also found impact to secrets, datasets and incomplete model weights. It has not said these categories applied to every customer.

Were payment card numbers exposed?

Fireworks says it does not store payment card numbers and that they were not affected. It lists other billing information, including addresses, invoice and payment history, account balances and credit usage, as impacted.

Were Notion AI transcripts involved?

Notion said transcripts from its AI Insights feature may have been included in a dataset attackers accessed. Notion reported that fewer than 1% of its workspaces were affected; it has not provided a transcript count in the supplied material.

What should Fireworks customers do now?

Check for a direct notice from Fireworks and follow its account-specific guidance. Organizations should review relevant credentials, datasets and billing records with their security teams. Fireworks has said it rotated employee keys and revoked additional user keys and service-account tokens.

What is still unknown about the breach?

Fireworks has not disclosed the number of affected customers, named the cloud provider, explained how the initial credentials were obtained or said what happened to accessed data. Its investigation is ongoing.

Source: ThorstenMeyerAI.com

You May Also Like

Stop Cropping Wrong: How to Photograph Art for Perfect Reproduction

Stop cropping mistakes and discover how to photograph art flawlessly for perfect reproduction—your ultimate guide to capturing every detail accurately.

The Real Cost Of A Local-Inference Rig In 2026

An in-depth analysis of the hardware costs, memory constraints, and strategic choices for local AI inference setups in 2026.

Stop Blaming the Printer: Why Your Screen-to-Print Workflow Keeps Failing

Stop blaming the printer; discover the hidden pitfalls in your screen-to-print workflow that could be sabotaging your results. Are you ready to uncover them?

The #1 Reason Your Art Prints Look “Different” Than Your Screen

The #1 reason your art prints look different than your screen is due to a fundamental color mismatch caused by…