Skip to content

SecurityFireworks AI

Under investigation

Fireworks AI expands October breach disclosure: billing data, datasets and incomplete model weights were accessed

Fireworks AI platform at a glance

In a November 9, 2026 update, Fireworks AI said its October incident reached further than first reported: account and billing information was impacted, and for a limited set of accounts also secrets, datasets and incomplete model weights. The investigation, with Unit 42, is ongoing.

Fireworks AI platform: status

Under investigationNot rated
Affected
  • Fireworks AI internal application: resource metadata and billing information (billing and shipping addresses, invoice and payment history, balances, credit usage) were accessed
  • A limited set of Fireworks AI accounts: secrets, datasets and a subset of incomplete model weights were also accessed
  • Fireworks says no impact has been detected to Inference, Training SDK or Nexus (zero data retention by default); payment card numbers are not stored and were not impacted
CVE identifiers
Not published
Last checked

What changed with Fireworks AI platform

On November 9, 2026, Fireworks AI updated its October 2026 security bulletin: the investigation has found wider impact than the company first reported. When the first bulletin was published on October 9, only Fireworks stored secrets (for example, secrets used in evaluation jobs) were known to have been accessed. Since then, Fireworks discovered impacts to account and billing information and, for a limited set of accounts, also to secrets, datasets and incomplete models (model weights). The company says its investigation is ongoing and may reveal additional information.

Fireworks says a third-party cloud provider that hosted its R&D machines experienced a security incident on October 23, 2026, and that on October 24 the unauthorized party used it to reach Fireworks development machines and run an unauthorized workload, which led to additional customer data impact. The affected internal application provided access to resource metadata (resource identifiers, display names, descriptions, creation times) and billing information (billing and shipping addresses, invoice and payment history, account balances and credit usage). Payment card numbers are not stored by Fireworks and were not impacted.

Fireworks links the evidence to a financially motivated cybercriminal group aimed at selling tokens from unauthorized access to large language models through illicit routing gateways, known as LLMJacking. It says it detected the October 24 activity the same day, has not detected further successful unauthorized access on the platform customers use since October 25, and has not detected any impact to Inference, Training SDK or Nexus, which are zero data retention by default. Fireworks notified law enforcement, is working with Palo Alto Networks Unit 42, revoked and replaced credentials and service accounts, and has disabled self-serve dataset uploads and downloads used by Batch Inference and dataset-based training while it investigates. Affected customers are being notified with account-specific details and recommended actions.

How to fix it: Fireworks AI platform

  1. 1. Monitor

    Check whether Fireworks has notified your account: the company is notifying affected customers with the impact details and recommended response actions that apply to them, and says to reply to the incident notification email or contact security-notice@fireworks.ai.

    fireworks.ai (opens in a new tab)
  2. 2. Configuration

    Rotate third-party API keys and tokens you stored as secrets in Fireworks, especially in evaluation jobs: the October bulletin said environment variables, including API keys and tokens stored as secrets, were captured in certain affected accounts.

    fireworks.ai (opens in a new tab)

Advisories

Why Fireworks AI platform matters for businesses

Why it matters: if your team fine-tunes models or stores keys and datasets on Fireworks, treat this as a credential and data-hygiene event, not just a vendor headline. Check whether your account was notified, rotate third-party API keys and tokens you stored as secrets on the platform, and review which datasets you uploaded. The update also widens the October wave of AI-platform incidents: exposure of billing records and partial model weights goes a step beyond the API-key theft that was disclosed first.

Get AI News by email

Verified AI stories, each with its official source, on Monday and Thursday mornings. Add breaking news to hear about the biggest ones as soon as we publish them.

Every story links its official source

Free, in English or Spanish

Unsubscribe with one click, any time

What to send

Sources for this story

  1. Official
  2. Official

Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.

  • #security
  • #data-breach
  • #llmjacking
  • #api-keys
  • #inference-platform
  • #incident-response

Want this working in your business?

We turn new AI capabilities into agents, voice receptionists, and automations you can actually use.