Overview
Fireworks AI disclosed on Monday (2026-11-09) that its investigation into an incident first reported in early October uncovered further malicious activity. The expanded scope covers account and billing information, secrets, datasets and incomplete models for a "limited set of accounts." The Hacker News reported the update on 2026-11-10.
Timeline
| Date | Event |
|---|---|
| 2026-10-06 | Fireworks detects unauthorized use of internal credentials. The attacker captured environment variables, including API keys and secrets, in evaluation jobs for a limited number of customer accounts. |
| 2026-10-10 | Initial security bulletin published. |
| 2026-10-23 | Attacker reaches Fireworks' R&D development environment via an unnamed third-party cloud provider. |
| 2026-10-24 | Attacker runs an unauthorized workload on those development machines, exposing additional customer data. |
| 2026-10-25 | Fireworks reports no further evidence of access to the customer-facing platform. |
| 2026-11-09 | Expanded scope disclosed. |
What Was Exposed
- Resource metadata: identifiers, display names, descriptions and creation times
- Billing data: addresses, invoice and payment history, balances and credit usage (full card numbers are not stored and were not affected)
- Incomplete model weights and datasets for certain customers
- Secrets: API keys and tokens from environment variables in affected accounts
- Notion AI chat transcripts used for Notion's Insights feature, mostly not attributable to specific users or workspaces
Notion reports fewer than 1% of its workspaces were impacted. It has disabled Insights and stopped serving open-weight models through Fireworks.
Fireworks links the activity to a financially motivated group that appears to resell unauthorized LLM access to illicit gateways, consistent with LLMjacking.
Recommendations
Fireworks customers
- Rotate any API keys, tokens or secrets that may have been present in evaluation environments.
- Review accounts for unauthorized usage and billing anomalies.
Notion users in affected workspaces
- Review the impacted data within your workspace.
- Rotate passwords, API keys or other credentials ever pasted into Notion AI during the attack window.
Everyone
- Avoid placing long-lived secrets in environment variables of third-party evaluation or training jobs; use short-lived, scoped credentials.