--- title: "Optimizely Web Experimentation Hijack: What to Check Now" url: https://playciso.com/blog/optimizely-web-experimentation-script-injection updated: 2026-11-20 section: Blog publisher: PlayCISO --- # Optimizely Web Experimentation Hijack: What to Check Now > A signup-flow flaw let attackers put card-skimming, wallet-swapping JavaScript into Optimizely Web projects on 16 Nov 2026. What is confirmed, what to do. Source: https://playciso.com/blog/optimizely-web-experimentation-script-injection · Published: 2026-11-20 · Publisher: PlayCISO (https://playciso.com) Primary source: https://status.optimizely.com/incidents/ftw0fh9wx43z --- **Attackers turned Optimizely's own snippet into a delivery channel for card-skimming and wallet-swapping JavaScript.** Optimizely says that on **16 November 2026** an unauthorized third party exploited a flaw in the **Web Experimentation account signup flow**, impersonated users on targeted customer accounts and inserted malicious JavaScript into those customers' projects. Because Optimizely Web runs project JavaScript on every page that loads the customer's snippet, the code reached those sites' visitors. Optimizely says it closed the flaw within three hours of detection and removed the code the same day. [Zscaler ThreatLabz](https://www.zscaler.com/blogs/security-research/attackers-exploit-optimizely-flaw-inject-malicious-javascript) counted **more than 450 domains** serving it; [Report URI](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/) found it in **188 snippets for 178 organisations**. Some iOS users were targeted with exploit-chain delivery attempts; successful iOS exploitation was not established. **Who this is for:** CISOs, web and e-commerce owners, marketing-technology owners and anyone who runs Optimizely Web or another tag that executes vendor-editable JavaScript on their pages. *Based on Optimizely's incident notice, Zscaler ThreatLabz's analysis and Report URI's analysis, read on 20 November 2026. We first summarised the incident in our [17-18 November roundup](/blog/cyber-incidents-17-18-november-2026-whats-confirmed). PlayCISO is not affiliated with Optimizely, Zscaler or Report URI. We publish no indicators; Zscaler and Report URI list them.* Confirmed vs not yet known **Optimizely confirms:** a flaw in the Web Experimentation signup flow was exploited on 16 November to impersonate users on targeted customer accounts and insert malicious JavaScript; it was detected and blocked that day and the vulnerability closed within three hours of detection; the code was removed from all affected projects; fewer than 5% of customers were impacted; "This was not a credentials breach"; no other Optimizely product was affected. **Reported by researchers:** what the script did (wallet-address swapping, cookie and screenshot theft, card skimming, iOS exploit-kit loading) and its reach: more than 450 domains and 3,000 URLs (Zscaler), 188 infected snippets for 178 organisations (Report URI), and about $7,040 reaching attacker wallets by 19:25 UTC on 16 November (Report URI). **Not established:** any successful compromise of an iPhone or iPad; how many card numbers were captured; who the attacker is; and the technical details of the signup-flow flaw. No CVE has been published. ## What happened Optimizely Web Experimentation lets a customer add custom code in a **Project JavaScript** field; Optimizely's snippet then runs that code on every page of the customer's site that loads the snippet. Zscaler says the attacker used the signup-flow weakness to get unauthorised write access to that field in multiple customer projects. Optimizely's notice of 18 November says the attacker "used it to impersonate users on targeted customer accounts" and insert the code. - Optimizely's response (its account): it detected the activity on the day it began, blocked delivery of the malicious code, closed the vulnerability within three hours of detection, removed the injected code from all affected projects, secured affected user accounts, added protections against unauthorised code delivery and contacted every Web Experimentation customer directly. Zscaler adds, citing Optimizely, that sessions were ended, tokens revoked and access reset for affected accounts. - Scope (Optimizely): fewer than 5% of customers; no other product affected. Optimizely says customers who do not use Web Experimentation need do nothing. - Reach (researchers): Report URI checked 1,611 distinct snippets and found the code in 188 belonging to 178 organisations, with banking and finance the largest sector. Zscaler counted more than 450 unique domains and 3,000 URLs across airlines, banking, retail, insurance, media, telecoms and other sectors. The two counts measure different things, so they do not contradict each other. ## What the injected JavaScript did Per Zscaler and Report URI. Report URI says the payload was rebuilt 26 times during the day. - Wallet-address swapping. It watched page text, forms, the clipboard and outgoing requests for addresses on eight cryptocurrencies, including Bitcoin, Ethereum, Tron and Solana, and replaced them with the attacker's. - Cookie and screenshot theft. When a swap was visible, it sent the page URL, a screenshot and cookies not marked HttpOnly to the attacker. - Card skimming. Later versions captured card numbers, expiry dates and CVVs from page forms and submissions. Zscaler says it could not read payment fields inside secure cross-origin iframes, which is why hosted payment fields matter. - iOS exploit-kit delivery. On iPhone and iPad visits it tried to load the Coruna and DarkSword exploit kits. Zscaler says the script "reportedly attempted to load" them and that wider impact "would depend on successful exploitation by the iOS/WebKit exploit chain". Report URI says the kits target older iOS 13 to 18 releases and fingerprint iOS 26, and that pages on iOS 18.6 or earlier reloaded every 60 seconds to retry. Successful iOS exploitation was not established. ## Timeline | Date (UTC) | Event | Source | | --- | --- | --- | | 16 Nov, 04:21 | First injected Optimizely snippet observed | Report URI | | 16 Nov, 08:10 | First build of the wallet-swapping payload | Report URI | | 16 Nov, 13:43 | Card skimmer added to the payload | Report URI | | 16 Nov, 17:13-17:57 | iOS exploit-kit loading added | Report URI | | 16 Nov | Optimizely detects the activity, blocks delivery and closes the vulnerability within three hours of detection | Optimizely | | 16 Nov, ~20:40-23:11 | Mass clean-up; Report URI finds all infected files clean by 23:11 | Report URI | | 17 Nov, 01:02 | Optimizely's first status update: vulnerability fixed, injected code removed | Optimizely | | 18 Nov | Zscaler ThreatLabz publishes its analysis | Zscaler | | 18 Nov, 14:49 | Optimizely update: signup-flow flaw, under 5% of customers, every Web Experimentation customer contacted | Optimizely | ## What security leaders should do this week - If you use Optimizely Web, read what Optimizely sent you and confirm whether your projects were affected. Optimizely says it contacted every Web Experimentation customer. - Review project JavaScript and change history. Audit every Project JavaScript field and experiment code against what your team deployed, and review change history, user activity and new account or user creation around 16 November. Check that production pages load only the snippet versions you approved. - Rotate and lock down access. Reset credentials for experimentation-platform administrators, rotate API tokens, session tokens and integration keys, and require MFA for every user of experimentation and personalisation tools (Zscaler's advice). Remove dormant users. - Enforce a Content Security Policy. A [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) that limits script-src and, above all, connect-src to sources you expect stops injected code from loading new scripts or sending stolen data to an attacker's server. Run it in enforcement mode with reporting turned on, and check your current headers with the [security headers checker](/tools/security-headers-checker). Report URI says some affected sites' CSP blocked the payload outright. - Use Subresource Integrity where it fits. [SRI](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) pins a script to a hash, which is right for static third-party libraries. It cannot pin a snippet whose content changes every time someone edits a project, which is exactly how this attack arrived, so pair it with CSP and change monitoring rather than relying on it. - Monitor scripts for unexpected changes. Keep an inventory of third-party scripts, remove the ones you do not need, and alert on changes to the content your pages load, not only to your own code. - Keep payment fields in hosted iframes. The skimmer could not read card fields inside secure cross-origin iframes, per Zscaler. If your checkout takes card numbers in page forms, treat cards entered on affected pages on 16 November as possibly exposed and take advice from your payment provider and counsel on notification. - Treat the vendor as part of your attack surface. Record the incident with the [third-party breach response checklist](/tools/third-party-breach-response-checklist) and ask every tag and experimentation vendor how customer-editable code is protected, using the [vendor risk scorecard](/tools/vendor-risk-scorecard). Visitors should update iPhones and iPads to the current iOS, check cryptocurrency transfers made around 16 November for swapped addresses, and watch card statements. ## Frequently asked questions ### What happened with Optimizely Web Experimentation? Optimizely says that on 16 November 2026 an unauthorized third party exploited a flaw in the Web Experimentation account signup flow, used it to impersonate users on targeted customer accounts and inserted malicious JavaScript into those customers' projects. Optimizely says it detected the activity that day, blocked delivery of the code, closed the vulnerability within three hours of detection and removed the code from all affected projects. ### Was Optimizely breached? Optimizely calls it a security incident in which a vulnerability was exploited, and says "This was not a credentials breach". It says no other Optimizely product was affected and fewer than 5% of its customers were impacted. It has contacted every Web Experimentation customer directly to say whether they were affected. ### What did the malicious Optimizely script do? Per Zscaler ThreatLabz and Report URI, it swapped cryptocurrency wallet addresses on the page, in forms, in the clipboard and in outgoing requests for attacker wallets; sent screenshots, page URLs and non-HttpOnly cookies to the attacker when a swap happened; in later versions captured card numbers, expiry dates and CVVs typed into page forms; and on iPhones and iPads tried to load the Coruna and DarkSword exploit kits. ### Were iPhones hacked through the Optimizely injection? That has not been established. Some iOS users were targeted with exploit-chain delivery attempts; successful iOS exploitation was not established. Zscaler says the script "reportedly attempted to load" the Coruna and DarkSword kits and that wider impact "would depend on successful exploitation". Report URI says the kits target older iOS versions, so update to the current iOS release. ### How many websites were affected? The counts measure different things. Report URI checked 1,611 Optimizely snippets and found the code in 188 belonging to 178 organisations. Zscaler counted more than 450 unique domains and more than 3,000 URLs serving the script. Optimizely says fewer than 5% of its customers were impacted. ### What should Optimizely customers do? Read Optimizely's message to you, audit every Project JavaScript field and recent change history, check account creation and user activity for the exposure window, rotate administrator credentials and API tokens, require MFA, enforce a Content Security Policy that limits where scripts can load from and send data to, and monitor third-party scripts for unexpected changes. If card or wallet data could have been entered on affected pages on 16 November, take advice on notification. ### Is there a CVE for the Optimizely flaw? No CVE had been published as of 20 November 2026. The flaw was in Optimizely's hosted service, which Optimizely says it has fixed; customers do not install a patch. ## Sources - [Optimizely status page: security incident notice](https://status.optimizely.com/incidents/ftw0fh9wx43z) (updates 17 November 01:02 UTC and 18 November 14:49 UTC) - [Zscaler ThreatLabz: Attackers exploit Optimizely flaw to inject malicious JavaScript](https://www.zscaler.com/blogs/security-research/attackers-exploit-optimizely-flaw-inject-malicious-javascript) (Atinderpal Singh and Jithin Prajeev Nair, 18 November 2026) - [Report URI: World's largest brands infected with malware via Optimizely](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/) (Scott Helme, 16 November 2026, updated 17 November) - [MDN: Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) and [Subresource Integrity](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity)