[INDIA] RBI, SEBI and IRDAI · Source-code escrow and continuity obligations for critical applications[EU DORA] ICT third-party risk testing required · In force Jan 2025[PRA] SS2/21 UK · Vendor recovery evidence required[MAS] Singapore TRM · Independent vendor recoverability expected[APRA] CPS 230 Australia · Third-party continuity obligations in force[FFIEC] United States · Source-code access and software escrow addressed in third-party contracts[ENTERPRISE] Mission-critical software procurement increasingly requires continuity evidence before contract
[INDIA] RBI, SEBI and IRDAI · Source-code escrow and continuity obligations for critical applications[EU DORA] ICT third-party risk testing required · In force Jan 2025[PRA] SS2/21 UK · Vendor recovery evidence required[MAS] Singapore TRM · Independent vendor recoverability expected[APRA] CPS 230 Australia · Third-party continuity obligations in force[FFIEC] United States · Source-code access and software escrow addressed in third-party contracts[ENTERPRISE] Mission-critical software procurement increasingly requires continuity evidence before contract

CYBER WATCH / Data breaches

Fireworks AI says attackers stole billing data and some secrets

AI infrastructure company Fireworks AI says attackers stole account and billing information from an October 2026 breach, and secrets, datasets and some incomplete model weights for a limited set of accounts. A second intrusion through a third-party cloud provider followed on October 24. Fireworks says card numbers were not stored or affected. It has engaged Palo Alto Networks Unit 42 and revoked credentials.

All updates
Reported Officially confirmedPublished 13 November 2026

Incident timing: First breach discovered in October 2026 (The Record gives October 6). Second incident on October 23 to 24, 2026.

What Fireworks confirmed

An October 2026 intrusion gave an attacker access to an internal Fireworks application. Fireworks' November 9 update says the system exposed resource metadata, billing details, invoice and payment history, account balances and credit usage. Payment card numbers are not stored by Fireworks and were not affected, the company said. For a limited set of accounts, secrets, datasets and some incomplete model weights were also accessed.

A second incident

A third-party cloud provider that hosted Fireworks research machines was breached on October 23. Fireworks says the intruder used that provider on October 24 to reach development machines and run an unauthorized workload that exposed more customer data. As of October 25, the company said it had found no further successful access to the platform customers use.

Who may be responsible

Fireworks says the evidence links the activity to a financially motivated group that sells access to large language models obtained through "LLMJacking." The company has not named the group. It has notified law enforcement and is working with Palo Alto Networks Unit 42.

Response

Fireworks says it replaced credentials and service accounts, isolated affected systems and tightened access to data storage. It disabled self-serve dataset uploads and downloads for batch inference and dataset-based training while the investigation continues. Based on current findings, the company says its Inference, Training SDK and Nexus products were not affected.

Notion's customers

Notion said some of its customers were affected and that it disconnected its systems from Fireworks. Notion said Fireworks told it on November 6 that customer data may have been accessed.

Source & attribution

Read the original reporting at Fireworks AI

AI-assisted summary prepared for Castler editorial review. Evidence labels describe the source of a claim, not a guarantee that every detail of an investigation is settled.

Editorial policy & corrections