Vendor incident, severity critical
Fireworks AI breached again via third-party cloud provider; customer billing data and model weights accessed
Published
Fireworks AI disclosed a new breach in which attackers used a compromised third-party cloud provider that hosted its R&D machines to reach development machines on October 24 and run an unauthorized workload. Attackers accessed resource metadata, billing information, and incomplete model weights and datasets for some customers, but not payment card numbers. This follows an earlier October incident where environment variables holding API keys and tokens were accessed for a limited number of accounts and used for LLMjacking.
What's affected
- fireworks-aievery version
Exposure window: UTC.
What to do
- Check notifications from Fireworks and its published advisory to see whether your account was affected
- Replace Fireworks API keys and any tokens stored as secrets in Fireworks environment variables
- Review account activity and usage for unauthorized calls or unexpected charges
Secrets to rotate if you were affected
AI API keys, Environment variables.
Check whether you were affected
Pharon tells teams automatically when this affects something they run. To check a machine, run this in Claude Code with the Pharon plugin, in the repository that uses it:
/pharon:check-incident fireworks-ai-breach-2026-11References
Notice fireworks-ai-breach-2026-11, signed with key feed-prod-2026-10 (Ed25519). The Pharon CLI verifies the signature before using a notice.