Optimizely Web Experimentation Malware: What Sites Should Do
Optimizely Web Experimentation malware hit 178 organisations on November 16, 2026. What the code did and the checks sites running test scripts should do now.

In this article
Optimizely Web Experimentation malware reached visitors of some of the best known sites on the web on November 16, 2026. An attacker added malicious JavaScript to customer projects in the A/B testing tool, so the code loaded on every page that carried the Optimizely snippet. Optimizely confirmed the incident on its status page, saying an unauthorized party “exploited a vulnerability in Experimentation” to inject the code.
The first detailed public analysis came from security researcher Scott Helme at Report URI. His sweep of Optimizely snippets found 188 infected snippets belonging to 178 organisations, and he says the real number is likely higher.
This matters far beyond Optimizely customers. Marketing teams load testing, tag and personalisation scripts on almost every page, often with less review than the main site code. This incident shows what happens when one of those vendors is compromised.

What happened in the Optimizely attack
Optimizely Web Experimentation lets marketers change pages and run tests by adding custom code to a project. One of those places is Project JavaScript, which runs on every page where the snippet loads. According to Report URI, the attacker used this to deliver its payload.
Optimizely’s status notice, posted on November 17, 2026 at 01:02 UTC, says the company has fixed the vulnerability, removed the injected code from affected projects, secured the affected user accounts and added protections against unauthorized code delivery. At the time of writing the incident was still listed as “Monitoring”. Search Engine Journal’s report says the attacker abused a flaw in the signup flow; Optimizely has not published a full technical write up yet.
Report URI’s timeline puts the first injection at 04:21 UTC on November 16, with a mass clean up starting around 20:40 UTC the same day. Named affected brands in its analysis include Zoom, the BBC, CNN, Salesforce, GitLab, IKEA and HSBC.
What the malicious code did
The payload was a multi purpose kit, not a single trick. Report URI describes four parts:
| Behaviour | What it targeted |
|---|---|
| Crypto address swapping | Replaced wallet addresses in page text, forms, the clipboard and outgoing requests |
| Card skimming (added 13:43 UTC) | Card number, expiry and CVV typed into site forms |
| Data theft | Page URL, cookies that were not HttpOnly and screenshots in some payment contexts |
| iOS exploit kits | Coruna and DarkSword exploit chains on older iPhones and iPads |
Card fields inside hosted payment iframes were out of reach, according to Report URI. That is a strong argument for keeping payment fields on a payment provider’s hosted form rather than on your own page.
As of 19:25 UTC on November 16, the attacker’s wallets had received about $7,040, Report URI says. It cannot see how many card numbers or cookies were captured, so the true damage is unknown.
Why marketing scripts are a security risk
Every script you add to a page runs with the same power as your own code. It can read forms, change links and send data anywhere unless you limit it. Testing tools are especially sensitive because their job is to rewrite pages.
We covered a similar pattern this week in our article on Gootloader SEO poisoning, where hacked sites became the delivery system. The lesson is the same: the more third party access a site has, the more places an attacker can enter. If you build your own tests, our guide to a JavaScript A/B testing script shows how small a self hosted setup can be.
What sites using Optimizely should do now

These steps combine Report URI’s recommendations with Optimizely’s own documentation. The order is our recommendation.
- Read Optimizely’s notice and your email. Optimizely says it notified affected customers. Check the account owner inbox and the status page for updates.
- Review Project JavaScript and custom code. Report URI suggests searching for the domain
1688360.cc, the stringatob(and any script you do not recognise. - Check the change history. Optimizely’s change history records edits to project JavaScript and can be filtered by date and by source (REST API or the web interface). Look closely at November 16 and the days around it.
- Rotate access. Review who has access to the Optimizely account, remove old users and rotate passwords and API tokens.
- Treat card data from November 16 as possibly exposed. Report URI advises this for sites that take card details in their own forms. Talk to your payment provider and legal team about customer communication.
- Rotate secrets in readable cookies. Any session or token stored in a cookie without the HttpOnly flag could have been read.
Tighten your Content Security Policy
A Content Security Policy (CSP) tells the browser which domains a page may load scripts from and send data to. Report URI recommends restricting connect-src, avoiding 'unsafe-eval' and 'strict-dynamic', and turning on violation reporting.
Note that Optimizely’s own CSP setup guide suggests a nonce with 'strict-dynamic' for script-src. You will need to weigh convenience against control. Optimizely suggests testing in report only mode first, which is a safe way to see what breaks before you enforce anything.
The same thinking applies to tag managers. Our guide to common GTM mistakes and the recent change that upgrades the Google tag to a Tag Manager container are good prompts to audit who can publish code on your site.
FAQ about the Optimizely Web Experimentation malware
Was every Optimizely customer affected?
No. Optimizely says the code was added to “some customer projects”. Report URI checked 1,611 snippets and found 188 infected, but says the full count is likely higher.
Is the malicious code still running?
Optimizely says it removed the injected code from affected projects. Report URI reported that nearly all infected snippets were clean by late on November 16. Still check your own project.
Does this affect Optimizely Feature Experimentation or the CMS?
The status page names Web Experimentation (snippet delivery) as the affected component. It does not mention other Optimizely products.
What should site visitors do?
Report URI advises iPhone and iPad users to update to iOS 18.7.3 or later, or 26.3 or later, to check crypto addresses before paying and to watch card statements.

