Breaking
Optimizely Supply Chain Attack Hits 178 Organisations Including Zoom, BBC and CNN
Attackers exploited a vulnerability in Optimizely Web Experimentation to inject malicious JavaScript into customer projects, serving crypto stealers, card skimmers and iOS exploit kits from Optimizely's own CDN for nearly 19 hours.

By TechWhoKnows
4 min read
A supply chain attack on Optimizely Web Experimentation compromised 178 organisations on 16 November 2026, turning a trusted A/B testing script into a malware delivery channel for some of the world's best-known websites.
According to research from Report URI, SOCRadar and Safeguard, attackers exploited a vulnerability in Optimizely's Experimentation product to add malicious JavaScript to the Project JavaScript field of customer projects. The malicious code was then served from Optimizely's own CDN to visitors of affected sites for nearly 19 hours.
Scale and impact
Report URI analysed 1,611 Optimizely snippets and found 188 infected snippets belonging to 178 organisations. The real number is likely higher. Named victims include Zoom, BBC, CNN, HSBC, GitLab, Salesforce, Fox News and numerous other household brands across banking, media, travel, retail and technology sectors.
Attack chain
The attacker wrote a small loader into the Project JavaScript field of many unrelated customer projects. Every visitor to an affected page downloaded the snippet from Optimizely's CDN, ran the loader, and fetched a second-stage script (track.js) from the attacker's domain 1688360.cc.
The payload delivered four distinct threats:
Cryptocurrency address swapping, replacing wallet addresses on page with attacker-controlled addresses
Credit card skimming, harvesting payment details typed into forms
Cookie and screenshot theft, exfiltrating session data to the attacker
iOS exploit kits, targeting older iOS versions with Safari/WebKit exploits
Optimizely response
Optimizely's status page entry posted at 01:02 UTC on 17 November 2026 states: "Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. We've fixed the vulnerability and removed the injected code from affected projects. We've also taken steps to secure affected user accounts and put additional protections in place to prevent unauthorized code from being delivered."
The company has not published a detailed postmortem, a count of affected projects, or technical details of the vulnerability.
Defensive lessons
Report URI found that allowing the vendor host in Content Security Policy (CSP) did not help, only 24 of 256 affected organisations' own hosts blocked the payload. What stopped it was a restrictive script-src without 'strict-dynamic' or 'unsafe-eval', plus tight connect-src to stop data exfiltration.
Subresource Integrity (SRI) cannot protect dynamic vendor snippets that are rebuilt whenever experiments change, an integrity hash either breaks experiments or gets turned off.
Immediate actions for affected organisations
Review all Project JavaScript and experiment code in Optimizely dashboards
Rotate exposed tokens, cookies and credentials
Scope card and session exposure for 16 November 2026
Move CSP from report-only to enforce mode
Implement change monitoring on every third-party script loaded
CISA is expected to add this vulnerability to its Known Exploited Vulnerabilities catalogue, which would require federal agencies to patch by a specified deadline.
Sources
- 1Safeguard Blog (detailed technical analysis)safeguard.sh
- 2SOCRadar (victim list and payload details)socradar.io
- 3Report URI (original research, 188 infected snippets)report-uri.com