_Incident · Other_

# Fireworks AI security incident exposed customer billing data and some incomplete model weights

Canonical ID: `eb238d6f-29cc-4984-8981-23e0c037d932`

- **Occurred:** 2026-10-24
- **Kind:** `other`
- **Status (derived):** active
- **Company:** [Fireworks AI](/companies/fireworks-ai.md) (id: `9d840539-7fcc-4716-b4e6-f3b74cac98fa`)

[Fireworks AI](/companies/fireworks-ai.md) said an unauthorized third party used a security incident at a third-party cloud provider on October 23 to reach Fireworks development machines on October 24 and run an unauthorized workload. Account and billing information was affected, and for a limited set of accounts secrets, datasets and incomplete models. Fireworks linked the activity to a financially motivated group selling unauthorized LLM access, known as LLMjacking.

## Sources (1)

1. **Update on October 2026 security incident** · https://fireworks.ai/security/bulletins/october-2026-security-incident-update · 2026-11-09

## Common questions

### What happened in Fireworks AI security incident exposed customer billing data and some incomplete model weights?

[Fireworks AI](/companies/fireworks-ai.md) said an unauthorized third party used a security incident at a third-party cloud provider on October 23 to reach Fireworks development machines on October 24 and run an unauthorized workload. Account and billing information was affected, and for a limited set of accounts secrets, datasets and incomplete models. Fireworks linked the activity to a financially motivated group selling unauthorized LLM access, known as LLMjacking.

### When did this incident occur?

The incident is recorded as occurring on October 24, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

### Who was involved in Fireworks AI security incident exposed customer billing data and some incomplete model weights?

The incident is recorded as involving [Fireworks AI](/companies/fireworks-ai.md) on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

### Has anyone responded to Fireworks AI security incident exposed customer billing data and some incomplete model weights?

No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.

### What is the current status of Fireworks AI security incident exposed customer billing data and some incomplete model weights?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/eb238d6f-29cc-4984-8981-23e0c037d932 · sources: /v1/incidents/eb238d6f-29cc-4984-8981-23e0c037d932/sources · responses: /v1/incidents/eb238d6f-29cc-4984-8981-23e0c037d932/responses · status: /v1/incidents/eb238d6f-29cc-4984-8981-23e0c037d932/status · canonical URL: /incidents/fireworks-ai-october-2026-security-incident_