Fireworks AI gets burned twice as customer data exposure widens

Attackers gained entry to Fireworks AI's environment by first compromising a third-party cloud provider hosting the company's R&D machines, illustrating how a supplier's security posture directly determines your own attack surface. Once inside the development environment, the threat actors ran unauthorized workloads—a hallmark of LLMJacking, where criminals monetize stolen access to AI inference capacity. The fact that this happened twice in October suggests the initial incident response failed to fully evict the attackers or close the underlying access paths. Billing records, datasets, and partial model weights were exposed, meaning the blast radius extended well beyond the compromised compute resources. Organizations must treat third-party cloud providers as an extension of their own trust boundary and apply rigorous access controls and monitoring accordingly.