[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgjUChvxd997glPju0rCfEYIGUj4XrarCEglpLREoMaI":3},{"article":4,"iocs":50,"watch_terms":51,"solutions":52,"lesson":146},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":32,"category":33,"article_tags":37},"e6557738-1dd0-46c6-87d6-80a69c5135fe","Fireworks AI gets burned twice as customer data exposure widens","fireworks-ai-gets-burned-twice-as-customer-data-exposure-widens-f3cf8b","Inference biz pins latest breach on cloud provider and LLMJacking miscreants","Fireworks AI has disclosed a second cyberattack in October, revealing a broader customer data exposure that includes billing records, datasets, and incomplete model weights. The incident began when attackers compromised a third-party cloud provider hosting Fireworks' R&D machines, subsequently accessing development systems to run unauthorized workloads. The company suspects financially motivated criminals involved in LLMJacking, who sell unauthorized access to AI models.","Fireworks AI discloses wider customer data exposure including billing records and model weights after a cloud provider","https:\u002F\u002Fwww.theregister.com\u002Fcyber-crime\u002F2026\u002F11\u002F10\u002Ffireworks-ai-gets-burned-twice-as-customer-data-exposure-widens\u002F5308722","https:\u002F\u002Fimage.theregister.com\u002F?imageId=5308749&width=800","2026-11-10T15:28:00+00:00","2026-11-10T16:00:27.555006+00:00",7,[17,20,23,25,28,30],{"name":18,"type":19},"Fireworks AI","vendor",{"name":21,"type":22},"LLMJacking","threat_actor",{"name":24,"type":19},"Palo Alto Networks",{"name":26,"type":27},"Unit 42","product",{"name":29,"type":19},"Notion",{"name":31,"type":19},"Render","2e06f76c-d5b9-4f54-9eef-4d3447b10730",{"id":32,"icon":34,"name":35,"slug":36},null,"Breaches","breaches",[38,40,45],{"category":39},{"id":32,"icon":34,"name":35,"slug":36},{"category":41},{"id":42,"icon":34,"name":43,"slug":44},"839da5c1-3c34-47e2-9499-f7201640e3ac","AI Security","ai-security",{"category":46},{"id":47,"icon":34,"name":48,"slug":49},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[24,18,29],{"controls":53,"vendors":140},[54,82,111],{"slug":55,"name":56,"problem":57,"products":58},"asset-inventory","Cyber asset inventory","You cannot patch, monitor or protect the devices, cloud resources and accounts you do not know you have.",[59,67,74],{"vendor_slug":60,"vendor_name":61,"vendor_logo":62,"product_slug":63,"product_name":64,"url":65,"description":66},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-cyber-assets","Axonius Cyber Assets","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fcyber-assets","A continuously reconciled view of every asset, who owns it, which security controls cover it and where it drifts from policy.",{"vendor_slug":68,"vendor_name":69,"vendor_logo":70,"product_slug":71,"product_name":69,"url":72,"description":73},"lansweeper","Lansweeper","\u002Fvendor-logos\u002Flansweeper.png","lansweeper-asset-inventory","https:\u002F\u002Fwww.lansweeper.com\u002Fproduct\u002Fasset-inventory\u002F","Discovery with and without agents that keeps one central, always-updated inventory of devices, software and their details.",{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":78,"product_name":79,"url":80,"description":81},"runzero","runZero","\u002Fvendor-logos\u002Frunzero.png","runzero-platform","runZero Platform","https:\u002F\u002Fwww.runzero.com\u002Fplatform\u002F","Finds and fingerprints everything on the network and in the cloud, including IoT and OT devices, without agents or credentials, and flags exposures.",{"slug":83,"name":84,"problem":85,"products":86},"cloud-security-posture","Cloud security posture management (CSPM and CNAPP)","Misconfigured cloud storage and over-permissive roles get caught before they leak.",[87,95,103],{"vendor_slug":88,"vendor_name":89,"vendor_logo":90,"product_slug":91,"product_name":92,"url":93,"description":94},"wiz","Wiz","\u002Fvendor-logos\u002Fwiz.png","wiz-cloud","Wiz Cloud","https:\u002F\u002Fwww.wiz.io\u002Fplatform\u002Fwiz-cloud","Agentless cloud security posture and attack path analysis across major cloud providers.",{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"orca-security","Orca Security","\u002Fvendor-logos\u002Forca-security.png","orca-cloud-security-platform","Orca Cloud Security Platform","https:\u002F\u002Forca.security\u002Fplatform\u002F","Agentless cloud security platform for posture, vulnerabilities and data exposure.",{"vendor_slug":104,"vendor_name":105,"vendor_logo":106,"product_slug":107,"product_name":108,"url":109,"description":110},"crowdstrike","CrowdStrike","\u002Fvendor-logos\u002Fcrowdstrike.png","falcon-cloud-security","Falcon Cloud Security","https:\u002F\u002Fwww.crowdstrike.com\u002Fen-us\u002Fplatform\u002Fcloud-security\u002F","Cloud posture management and workload protection.",{"slug":112,"name":113,"problem":114,"products":115},"third-party-risk-management","Third-party risk management (TPRM)","You know which suppliers could hurt you, and you hear quickly when one of them is breached.",[116,124,132],{"vendor_slug":117,"vendor_name":118,"vendor_logo":119,"product_slug":120,"product_name":121,"url":122,"description":123},"securityscorecard","SecurityScorecard","\u002Fvendor-logos\u002Fsecurityscorecard.png","security-ratings","SecurityScorecard Ratings","https:\u002F\u002Fsecurityscorecard.com\u002Fsolutions\u002Fuse-cases\u002Fsecurity-ratings\u002F","Outside-in security ratings and monitoring of suppliers.",{"vendor_slug":125,"vendor_name":126,"vendor_logo":127,"product_slug":128,"product_name":129,"url":130,"description":131},"bitsight","Bitsight","\u002Fvendor-logos\u002Fbitsight.png","bitsight-tprm","Bitsight Third-Party Risk Management","https:\u002F\u002Fwww.bitsight.com\u002Fproducts\u002Fthird-party-risk-management","Supplier assessments and continuous monitoring based on security ratings.",{"vendor_slug":133,"vendor_name":134,"vendor_logo":135,"product_slug":136,"product_name":137,"url":138,"description":139},"onetrust","OneTrust","\u002Fvendor-logos\u002Fonetrust.png","third-party-management","OneTrust Third-Party Management","https:\u002F\u002Fwww.onetrust.com\u002Fsolutions\u002Fthird-party-management\u002F","Supplier inventory, risk assessments and monitoring across privacy and security.",[141],{"slug":142,"name":24,"logo_path":143,"roles":144},"palo-alto-networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png",[145],"reported_by",{"slug":147,"title":148,"body":149,"framework_refs":150,"framework_notes":156},"third-party-cloud-compromise-exposes-fireworks-ai-customer-data-twice","Third-Party Cloud Compromise Exposes Fireworks AI Customer Data Twice","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.",[151,152,153,154,155],"NIS2 Article 21(2)(d)","ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships","CIS Control 12: Network Infrastructure Management (v8)","NIST SP 800-53 SI-4: System Monitoring","MITRE ATT&CK T1078: Valid Accounts",{"NIS2 Article 21(2)(d)":157,"MITRE ATT&CK T1078: Valid Accounts":158,"NIST SP 800-53 SI-4: System Monitoring":159,"CIS Control 12: Network Infrastructure Management (v8)":160,"ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships":161},"This point explicitly requires measures addressing security risks arising from supplier and third-party relationships, which is the precise vector attackers used to reach Fireworks AI's systems.","The attackers leveraged access obtained through the compromised third-party provider to authenticate into Fireworks AI's development systems, exploiting trusted credentials rather than breaking in through a technical vulnerability.","Continuous monitoring for unauthorized workloads and anomalous resource usage—required by this control—would have detected LLMJacking activity earlier and potentially before the second incident occurred.","Proper network segmentation between third-party-hosted R&D machines and production systems storing billing data and model weights would have limited lateral movement after the initial supplier compromise.","This control requires organizations to define and implement processes to manage information security risks associated with suppliers, which would have included vetting and monitoring the third-party cloud provider's security posture."]