Fireworks AI breach hits Uber (149,346 drivers), Notion and Cursor; billing data and partial model weights exposed
Matéria consolidada. Reúne 24 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 7 fontes trouxeram em 17/11/2026 12:05; os links antigos trazem para cá.
Fontes: bleepingcomputer.com ×3 ↗ techcrunch.com ×4 ↗ securityweek.com ×2 ↗ gbhackers.com ×3 ↗ olhardigital.com.br ↗ thehackernews.com ↗ theregister.com ↗
Fireworks AI, an AI infrastructure provider, disclosed on 2026-11-10 a second security incident involving unauthorized access to its development machines through a third-party cloud provider (bleepingcomputer.com, theregister.com). Attackers accessed environment variables containing API keys, resource metadata, billing information and incomplete model weights for some customers (bleepingcomputer.com, thehackernews.com). The activity is linked to financially motivated criminals engaged in LLMjacking, the theft of access to large language models for illegal resale, using stolen cloud credentials (gbhackers.com, thehackernews.com). TechCrunch (techcrunch.com, 2026-11-12) also says the attackers appear financially motivated, aiming to sell tokens and exploit LLM access, and describes this as Fireworks' second breach in two months. The Register ties the incident to an attack on October 23, while securityweek.com dates the second attack to October 24 and describes two attacks in October 2026: the first through compromised internal credentials, the second through the third-party cloud provider hosting Fireworks' research and development machines. Fireworks revoked or rotated credentials, isolated affected systems and engaged incident response teams, including Palo Alto Networks Unit 42 (bleepingcomputer.com, gbhackers.com). Per securityweek.com, Fireworks contained the breach the same day and notified Notion on November 2. On 2026-11-11 Notion confirmed that Notion AI chat transcripts were exposed through the Fireworks breach. It said fewer than 1% of workspaces were affected, that customers were notified on November 9, 2026, and that its own systems remained secure (gbhackers.com, bleepingcomputer.com). techcrunch.com reports the same confirmation, with about 1% of Notion customers affected. The Register had earlier described this exposure only as possible. A later techcrunch.com report (2026-11-13) adds a second downstream victim: Uber confirmed that personal and driver's license information of thousands of Uber drivers was stolen through the Fireworks AI breach. On 2026-11-13 and 2026-11-14, olhardigital.com.br and gbhackers.com added detail: Uber was alerted on October 9 and confirmed unauthorized data access on October 13, about 1,873 Rhode Island residents were notified (olhardigital.com.br), and at least 7,870 drivers across three states had been notified (gbhackers.com). securityweek.com (2026-11-16) puts the scale far higher: Uber is notifying roughly 150,000 drivers (149,346 per a reported filing with the Texas Attorney General). Per securityweek.com, an Uber spokesperson confirmed to TechCrunch that the provider was Fireworks AI, and the attackers used compromised provider credentials on October 7 to reach data Uber had shared with the provider. The latest techcrunch.com report (2026-11-16) states the figure directly: Uber is notifying 149,346 drivers, Uber said Fireworks told it on October 9 that hackers had stolen internal credentials and used them to reach Uber's data, and Cursor also confirmed data theft in the same incident. bleepingcomputer.com (2026-11-17) confirms the 149,346 figure, citing a filing with the Maine Attorney General, and says notification letters went out on November 10. It also reports that Cursor and Notion were affected by the same Fireworks breach. No group has claimed responsibility. Uber's investigation is ongoing.
Detalhes técnicos
- Initial access: stolen cloud credentials were used to reach environment variables, and the attackers later compromised development machines (thehackernews.com). securityweek.com describes two attacks: the first through compromised internal credentials, the second through the third-party cloud provider hosting Fireworks' R&D machines. techcrunch.com says the attackers breached Fireworks' cloud provider and accessed customer data from a Fireworks development system. In its 2026-11-13 report on Uber, techcrunch.com says the theft of internal credentials at Fireworks AI was then used to access Uber's data, and its 2026-11-16 report repeats that the attackers used Fireworks' own internal credentials. gbhackers.com (2026-11-14) describes a credential compromise at Fireworks AI that gave unauthorized access to Uber's account with Fireworks AI, and says Uber's internal systems were not directly affected. securityweek.com (2026-11-16) says the attackers used compromised provider credentials on October 7 to reach the data Uber had shared with the provider. bleepingcomputer.com (2026-11-17) says the provider told Uber that an unauthorized party used compromised internal credentials to access Uber's account with it, and that Fireworks was reportedly hacked after a third-party cloud provider breach.
- Affected environments: development machines and evaluation environments (gbhackers.com). Notion describes the entry point as Fireworks' development environment, reached via a third-party cloud provider (bleepingcomputer.com). Uber's data sat in an environment created and managed by Uber's Cloud Security team (securityweek.com, 2026-11-16).
- Attacker activity: the second attack, on October 24, resulted in unauthorized workloads that exposed Notion AI chat transcripts tied to the Insights feature (securityweek.com).
- Detection gap: alerts for unauthorized access were enabled in Uber's environment, but none fired because the attacker used valid credentials (securityweek.com, 2026-11-16; techcrunch.com, 2026-11-16: "no alerts were triggered").
- Exposed data: API keys in environment variables, resource identifiers and metadata, billing data, customer datasets and incomplete model weights (bleepingcomputer.com, gbhackers.com, theregister.com). techcrunch.com also lists billing information and datasets, including Notion AI chat transcripts from the Insights feature, and in its 2026-11-16 report mentions billing data and some private AI datasets. Fireworks first said it had found no evidence that customer personal information, models or datasets were accessed; in a November 9 update it acknowledged that account and billing information, some customer datasets and incomplete models were also affected (securityweek.com, 2026-11-16).
- Notion impact: the datasets included Notion AI chat transcripts used in the Insights feature, from a small subset of workspaces (under 1%). The exposed data was mostly unattributable, lacking user or workspace identifiers (bleepingcomputer.com, securityweek.com). No other Notion features were impacted (gbhackers.com).
- Cursor impact: techcrunch.com (2026-11-16) says Cursor also confirmed data theft in the same incident; the source gives no detail on what was taken. bleepingcomputer.com (2026-11-17) reports that Cursor users' devices were reportedly infected with backdoor malware; this is a single-source, unconfirmed claim that no other source corroborates.
- Uber impact: personal and driver's license information of Uber drivers was stolen. securityweek.com (2026-11-16) puts the number at roughly 150,000 drivers (149,346 per a reported Texas Attorney General filing) and lists the exposed data as images of driver's licenses, names, addresses, dates of birth, driver's license numbers and government-issued ID numbers. techcrunch.com (2026-11-16) gives the same 149,346 figure as the number of drivers Uber is notifying, listing names, addresses, dates of birth and driver's license numbers. bleepingcomputer.com (2026-11-17) gives 149,346 drivers per a Maine Attorney General filing, with names, driver's license numbers, dates of birth and addresses exposed, and says notification letters went out on November 10 and that Uber did not name the provider itself. Uber says the provider's credentials gave no access to other Uber systems (securityweek.com). Driver license numbers had earlier been reported in Massachusetts, South Carolina, Rhode Island, Illinois and California (techcrunch.com); securityweek.com says notifications were filed in California, Iowa, Massachusetts, South Carolina, Texas and Vermont; techcrunch.com (2026-11-16) lists notices filed in California, Iowa, Oregon, Illinois, Massachusetts, Rhode Island, South Carolina, Texas and Vermont. olhardigital.com.br reports that about 1,873 Rhode Island residents were affected, with notifications also extending to residents of DC, Maryland, North Carolina, New York and Pennsylvania. According to olhardigital.com.br, the vendor first reported its breach to Uber on October 9, Uber suspended data connections and launched an investigation, and unauthorized data access was confirmed on October 13. gbhackers.com says at least 7,870 drivers across three states had been notified and that the stolen license data creates a risk of identity fraud and follow-on scams. olhardigital.com.br says no fraudulent use of the data has been detected so far. techcrunch.com notes this is Uber's second known data breach in 2026, after an earlier incident at its Uber Freight unit involving extortion and data theft. olhardigital.com.br does not name the vendor; gbhackers.com, techcrunch.com and securityweek.com name Fireworks AI, and bleepingcomputer.com (2026-11-17) names it via TechCrunch. A techcrunch.com mobility newsletter (2026-11-15) had reported the notifications without naming the provider, the attacker or the count.
- Attribution: unnamed LLMjacking criminals or a cybercriminal group selling stolen LLM access (gbhackers.com, thehackernews.com, theregister.com, techcrunch.com). techcrunch.com says Fireworks AI attributes the breach to a financially motivated group aiming to sell stolen tokens for LLM access, and that no group has claimed responsibility (2026-11-16). bleepingcomputer.com (2026-11-17) repeats that Fireworks says the group is financially motivated and linked to LLMjacking. No named threat actor is given in the sources.
- The specific third-party cloud provider is not named in the sources.
Remediação
- Fireworks revoked or rotated compromised credentials and keys, isolated affected systems and carried out security hardening (bleepingcomputer.com, thehackernews.com). It contained the breach the same day, per securityweek.com.
- Notion cut off Fireworks' access, had data deleted from vendor systems, halted training runs and disabled the Insights feature (bleepingcomputer.com). techcrunch.com likewise says Notion disconnected from Fireworks, deleted stored data and stopped connectivity. Its investigation is ongoing (gbhackers.com).
- Uber suspended its data connections to the vendor after the October 9 alert and investigated (olhardigital.com.br, securityweek.com, bleepingcomputer.com). It is offering affected individuals 90 days of free credit monitoring and fraud assistance through Cyberscout (olhardigital.com.br, gbhackers.com, which mentions free credit monitoring and fraud assistance; securityweek.com also confirms free credit monitoring and fraud assistance). The 2026-11-16 techcrunch.com report gives no remediation guidance beyond the driver notifications. bleepingcomputer.com (2026-11-17) advises affected drivers to watch for identity theft and fraud, since driver's license numbers and dates of birth were exposed.
- Users of affected Notion workspaces should review their data and rotate any credentials or sensitive information that were entered in AI chats (bleepingcomputer.com, securityweek.com).
- Customers should rotate any API keys and secrets stored in environment variables or shared with Fireworks, and review billing and usage records for anomalous LLM consumption, a typical LLMjacking indicator. This is a general recommendation, not one stated by the sources.
- Organizations sharing data with third-party providers should note that alerts did not fire in Uber's case because valid credentials were used, so monitoring of provider-credential behavior (unusual access to shared data) matters. This is a general recommendation, not one stated by the sources.
- Uber drivers who receive a notification should enroll in the offered monitoring and watch for misuse of their personal and license data, including identity fraud and follow-on scams. Enrolling is a general recommendation, not one stated by the sources, although watching for identity theft and fraud is also advised by bleepingcomputer.com.
- Cursor users should watch for vendor communications about the confirmed data theft; the sources give no details on its scope or on any guidance (general note). Given the unconfirmed report of backdoor malware on Cursor users' devices (bleepingcomputer.com), users may also wish to check their devices for suspicious software; this is a general note, not guidance from the sources.
Relatos divergentes
- Scope: gbhackers.com's earlier coverage called the breach "widespread" and said it affected customer information and datasets. thehackernews.com says only a limited set of accounts was impacted, and theregister.com says "some customers". The later Notion-derived reports (gbhackers.com, bleepingcomputer.com, securityweek.com) put the Notion impact at under 1% of workspaces, while techcrunch.com says about 1% of Notion customers. The Uber reports show the impact extends beyond Notion to driver data on a large scale (about 150,000 drivers per securityweek.com; 149,346 per techcrunch.com and bleepingcomputer.com), and techcrunch.com (2026-11-16) adds Cursor as another confirmed victim, so the earlier "limited" wording understates the overall scope. No overall figure for affected Fireworks customers is given. Fireworks' initial statement that no customer personal information, models or datasets were accessed was revised in its November 9 update (securityweek.com).
- Uber victim counts and states: techcrunch.com and securityweek.com (both 2026-11-16) cite roughly 150,000 drivers, specifically 149,346, and bleepingcomputer.com (2026-11-17, the most recent) confirms 149,346. The regulator filing behind the figure is given differently: securityweek.com attributes it to a reported Texas Attorney General filing, while bleepingcomputer.com attributes it to a filing with the Maine Attorney General; the sources do not reconcile this, and both may exist as separate state filings with the same total. techcrunch.com says Uber is notifying that number. The state lists differ: securityweek.com names California, Iowa, Massachusetts, South Carolina, Texas and Vermont, while techcrunch.com (2026-11-16) names California, Iowa, Oregon, Illinois, Massachusetts, Rhode Island, South Carolina, Texas and Vermont, a superset. Earlier figures were partial: olhardigital.com.br (2026-11-13) cited about 1,873 Rhode Island residents, with notifications in DC, Maryland, North Carolina, New York and Pennsylvania; gbhackers.com (2026-11-14) cited at least 7,870 drivers across three states; an earlier techcrunch.com report listed license numbers reported in Massachusetts, South Carolina, Rhode Island, Illinois and California. The earlier figures appear to be state-level or partial counts and are superseded as totals by the 149,346 figure, though the sources do not reconcile the state lists.
- Dates: theregister.com dates the attack to October 23, while securityweek.com dates the second attack to October 24 and says there was an earlier first attack in October 2026 (no date given). bleepingcomputer.com (2026-11-17) also gives October 24 for the Fireworks incident and notes that this is later than Uber's October 9 notification, without explaining the discrepancy. The other sources give no attack date. Notion's customer notification date of November 9, 2026 comes from gbhackers.com, and the date Fireworks notified Notion (November 2) comes from securityweek.com. techcrunch.com (2026-11-13) says Uber confirmed the driver data theft in October 2026; olhardigital.com.br, gbhackers.com and bleepingcomputer.com give the October 9 alert and October 13 confirmation, techcrunch.com (2026-11-16) also gives the October 9 notification from the provider, and securityweek.com (2026-11-16) adds that the credentials were used on October 7. bleepingcomputer.com adds that Uber's notification letters went out on November 10. These Uber dates fall before the October 23 and 24 attacks dated by theregister.com, securityweek.com and bleepingcomputer.com, so the Uber data theft is likely linked to the earlier first attack or a separate access path. No source states this explicitly.
- Initial access: most sources describe access through the third-party cloud provider hosting Fireworks' development machines, while techcrunch.com's Uber reports (2026-11-13 and 2026-11-16) describe theft of internal Fireworks credentials, gbhackers.com (2026-11-14) describes a credential compromise giving access to Uber's account with Fireworks, securityweek.com (2026-11-16) describes compromised provider credentials used on October 7, and bleepingcomputer.com (2026-11-17) describes compromised internal credentials at the provider. securityweek.com's description of two attacks (internal credentials, then the cloud provider) is consistent with all of these versions, but no source explicitly ties the Uber data to one of the two attacks.
- Vendor identification for Uber: olhardigital.com.br describes only a compromised third-party vendor and does not name Fireworks AI, and a techcrunch.com newsletter (2026-11-15) likewise did not name the provider, while techcrunch.com (2026-11-16), gbhackers.com and securityweek.com (citing an Uber spokesperson's confirmation to TechCrunch) explicitly attribute the Uber driver data theft to the Fireworks AI breach. bleepingcomputer.com (2026-11-17) says Uber itself did not name the provider and relies on TechCrunch for the identification.
- Cursor impact: techcrunch.com (2026-11-16) says only that Cursor confirmed data theft, with no detail, while bleepingcomputer.com (2026-11-17) alone reports that Cursor users' devices were reportedly infected with backdoor malware. The claim is hedged ("reportedly"), comes from a single source and is not corroborated by Cursor or other sources, so it should be treated as unconfirmed.
Linha do tempo
-
Uber notifies 149,346 drivers of data breach via compromised service provider account linked to Fireworks AI breach
ler a análise desta fonte ocultar
Uber is notifying drivers that attackers stole their data after compromising credentials at a third-party service provider. A filing with the Maine Attorney General puts the number affected at 149,346 drivers. Exposed data includes names, driver's license numbers, dates of birth and addresses. Uber says the provider notified it on October 9, 2026 that an unauthorized party had used compromised internal credentials to access Uber's account. Uber cut the data connections, and its investigation confirmed on October 13 that Uber data had been accessed. Notification letters went out on November 10. Uber did not name the provider. TechCrunch, as cited by BleepingComputer, identified it as AI provider Fireworks, which Fireworks says was hit by a financially motivated group linked to LLMjacking. The same Fireworks breach also affected Cursor and Notion. This summary rests on the article alone, and no additional research was performed. The article gives an October 24 date for the Fireworks incident, which is later than Uber's October 9 notification. The article does not explain the discrepancy.
Technical Details
- Initial access was through compromised internal credentials at a service provider, which were used to reach Uber's account with that provider.
- Fireworks reportedly was hacked after a third-party cloud provider breach.
- Cursor users' devices were reportedly infected with backdoor malware.
Remediation
Uber severed its data connections with the provider and investigated. Affected drivers should watch for identity theft and fraud, since driver's license numbers and dates of birth were exposed.
-
Fireworks AI breach exposes data of 149,346 Uber drivers, including driver's license numbers
ler a análise desta fonte ocultar
Uber is notifying 149,346 drivers that their personal data, including driver's license numbers, was stolen in an October breach at its third-party vendor Fireworks AI. Uber said the provider notified it on October 9 that hackers had stolen internal credentials and used them to reach Uber's data. TechCrunch identified the provider as Fireworks, which lets developers use open AI models. Fireworks attributed the breach to a financially motivated cybercriminal group that wants to sell stolen LLM access tokens. No group has claimed responsibility. Notion and Cursor also confirmed data theft in the same incident. This analysis rests on the article alone; no web research was performed.
Technical Details
- The attackers used Fireworks' own internal credentials. Uber had alerts enabled for unauthorized access to its Fireworks environment, but "no alerts were triggered".
- The stolen Uber data includes names, addresses, dates of birth and driver's license numbers.
- Fireworks' stolen customer data also included billing data and some private AI datasets.
Remediation
The article gives no remediation guidance. Affected drivers are being notified, and notices were filed in California, Iowa, Oregon, Illinois, Massachusetts, Rhode Island, South Carolina, Texas and Vermont.
-
Uber driver data of about 150,000 people stolen via compromised credentials at third-party provider Fireworks AI
ler a análise desta fonte ocultar
Uber is notifying roughly 150,000 drivers (149,346 per a reported filing with the Texas Attorney General) that their personal data was stolen. The breach involved a third-party service provider, which an Uber spokesperson confirmed to TechCrunch was Fireworks AI. Uber learned of the incident on October 9. By October 13 it had determined that the attackers used compromised provider credentials on October 7 to reach data Uber had shared with the provider. Exposed data includes images of driver's licenses, names, addresses, dates of birth, driver's license numbers and government-issued ID numbers. This summary draws only on the article. No web research was done, so the vendor advisory and any CVE or IOC details were not checked.
Technical Details
- The data sat in an environment created and managed by Uber's Cloud Security team.
- Alerts were enabled, but none fired because the attacker used valid credentials.
- Uber says the provider's credentials gave no access to other Uber systems. The investigation is ongoing.
- Fireworks first said it had found no evidence that customer personal information, models or datasets were accessed. In a November 9 update it acknowledged that account and billing information, some customer datasets and incomplete models were also affected.
- Notion customer data was reportedly compromised in the same Fireworks AI hack, according to a related SecurityWeek headline.
Remediation
- Uber cut its data connections with the provider.
- It is offering affected individuals free credit monitoring and fraud assistance.
- Notifications were filed in California, Iowa, Massachusetts, South Carolina, Texas and Vermont.
-
TechCrunch Mobility roundup: Uber notifies drivers of October third-party vendor breach exposing license data
ler a análise desta fonte ocultar
This is a TechCrunch mobility newsletter, not a security report. Its main security item is that Uber is thousands of drivers that their personal and driver's license information was stolen in an October data breach at one of its tech providers. The article does not name the provider, the attacker, the number of people affected, or the attack method. No web research was done, so there is no vendor statement or other corroboration. The rest of the newsletter covers business and policy news: Nvidia leadership and China export-control speculation, robotaxi funding, a NHTSA probe of Waymo, and Lucid earnings. None of that is a direct cyber threat.
-
Uber Drivers' License Data Stolen via Fireworks AI Vendor Breach Affecting Thousands
ler a análise desta fonte ocultar
In October 2026, a third-party vendor, Fireworks AI, suffered a credential compromise that exposed personal and driver's license data of thousands of Uber drivers in the United States. The breach did not directly affect Uber's internal systems but occurred through unauthorized access to Uber's account with Fireworks AI. Uber began investigating after being alerted on October 9 and confirmed data access by October 13. Notifications have been sent to at least 7,870 drivers across three states, with expectations of more affected individuals as additional state disclosures emerge. The stolen data involves sensitive driver's license details, posing a risk for identity fraud and follow-on scams. Uber is providing affected drivers with free credit monitoring and fraud assistance.
-
Uber confirms unauthorized data access via compromised third-party vendor credentials
ler a análise desta fonte ocultar
Uber disclosed a security incident where an unauthorized individual used compromised credentials of a third-party vendor to access company data. The breach was first reported by the vendor on October 9, leading Uber to suspend data connections and launch an investigation that confirmed unauthorized data access on October 13. The compromised information included personal data such as driver’s license details of approximately 1,873 residents of Rhode Island, with notifications extending to residents of DC, Maryland, North Carolina, New York, and Pennsylvania. Uber is providing affected individuals with 90 days of free credit monitoring and fraud assistance through Cyberscout. No fraudulent use of the data has been detected so far.
-
Hackers breach Fireworks AI, stealing thousands of Uber drivers' license data via third-party compromise
ler a análise desta fonte ocultar
In October 2026, Uber confirmed that hackers stole personal and driver's license information of thousands of Uber drivers through a data breach at Fireworks AI, a third-party provider that offers access to open AI models. The breach involved the theft of internal credentials at Fireworks AI, which were then used to access Uber's data. Affected driver licenses numbers have been reported in Massachusetts, South Carolina, Rhode Island, Illinois, and California, with the total number of victims expected to increase as further notifications occur. Fireworks AI attributes the breach to a financially motivated cybercriminal group aiming to sell stolen tokens for accessing large language models. Uber has not disclosed the total count of affected drivers or customers. This incident is the second known data breach for Uber in 2026, following an incident at its Uber Freight unit involving extortion and data theft.
-
Cyberattack on Fireworks AI exposed Notion customers' chat transcripts and billing data
ler a análise desta fonte ocultar
Fireworks AI, a platform used to access open AI models, suffered a cyberattack where attackers breached its cloud provider and accessed customer data from a Fireworks development system. The breach exposed some customers' billing information and datasets, including chat transcripts of Notion AI customers who used the Insights feature. Notion confirmed about 1% of its customers were affected and has since disconnected from Fireworks, deleted stored data, and stopped connectivity. The attackers appear financially motivated, aiming to sell tokens and exploit large language model access. This marks Fireworks' second breach in two months, highlighting risks in tech supply chain dependencies.
-
Notion Customer Data Accessed in Fireworks AI Data Breach Following LLMJacking Attack
ler a análise desta fonte ocultar
Notion has disclosed a data breach affecting a small subset of its customers due to a compromise at Fireworks AI, a cloud platform used for running open-source AI models. The breach involved two attacks in October 2026: initially through compromised internal credentials and later via a third-party cloud provider hosting Fireworks AI’s research and development machines. The second attack on October 24 resulted in unauthorized workloads that exposed Notion AI chat transcripts tied to the Insights feature. Less than 1% of Notion’s workspaces were affected, and most transcripts could not be linked back to specific customers or workspaces. Notion recommends impacted users rotate any credentials or sensitive information potentially exposed during the incident. Fireworks AI contained the breach on the same day and notified Notion on November 2.
-
Notion AI chat transcripts exposed in Fireworks AI breach affecting under 1% of users
ler a análise desta fonte ocultar
Notion disclosed that a security breach at its AI infrastructure provider, Fireworks AI, led to the exposure of AI chat transcripts from a small subset of Notion workspaces. The breach involved unauthorized access to Fireworks' development environment via a third-party cloud provider, compromising resource metadata, billing information, and datasets including Notion AI chat transcripts used in the Insights feature. Notion responded promptly by cutting off Fireworks' access, deleting data from vendor systems, and halting training runs. The exposed data was mostly unattributable, lacking user or workspace identifiers. Less than 1% of Notion users were impacted, and the Insights feature has been disabled. Users of affected workspaces are advised to review their data and rotate credentials if entered in chats.
-
Notion AI Data Breach Exposes Customer Chat Transcripts After Third-Party Cyberattack
ler a análise desta fonte ocultar
Notion has announced that a cyberattack targeting its AI infrastructure provider, Fireworks AI, led to the exposure of customer chat transcripts. The breach affected fewer than 1% of Notion workspaces, with no other features impacted. Customers were notified on November 9, 2026, and investigations are ongoing. The company confirmed that its own systems remained secure.
-
Fireworks AI incident exposes customer data via cloud provider breach and LLMjacking threat
ler a análise desta fonte ocultar
Fireworks AI disclosed a security incident involving unauthorized access to its development environment through a third-party cloud provider, resulting in exposure of billing data, resource metadata, and incomplete model weights for some customers. The attackers used stolen credentials to access environment variables and later compromised development machines, impacting a limited set of accounts. The breach is linked to a cybercriminal group involved in LLMjacking, selling stolen access to large language models. Fireworks responded by credential rotation, system isolation, and security hardening. This incident highlights ongoing risks of AI infrastructure attacks and cybercriminal exploitation of LLM vulnerabilities.
-
Fireworks AI suffers second breach with wider customer data exposure in October
ler a análise desta fonte ocultar
AI infrastructure provider Fireworks disclosed a second cybersecurity incident involving unauthorized access via a third-party cloud provider. The breach impacted billing records, resource metadata, and incomplete model weights for some customers, following an attack on October 23. The incident was linked to LLMJacking criminals, targeting AI models and customer datasets. Fireworks responded by credential rotation, system isolation, and collaborating with security teams to remediate the vulnerabilities. Notion AI chat transcripts may have also been exposed, though no personal or workspace-specific data was confirmed.
-
Fireworks AI suffers widespread breach via LLMJacking involving customer data and model weights
ler a análise desta fonte ocultar
Fireworks AI has disclosed a significant security breach affecting customer information, datasets, and incomplete model weights. The incident was driven by financially motivated criminals exploiting stolen cloud credentials to carry out LLMJacking—a method of stealing access to large language models for illegal resale. The breach involved unauthorized access to development machines and evaluation environments, leading to exposure of resource identifiers, billing data, and some model weights. Fireworks responded by revoking compromised keys, isolating affected systems, and collaborating with forensic experts including Palo Alto Networks Unit 42. The event underscores ongoing cloud credential theft and LLMjacking risks affecting AI services.
-
Fireworks AI reveals new breach after cloud provider hack involves customer data
ler a análise desta fonte ocultar
AI infrastructure startup Fireworks disclosed a new security breach involving unauthorized access to its development machines through a third-party cloud provider. Attackers accessed environment variables with API keys, resource metadata, billing info, and incomplete model weights. The company responded by revoking credentials, isolating systems, and working with incident response teams, including Palo Alto Networks' Unit 42, to investigate further. The incident highlights risks of LLMjacking and cloud vulnerabilities in AI services.