[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fwkpmw0K8Zjyk3cE9_m1FmYd-jxwjVWBobj7FDzC3RLQ":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},"dbfe6272-e177-4fb6-a544-35c37a32489c","third-party-script-injection-via-optimizely-compromises-178-organizations","797fce6e-a7e6-4292-8fe7-a42ac75bdc4d","Third-Party Script Injection via Optimizely Compromises 178 Organizations","An attacker exploited a vulnerability in Optimizely's web experimentation platform to inject malicious JavaScript into the websites of 178 customer organizations, including major media and financial firms. Because these organizations trusted and loaded Optimizely's scripts directly into their pages, a single compromised platform became a force-multiplier for credential theft, payment card skimming, and crypto theft. This is a classic supply chain attack: the victims did not introduce the vulnerability themselves, but their users paid the price. Organizations that rely on third-party JavaScript must treat those dependencies as a potential attack surface and monitor them accordingly.","**Immediate actions:**\n- Audit all third-party JavaScript dependencies currently loaded on customer-facing web properties and remove any that are not strictly necessary.\n- Implement Subresource Integrity (SRI) hashes for all externally hosted scripts so browsers reject tampered versions.\n- Deploy a Content Security Policy (CSP) that restricts which scripts and domains are permitted to execute on your pages.\n\n**Long-term improvements:**\n- Establish a formal third-party vendor risk management process that includes security assessments and contractual breach-notification requirements.\n- Continuously monitor external scripts loaded on your sites for unexpected changes using automated diffing or client-side security tooling.\n- Maintain a real-time software inventory (including third-party SaaS dependencies) so affected assets can be identified immediately when a vendor incident is disclosed.\n\n**Detection measures:**\n- Enable browser-side telemetry and anomaly alerting to detect unexpected outbound data flows (e.g., to unknown cryptocurrency or exfiltration endpoints).\n- Subscribe to threat intelligence feeds and vendor security advisories so your team is alerted to compromise events affecting suppliers without delay.\n- Review web application firewall and CDN logs regularly for signs of unauthorized script modifications or suspicious payload delivery.",[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","MITRE ATT&CK T1195.002: Compromise Software Supply Chain",{"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,"MITRE ATT&CK T1195.002: Compromise Software Supply Chain":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"NIS2 explicitly requires security measures addressing supply chain risks; vetting the security practices of a third-party script provider like Optimizely falls directly under this obligation.","This control requires organizations to protect against supply chain threats by assessing and monitoring third-party components, which would have prompted scrutiny of Optimizely's integrity before or during the compromise.","OWASP A08 specifically covers the failure to verify the integrity of third-party scripts and software, which is precisely what allowed the injected malicious JavaScript to execute undetected across victim sites.","The attacker compromised Optimizely's platform to distribute malware through its legitimate delivery channel to downstream customer websites, matching this technique exactly.","Maintaining an inventory of all third-party scripts and SaaS dependencies would have allowed affected organizations to quickly identify exposure when Optimizely's compromise was disclosed.","published","2026-11-17T12:20:26.380311+00:00","2026-11-17T12:20:26.354+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.helpnetsecurity.com\u002F2026\u002F11\u002F17\u002Foptimizely-vulnerability-malicious-javascript\u002F","malware-spread-through-optimizely-hits-178-organizations-including-bbc-cnn-and-z-ec4cbc","Malware spread through Optimizely hits 178 organizations, including BBC, CNN and Zoom",[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},"879269f2-d7d9-41c9-9b36-d124cc439154","2026-11-17","afternoon","ThreatNoir Afternoon Brief — November 17","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-17\u002Fthreatnoir-afternoon-brief-2026-11-17.mp3",[51,54,58],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":55,"name":56,"problem":57},"waf-ddos","Web application firewall and DDoS protection","Websites and APIs stay up, and common web attacks are filtered before they reach them.",{"slug":59,"name":60,"problem":61},"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."]