Fireworks AI discloses second breach in weeks, reached via third-party cloud provider hosting its R&D machines
Fireworks AI, an inference platform for running open-source models, disclosed on November 9, 2026 a second security incident within weeks (fireworks.ai). The October incident involved unauthorized use of internal credentials and access to environment variables holding API keys and tokens for a limited number of customer accounts (fireworks.ai). In the new breach, a third party used a security incident at a third-party cloud provider hosting Fireworks R&D machines to reach Fireworks development machines on October 24 and run an unauthorized workload (fireworks.ai). The attackers accessed resource metadata, billing information and, for some customers, secrets, datasets and incomplete model weights, but not payment card numbers, which Fireworks does not store (bleepingcomputer.com). Fireworks says it had detected no further successful unauthorized access to the platform customers use as of October 25 and is working with Palo Alto Networks' Unit 42 on the full scope (bleepingcomputer.com). Criticity is high rather than critical: no vulnerability or CVE is involved, access relied on stolen credentials and a third-party foothold, exposure is limited to some accounts, and the vendor reports no further platform access, but the loss of datasets and model weights is serious.
Detalhes técnicos
- The first incident was identified on October 6 and involved unauthorized use of internal Fireworks credentials and access to environment variables used in evaluation jobs (fireworks.ai).
- A third-party cloud provider hosting Fireworks R&D machines had a security incident on October 23; the unauthorized party used it to reach Fireworks development machines on October 24 (fireworks.ai).
- Fireworks says it detected this activity the same day and closed known critical vulnerabilities (bleepingcomputer.com).
- The vendor's bulletin does not name a threat actor or malware family. The article quotes the October notice describing a financially motivated group selling LLM tokens to illicit routing gateways ('LLMJacking') (bleepingcomputer.com).
Remediação
- Fireworks revoked and replaced credentials and service accounts, restricted unauthorized network pathways, isolated affected systems and tightened access to data storage and analytics systems (bleepingcomputer.com).
- Fireworks states that customers who received an affected-customer notice should replace revoked Fireworks API keys if they still need them, and that customers without such a notice need no incident-specific action (fireworks.ai).
- Dataset transfers were reported as still disabled while the investigation continues (unite.ai).
Linha do tempo
-
Fireworks AI discloses second breach in weeks, reached via third-party cloud provider hosting its R&D machines
ler a análise desta fonte ocultar
Fireworks AI, an inference platform for running open-source models, disclosed on November 9, 2026 a second security incident within weeks (fireworks.ai). The October incident involved unauthorized use of internal credentials and access to environment variables holding API keys and tokens for a limited number of customer accounts (fireworks.ai). In the new breach, a third party used a security incident at a third-party cloud provider hosting Fireworks R&D machines to reach Fireworks development machines on October 24 and run an unauthorized workload (fireworks.ai). The attackers accessed resource metadata, billing information and, for some customers, secrets, datasets and incomplete model weights, but not payment card numbers, which Fireworks does not store (bleepingcomputer.com). Fireworks says it had detected no further successful unauthorized access to the platform customers use as of October 25 and is working with Palo Alto Networks' Unit 42 on the full scope (bleepingcomputer.com). Criticity is high rather than critical: no vulnerability or CVE is involved, access relied on stolen credentials and a third-party foothold, exposure is limited to some accounts, and the vendor reports no further platform access, but the loss of datasets and model weights is serious.
Technical Details
- The first incident was identified on October 6 and involved unauthorized use of internal Fireworks credentials and access to environment variables used in evaluation jobs (fireworks.ai).
- A third-party cloud provider hosting Fireworks R&D machines had a security incident on October 23; the unauthorized party used it to reach Fireworks development machines on October 24 (fireworks.ai).
- Fireworks says it detected this activity the same day and closed known critical vulnerabilities (bleepingcomputer.com).
- The vendor's bulletin does not name a threat actor or malware family. The article quotes the October notice describing a financially motivated group selling LLM tokens to illicit routing gateways ('LLMJacking') (bleepingcomputer.com).
Remediation
- Fireworks revoked and replaced credentials and service accounts, restricted unauthorized network pathways, isolated affected systems and tightened access to data storage and analytics systems (bleepingcomputer.com).
- Fireworks states that customers who received an affected-customer notice should replace revoked Fireworks API keys if they still need them, and that customers without such a notice need no incident-specific action (fireworks.ai).
- Dataset transfers were reported as still disabled while the investigation continues (unite.ai).