Fireworks AI breach widens: billing data, customer secrets and partial model weights exposed in LLMjacking-linked intrusion
Fireworks AI has widened its disclosure of an October 2026 intrusion. On November 9 it said attackers reached account and billing records and, for a limited set of accounts, secrets, datasets and incomplete model weights (fireworks.ai). The first detection was unauthorized use of internal credentials on October 6, and the earlier bulletin had reported only stolen environment variables used in evaluation jobs (gbhackers.com, fireworks.ai). A second intrusion began when a third-party cloud host running Fireworks' R&D machines was breached on October 23, and the intruder used that access to reach development machines on October 24 (fireworks.ai). The company links the activity to a financially motivated group practicing LLMJacking, which resells stolen LLM access through illicit routing gateways, but it has not named the group (fireworks.ai). The vendor reports no further attacker access to its customer platform since October 25 and no impact on Inference, Training SDK or Nexus, which are zero data retention by default (fireworks.ai). No CVE or software flaw is involved, so the risk comes from exposed credentials and data rather than a vulnerability score.
Detalhes técnicos
- The intruder used stolen internal credentials first, and the affected internal application then exposed resource identifiers, display names, descriptions and creation times (fireworks.ai, gbhackers.com).
- Billing data exposed includes billing and shipping addresses, invoices, payment history, account balances and credit usage. Payment card numbers are not stored and were not affected (fireworks.ai).
- For certain customers, a subset of incomplete model weights and datasets was accessed (fireworks.ai).
- The investigation is ongoing, and Fireworks says its findings are based on the investigation to date and may change (fireworks.ai).
- Neither the vendor nor the article gives a CVSS score, CVE or GHSA identifier, because no software vulnerability has been published for this incident.
Remediação
The vendor's bulletin describes operational hardening rather than a code fix, so no Fix Details section applies. Fireworks revoked and replaced credentials and service accounts, removed unnecessary elevated privileges, restricted unauthorized network paths, isolated affected systems, tightened access to storage and analytics, and strengthened logging (fireworks.ai). It disabled self-serve dataset uploads and downloads for Batch Inference and dataset-based training, while Training SDK remains available and Lab-based training runs in an isolated environment (fireworks.ai).
Affected customers should replace revoked keys, rotate third-party secrets with the issuing providers, update their applications, and review logs for unauthorized reads, downloads or changes (gbhackers.com). Deleting stored secrets does not invalidate the credentials, and customers should check users, evaluators, jobs, datasets and keys for unfamiliar activity (gbhackers.com). Questions go to [email protected] (fireworks.ai).
Linha do tempo
-
Fireworks AI breach widens: billing data, customer secrets and partial model weights exposed in LLMjacking-linked intrusion
ler a análise desta fonte ocultar
Fireworks AI has widened its disclosure of an October 2026 intrusion. On November 9 it said attackers reached account and billing records and, for a limited set of accounts, secrets, datasets and incomplete model weights (fireworks.ai). The first detection was unauthorized use of internal credentials on October 6, and the earlier bulletin had reported only stolen environment variables used in evaluation jobs (gbhackers.com, fireworks.ai). A second intrusion began when a third-party cloud host running Fireworks' R&D machines was breached on October 23, and the intruder used that access to reach development machines on October 24 (fireworks.ai). The company links the activity to a financially motivated group practicing LLMJacking, which resells stolen LLM access through illicit routing gateways, but it has not named the group (fireworks.ai). The vendor reports no further attacker access to its customer platform since October 25 and no impact on Inference, Training SDK or Nexus, which are zero data retention by default (fireworks.ai). No CVE or software flaw is involved, so the risk comes from exposed credentials and data rather than a vulnerability score.
Technical Details
- The intruder used stolen internal credentials first, and the affected internal application then exposed resource identifiers, display names, descriptions and creation times (fireworks.ai, gbhackers.com).
- Billing data exposed includes billing and shipping addresses, invoices, payment history, account balances and credit usage. Payment card numbers are not stored and were not affected (fireworks.ai).
- For certain customers, a subset of incomplete model weights and datasets was accessed (fireworks.ai).
- The investigation is ongoing, and Fireworks says its findings are based on the investigation to date and may change (fireworks.ai).
- Neither the vendor nor the article gives a CVSS score, CVE or GHSA identifier, because no software vulnerability has been published for this incident.
Remediation
The vendor's bulletin describes operational hardening rather than a code fix, so no Fix Details section applies. Fireworks revoked and replaced credentials and service accounts, removed unnecessary elevated privileges, restricted unauthorized network paths, isolated affected systems, tightened access to storage and analytics, and strengthened logging (fireworks.ai). It disabled self-serve dataset uploads and downloads for Batch Inference and dataset-based training, while Training SDK remains available and Lab-based training runs in an isolated environment (fireworks.ai).
Affected customers should replace revoked keys, rotate third-party secrets with the issuing providers, update their applications, and review logs for unauthorized reads, downloads or changes (gbhackers.com). Deleting stored secrets does not invalidate the credentials, and customers should check users, evaluators, jobs, datasets and keys for unfamiliar activity (gbhackers.com). Questions go to [email protected] (fireworks.ai).