[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJvnW6GKClPDSYeliIFS-TTZRUYaO8BgLvVBFs8QJZKU":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},"d33b1539-dfe6-4990-a77a-311e820f9293","optimizely-platform-compromise-poisons-178-major-websites-via-malicious-javascript","ab3300a7-6fe3-4eff-93cc-cf308d093480","Optimizely Platform Compromise Poisons 178 Major Websites via Malicious JavaScript","Attackers compromised the Optimizely platform itself, allowing them to inject malicious JavaScript served from Optimizely's own trusted domain with a valid certificate — meaning browsers and security tools had no inherent reason to block it. For approximately 17 hours, visitors to 178 high-profile sites including Zoom, BBC, and CNN were exposed to crypto-clipping, payment card skimming, and iOS exploit kits. This incident illustrates the classic supply chain attack risk: when you trust a third-party vendor, you implicitly trust everything they serve. Organizations that relied on Optimizely had no direct control over the compromise, yet their customers bore the consequences. Robust third-party risk management and real-time integrity monitoring of externally loaded scripts are essential defenses.","**Immediate actions:**\n- Audit all third-party JavaScript dependencies currently loaded on your websites and remove any that are not strictly necessary.\n- Implement Subresource Integrity (SRI) hashes for all externally hosted scripts so browsers reject tampered or unexpected code.\n- Deploy a strict Content Security Policy (CSP) header to restrict which domains are permitted to execute scripts on your site.\n\n**Long-term improvements:**\n- Establish a formal third-party vendor risk assessment process that includes ongoing security posture reviews and contractual incident notification obligations.\n- Evaluate and adopt client-side script monitoring solutions that alert on unexpected changes to externally loaded JavaScript in real time.\n- Maintain an authoritative inventory of all third-party services and scripts integrated into your web properties.\n\n**Detection measures:**\n- Configure real-time alerting on unexpected changes to page content or new outbound network connections originating from your web properties.\n- Monitor threat intelligence feeds and vendor security advisories for compromises affecting your third-party service providers.\n- Review web server and CDN logs regularly for anomalous script-loading patterns or unusual visitor behavior indicative of skimming activity.",[12,13,14,15,16],"MITRE ATT&CK T1195.002: Compromise Software Supply Chain","NIS2 Article 21(2)(d)","CIS Control 2: Inventory and Control of Software Assets (v8)","PCI DSS Requirement 6.4","NIST SP 800-53 SR-6: Supplier Assessments and Reviews",{"NIS2 Article 21(2)(d)":18,"PCI DSS Requirement 6.4":19,"NIST SP 800-53 SR-6: Supplier Assessments and Reviews":20,"MITRE ATT&CK T1195.002: Compromise Software Supply Chain":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"NIS2's supply chain security point requires organizations to manage security risks arising from their third-party suppliers and service providers, which is precisely the relationship that was exploited here.","PCI DSS Requirement 6.4 mandates protection of web-facing applications, including controls over third-party scripts that handle or could access payment card data, directly applicable to the skimming component of this attack.","This control requires organizations to assess and monitor the security practices of suppliers, which would have included evaluating Optimizely's integrity controls and responding faster when the compromise occurred.","Attackers compromised the Optimizely platform upstream, causing malicious code to be distributed automatically to all downstream customer websites — the exact scenario this technique describes.","Knowing exactly which third-party scripts are loaded on your web properties is a prerequisite for detecting unauthorized or tampered external code like the injected Optimizely JavaScript.","published","2026-11-17T03:20:24.904452+00:00","2026-11-17T03:20:24.886+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.cyberkendra.com\u002F2026\u002F11\u002Foptimizely-malware-hits-zoom-bbc-cnn-what-to-do.html","optimizely-malware-hits-zoom-bbc-cnn-what-to-do-670d1b","Optimizely Malware Hits Zoom, BBC, CNN: What to Do",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"c8b843a5-d5a7-41d1-8d3b-cabded09d2ef","Data Protection","data-protection","Unencrypted data, missing DLP, poor classification","#3b82f6",{"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},"security-monitoring-siem","Security monitoring (SIEM)","Logs from everywhere end up in one place, with alerts that someone actually sees.",{"slug":56,"name":57,"problem":58},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",{"slug":60,"name":61,"problem":62},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]