Fireworks AI expands breach disclosure after attackers reached development machines via a cloud provider
- Severity
- High
- Sources
- 1
What happened
Fireworks AI's updated bulletin extends an earlier October 6 incident involving misuse of internal credentials and environment variables in evaluation jobs, with keys and tokens potentially exposed. The later intrusion, via a third-party cloud provider's compromised environment on October 23-24, exposed billing data, resource metadata, and partial incomplete model weights and datasets; no CVEs or affected software versions were disclosed. Customers should revoke and rotate any Fireworks keys and third-party credentials, not just delete stored secrets, and review access logs, unfamiliar users, API keys, training jobs and datasets. Note that Inference, Training SDK and Nexus reportedly show no impact.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Replace any Fireworks API keys that were revoked and rotate exposed third-party credentials with their issuing providers.
- Review access logs, unfamiliar users, API keys, training jobs and datasets for unauthorised activity.
- Watch for direct notifications from Fireworks if your account data was affected.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Who and what is in it
Companies