# SZB-c3df970f8e: Fireworks AI discloses breach of development machines after cloud provider hack

Fireworks has disclosed that attackers accessed its development machines after breaching a third-party cloud provider, according to BleepingComputer.

- Type: Breach
- Status: Confirmed
- Vendor: Fireworks AI
- Disclosed: 2026-10-10 (The Hacker News: “In a notice published on October 10, 2026, the company said it detected unauthorized use of internal Fireworks credentials that allowed an unauthorized…”, [source](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html))
- Data taken: Home addresses, Tokens and keys
- Way in: Stolen credentials, Third-party vendor (The Hacker News: “In a notice published on October 10, 2026, the company said it detected unauthorized use of internal Fireworks credentials that allowed an unauthorized third-p…”, [source](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html))
- Campaign: LLMjacking (The Hacker News: “The activity is assessed to be part of an emerging threat known as LLMjacking , which refers to the act of hijacking a victim's LLM through stolen credentials…”, [source](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html))
- Sources: 16 distinct
- First seen by cve.now: 2026-11-09 21:12 UTC · Updated: 2026-11-10 22:25 UTC

Written by a model from the sources below. Verify against them.

## Summary

The reporting does not say what data, if any, was taken.

## What to do

- Rotate API keys and tokens you gave it, and review the OAuth apps and integrations connected to it · For tokens and keys (certain affected accounts)
- Expect phishing that uses this breach; verify messages that mention it · For home addresses
- Rotate API keys and secrets that were used with Fireworks
- Review account and API activity logs for unexpected access
- Enable multi-factor authentication on Fireworks console accounts
- Watch for further updates from Fireworks on the scope of the breach
- Review account and billing records for unfamiliar activity or charges
- Check whether your datasets or models were stored on the platform and assess exposure

## Timeline

- 2026-10-06: Discovered. The Hacker News: “The activity was detected on October 6, 2026, at 9 a.m. PDT.” ([source](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html))
- 2026-10-10: Made public by Fireworks AI. The Hacker News: “In a notice published on October 10, 2026, the company said it detected unauthorized use of internal Fireworks credentials that allowed an unauthorized…” ([source](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html))
- 2026-11-09 21:10 UTC: Reported by BleepingComputer
- 2026-11-09 21:12 UTC: First seen by cve.now
- 2026-11-10 15:33 UTC: Confirmed by Fireworks AI. The Hacker News: “Fireworks AI disclosed on Monday that its investigation into a security incident first reported early last month uncovered further malicious activity, affectin…” ([source](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html))
- 2026-11-10 22:25 UTC: Record last updated

## What was taken

- Home addresses: [BleepingComputer](https://www.bleepingcomputer.com/news/security/fireworks-ai-discloses-new-breach-after-cloud-provider-hack/): “In the new breach, the threat actors accessed resource metadata (e.g., Fireworks resource identifiers, display names, descriptions, creation time), billing information (e.g., billing and shipping addresses, invoice and payment history, account balance, and credit usage), and incomplete model weights and datasets for some customers.”
- Tokens and keys (certain affected accounts): [The Hacker News](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html): “At that time, the AI infrastructure provider said it only found evidence that environment variables, including API keys and tokens stored as secrets, were captured in certain affected accounts, adding that there were no signs that customer models, datasets, training data, inference traffic, or personal information were accessed.”

## Evidence (16 sources)

- 2026-11-09 · Social · [Bluesky](https://bsky.app/profile/scoopfeeds.com/post/3mzvtlelgul2m): “Fireworks AI, a popular startup that helps companies run artificial intelligence models, notified customers on Monday of a security breach in which their data was accessed…” (+5 more: [Bluesky](https://bsky.app/profile/hnbot.gsuscs.xyz/post/3mzx25wecfs2u), [Bluesky](https://bsky.app/profile/hackernewsbot.bsky.social/post/3mzx5ihpvwt2e), [Bluesky](https://bsky.app/profile/betterhn20.e-work.xyz/post/3mzx5knsc6w2n), [Bluesky](https://bsky.app/profile/betterhn50.e-work.xyz/post/3mzxd5gyth72c), [Bluesky](https://bsky.app/profile/hn100.atproto.rocks/post/3mzxokyv2e22v))
- 2026-11-09 · Social · [Hacker News](https://news.ycombinator.com/item?id=50432415): “Fireworks AI Hacked”
- 2026-11-09 · Social · [Bluesky](https://bsky.app/profile/druce.ai/post/3mzw3iz2uuw25): “Fireworks AI tells customers including Notion and Cursor of an Oct. 24 data breach, its second known hack in weeks”
- 2026-11-10 · Social · [Bluesky](https://bsky.app/profile/bigearthdata.ai/post/3mzwefarxid2i): “Fireworks AI Expands Breach Disclosure to Datasets and Model Weights” (+8 more: [Bluesky](https://bsky.app/profile/thedailytechfeed.com/post/3mzwpftscy72i), [Bluesky](https://bsky.app/profile/ifynxstudio.bsky.social/post/7eot5u537qaca), [Bluesky](https://bsky.app/profile/computebulletin.bsky.social/post/3mzwqukwxcc2s), [Bluesky](https://bsky.app/profile/abijita.bsky.social/post/3mzxconjufb2x), [Bluesky](https://bsky.app/profile/undercodenews.bsky.social/post/3mzxf64djk32q), [Bluesky](https://bsky.app/profile/aisecguru.bsky.social/post/3mzxgrs3lbo2u), [Bluesky](https://bsky.app/profile/sovereignmagazine.com/post/3mzxr3c64mj2v), [Bluesky](https://bsky.app/profile/ransomnews.online/post/3mzxus3zi7w2d))
- 2026-11-10 · Social · [Bluesky](https://bsky.app/profile/infosec.skyfleet.blue/post/gt7dvvtscmi2c): “Hackers Breach Fireworks AI Through Third-Party Cloud Provider to Steal Customer Data” (+4 more: [Bluesky](https://bsky.app/profile/e-kiledjian.bsky.social/post/3mzx6yz2uxc25), [Bluesky](https://bsky.app/profile/rasnedev.bsky.social/post/3mzxdscgk2n22), [Bluesky](https://bsky.app/profile/securityrss.bsky.social/post/3mzxutz6qzj24), [Bluesky](https://bsky.app/profile/undercodenews.bsky.social/post/3mzyi52wsgc2y))
- 2026-11-10 · Social · [Hacker News](https://news.ycombinator.com/item?id=50437106): “Fireworks AI security breach impacts Notion and their customers”
- 2026-11-10 · Press · [BleepingComputer](https://www.bleepingcomputer.com/news/security/fireworks-ai-discloses-new-breach-after-cloud-provider-hack/): “AI infrastructure startup Fireworks has disclosed a new security breach in which attackers accessed its development machines after breaching a third-party cloud provider.”
- 2026-11-10 · Social · [Mastodon](https://infosec.exchange/@cyberworldops/117591108215338068): “Fireworks AI disclosed a customer data breach originating from a compromise at its cloud host.”
- 2026-11-10 · Social · [Bluesky](https://bsky.app/profile/undercodenews.bsky.social/post/3mzwzbjimpv2r): “Fireworks AI has disclosed a second security incident within weeks, revealing that attackers compromised…” (+1 more: [Bluesky](https://bsky.app/profile/undercodenews.bsky.social/post/3mzx3oulrnx2g))
- 2026-11-10 · Social · [Bluesky](https://bsky.app/profile/neroqc.bsky.social/post/3mzxca5h6r62f): “Fireworks AI Hit by LLMJacking Cyberattack Exposing Customer Data and AI Model Weights”
- 2026-11-10 · Social · [Mastodon](https://thecybersecguru.com/news/fireworks-ai-breach-model-weights-stolen/): “Fireworks AI confirmed attackers stole up to 7.69% of customer model weights via IAM role chaining.”
- 2026-11-10 · Social · [Mastodon](https://mastox.eu/@thecybersecguru/117592145683223212): “Attackers compromised a third-party cloud provider, pivoted into Fireworks' R&D environment, escalated cloud privileges, and accessed customer datasets, secrets, billing information and incomplete model weights.”
- 2026-11-10 · Press · [The Hacker News](https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html): “Fireworks AI disclosed on Monday that its investigation into a security incident first reported early last month uncovered further malicious activity, affecting account and billing information, alongside secrets, datasets, and incomplete models for a "limited set of accounts."”
- 2026-11-10 · Social · [Mastodon](https://infosec.exchange/@adrianhollister/117592982875226741): “Notion is telling customers their AI chat transcripts surfaced in the Fireworks AI breach: fewer than 1% of workspaces, in most cases unattributable, no tool-call results.”
- 2026-11-10 · Social · [Mastodon](https://mastodon.social/@hacksgr/117593293721839527): “On Oct. 23, attackers reached development machines through an unnamed third-party cloud provider; an unauthorized workload ran the next day, leading to additional customer data impact.”
- 2026-11-10 · Social · [Bluesky](https://bsky.app/profile/hendryadrian.bsky.social/post/3mzxy3svecg22): “Fireworks AI says attackers accessed its development environment and affected a limited set of customer accounts, exposing account and billing information, secrets, datasets and incomplete models.”

## Corrections

- 2026-11-10: Changed “Tokens and keys of some customers were exposed” to “Tokens and keys of a limited number of accounts were exposed”.
- 2026-11-10: Changed “Home addresses were exposed” to “Home addresses of some customers were exposed”.
- 2026-11-10: Changed “Tokens and keys of a limited number of accounts were exposed” to “Tokens and keys were exposed”.
- 2026-11-10: Changed “Tokens and keys were exposed” to “Tokens and keys of some customers were exposed”.
- 2026-11-10: Changed “Tokens and keys of some customers were exposed” to “Tokens and keys of certain affected accounts were exposed”.
- 2026-11-10: Changed “Tokens and keys of certain affected accounts were exposed” to “Tokens and keys of a limited number of accounts were exposed”.
- 2026-11-10: Changed “Home addresses of some customers were exposed” to “Home addresses were exposed”.
- 2026-11-10: Changed “Tokens and keys of a limited number of accounts were exposed” to “Tokens and keys of certain affected accounts were exposed”.

Something wrong on this page? Report an error: https://github.com/sazabi/cve.now/issues/new?title=Wrong%20fact%20on%20SZB-c3df970f8e&body=https%3A%2F%2Fcve.now%2FSZB-c3df970f8e%0A%0AWhat%20is%20wrong%2C%20and%20the%20source%20that%20shows%20it%3A%0A

## Questions about the Fireworks AI breach

### Was Fireworks AI breached?

Yes. Fireworks AI says so: “Fireworks AI disclosed on Monday that its investigation into a security incident first reported early last month uncovered further malicious activity, affecting account and billing information, alongside secrets, datasets, and incomplete models for a "limited set of accounts."” (The Hacker News).

Source: https://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.html

### What data was exposed?

Home addresses, Tokens and keys (certain affected accounts).

### What should Fireworks AI customers do?

Rotate API keys and tokens you gave it, and review the OAuth apps and integrations connected to it. Expect phishing that uses this breach; verify messages that mention it. Rotate API keys and secrets that were used with Fireworks. Review account and API activity logs for unexpected access. Enable multi-factor authentication on Fireworks console accounts. Watch for further updates from Fireworks on the scope of the breach. Review account and billing records for unfamiliar activity or charges. Check whether your datasets or models were stored on the platform and assess exposure.

## Related

- Started as early warning SZB-c3df970f8e, first seen 2026-11-09 21:12 UTC
- Browse: [Breaches](https://cve.now/breaches.md) · [Early warnings](https://cve.now/early-warnings.md)

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/SZB-c3df970f8e
Site guide for agents: https://cve.now/llms.txt