[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f95UFzebI4I8Exrt34YXubBoi2_I6hl8WFFFLVZY7_y0":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"8a93c2de-1886-44b6-bfa9-8487aa9ea8f9","optimizely-cdn-compromise-poisons-major-brands-via-supply-chain-attack","49dc7bf0-99c5-4832-9ea0-525a81e64035","Optimizely CDN Compromise Poisons Major Brands via Supply Chain Attack","Attackers compromised JavaScript files hosted on Optimizely's content delivery network, silently injecting malicious code into the websites of 178 organizations—including Zoom, CNN, and Salesforce—without those organizations modifying any of their own code. This highlights a critical blind spot: companies that trust third-party scripts implicitly inherit any security failures of those providers. The malicious scripts were designed to steal cryptocurrency and payment credentials, and to exploit iOS device vulnerabilities, demonstrating how a single CDN compromise can enable large-scale data theft. Organizations had no direct control over the tampered files yet bore full exposure to their customers. Without proactive monitoring of third-party script integrity, such attacks can persist undetected for extended periods.","**Immediate actions:**\n- Audit all third-party JavaScript dependencies and verify their integrity against known-good hashes immediately.\n- Implement Subresource Integrity (SRI) attributes on all externally hosted scripts to block execution of tampered files.\n- Review Content Security Policy (CSP) headers to restrict which external domains are permitted to serve executable scripts.\n\n**Long-term improvements:**\n- Conduct formal security assessments of critical third-party vendors and require evidence of their security controls.\n- Maintain an inventory of all third-party scripts, CDNs, and external dependencies used across your web properties.\n- Establish contractual obligations with vendors for timely breach notification and minimum security standards.\n\n**Detection measures:**\n- Deploy client-side script monitoring tools (e.g., browser telemetry or real user monitoring) to detect unexpected script behavior or new network destinations.\n- Configure automated alerts for changes to externally loaded JavaScript files using file integrity or CDN monitoring services.\n- Regularly scan your website's loaded resources for newly introduced or modified third-party scripts.",[12,13,14,15,16],"CIS Control 2: Inventory and Control of Software Assets (v8)","NIS2 Article 21(2)(d)","NIST SP 800-53 SA-12: Supply Chain Protection","OWASP A08:2021 Software and Data Integrity Failures","NIST CSF 2.0 DE.CM-09: Monitoring of external service providers",{"NIS2 Article 21(2)(d)":18,"NIST SP 800-53 SA-12: Supply Chain Protection":19,"OWASP A08:2021 Software and Data Integrity Failures":20,"CIS Control 2: Inventory and Control of Software Assets (v8)":21,"NIST CSF 2.0 DE.CM-09: Monitoring of external service providers":22},"NIS2 Article 21(2)(d) explicitly requires security measures addressing supply chain risks; this attack succeeded precisely because organizations lacked controls over the security practices of their CDN provider, Optimizely.","SA-12 requires organizations to apply security safeguards to protect against supply chain threats; enforcing SRI and vetting CDN providers would have been required controls under this item.","OWASP A08 specifically addresses the failure to verify the integrity of software and data from external sources, which is exactly how malicious JavaScript was silently delivered through Optimizely's CDN without detection.","CIS Control 2 requires organizations to maintain an inventory of authorized software, including third-party scripts; had the 178 affected organizations tracked and validated their CDN-sourced JavaScript assets, the unauthorized modification would have been detectable.","DE.CM-09 calls for continuous monitoring of external service providers' activities; ongoing integrity checks of Optimizely-served scripts would have detected the injected malware before widespread harm occurred.","published","2026-11-17T03:20:44.016685+00:00","2026-11-17T03:20:44.003+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Foptimizely-supply-chain-attack-infects-major-brands-sites-with-malware\u002F","optimizely-supply-chain-attack-infects-major-brands-sites-with-malware-cb498b","Optimizely supply chain attack infects major brands' sites with malware",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"4a34572e-ce43-438e-a28e-49cbf1a3a04a","2026-11-17","morning","ThreatNoir Morning Brief — November 17","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-17\u002Fthreatnoir-morning-brief-2026-11-17.mp3",[51,55,59],{"slug":52,"name":53,"problem":54},"saas-security-posture","SaaS security posture management (SSPM)","Business apps like Microsoft 365 and Salesforce stop leaking through risky settings and connected apps.",{"slug":56,"name":57,"problem":58},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",{"slug":60,"name":61,"problem":62},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]