At least 178 top web destinations unwittingly served malicious JavaScript on November 16, 2026, after an attacker exploited a vulnerability in Optimizely’s Experiments platform, according to security researchers.
The attack in brief: widespread, iterative, and tailored
Report URI researcher Scott Helme reported that on November 16 malicious JavaScript was delivered to visitors of 178 organizations via Optimizely. The payload was rebuilt 26 times during the day and dropped a multi‑purpose malware kit capable of stealing payment card data, cookies and screenshots, and of swapping cryptocurrency payment addresses for the attacker’s. The compromised scripts also served exploit code for known vulnerabilities in older Apple iPhone and iPad devices — zero‑click exploit chains known as “DarkSword” and “Coruna.”
How the supply‑chain failure worked
Optimizely provides JavaScript snippets that websites embed to run experiments and render features. JavaScript executes on users’ devices and can both read and modify content displayed in the browser. Zach Edwards, a researcher at Infoblox and co‑founder of DecryptAds, explained why that positioning made the attack immediate: “So to make the product work as expected, this code is setup to fire immediately on‑page load, and not restrict rendering behind a consent dialog box,” he said. “This means that this supply chain attack didn’t require any clicking or consent to trigger — most of the impacted clients would immediately serve up the payload as soon as someone loaded the page.”

The cyber insurance questionnaire just landed. Now what?
SOC 2, HIPAA, insurance renewals - someone has to own security strategy. Nubivance provides fractional CISO leadership without the full-time salary.
Get a security leadOptimizely’s announced containment steps
Optimizely told KrebsOnSecurity that on November 16, 2026 it “identified a security incident in which an unauthorized party exploited a vulnerability in the Optimizely Experimentation to add malicious JavaScript to some customer projects.” The company said it “acted swiftly to contain the incident and have fully remediated the identified vulnerability.” Measures Optimizely listed included blocking access to the vulnerable path, deploying a fix, removing injected code from affected projects, ending active sessions, revoking tokens, resetting access for affected user accounts, and “implementing additional protections to prevent malicious code from being delivered in Cloudflare.” Optimizely said it is working with third‑party experts on a comprehensive investigation and published an initial findings report (PDF) on November 18.
Content Security Policies: the technical firewall that many sites lack
Report URI assessed how the affected sites fared against Content Security Policies (CSPs), which limit which domains can serve third‑party content. The findings were blunt: 68 of the impacted sites had no CSP at all, 50 had CSPs that still allowed the malicious payload and data exfiltration, and only 24 of the affected sites (15 percent) had CSPs that fully blocked the malicious code. Helme’s broader measurement via crawler.ninja puts CSP deployment across the Web’s busiest sites at roughly 10 percent. As Helme put it, “The important lesson here is that trusted JavaScript doesn’t always remain trustworthy.”
What this means for technologists, affected enterprises, and end users
- Technologists and security teams: The incident highlights immediate value in deploying restrictive, well‑tested CSPs and reviewing which third‑party snippets run before user consent flows. As Edwards warned, “With literally all websites which embed 3rd party JavaScript resources, if you don’t have a content security policy then if any of those partners get compromised, new domains can be injected into your website via JavaScript which won’t be stopped.”
- Affected enterprises and procurement leaders: Sites that embed experiment or marketing code need incident playbooks that assume third‑party providers can be compromised. Optimizely’s list of remediation steps provides a partial template — block vulnerable paths, remove injected code, revoke tokens and reset accounts — but organizations must also audit which partners run code before consent dialogs appear.
- End users and general public: Reporters noted practical defenses at the browser level — script‑blocking extensions such as NoScript or modern ad/script blockers can prevent most third‑party JavaScript from executing. As KrebsOnSecurity observed, “Ten years ago, the standard security advice for end users was to install antivirus and enable a firewall. These days, your ad/script blocker is your firewall.”
Report URI estimated the attackers stole roughly $7,500 worth of virtual currency and an unknown number of payment card records; Helme said the incident could have been far worse had more sites lacked countermeasures. He expressed hope that the episode will spur wider CSP adoption, but the data are stark: among the most heavily trafficked sites, effective CSPs remain uncommon. The next question is operational as much as technical — will downstream sites change how and when third‑party JavaScript is allowed to run, and will vendors adopt stronger defaults to prevent trusted scripts from becoming attack vectors?
https://krebsonsecurity.com/2026/11/attackers-used-optimizely-to-a-b-test-malware-on-top-websites/




