On 16 November 2026, an attacker used a flaw in Optimizely Web Experimentation to add harmful code to its customers’ websites. Visitors to sites run by the BBC, Zoom, HSBC, IKEA and others were served it for part of that day.
Few people think of a website testing tool as a supplier with access to every page. This one had it.
What happened
Optimizely Web Experimentation lets organisations test different versions of their web pages. A small piece of Optimizely’s code, called a snippet, sits on each page and loads from Optimizely’s servers. Customers can also add their own code to it, which then runs on every page.
The attacker placed harmful code in that customer code area, so Optimizely’s servers delivered it to each site’s visitors. Optimizely posted a notice at 01:02 UTC on 17 November. It says “an unauthorized party exploited a vulnerability in Experimentation”. That party then “used it to add malicious JavaScript to some customer projects”. It has not said how many customers were affected, or how the attacker got in.
Report URI, a service that monitors what code runs on websites, examined 1,611 Optimizely snippets. It found 188 infected snippets belonging to 178 organisations. It says “the real number is likely higher”.
According to Report URI, the harmful code did several things, including:
- Swapped cryptocurrency addresses. It replaced wallet addresses on the page with the attacker’s own. About $7,000 reached the attacker.
- Read card details. From 13:43 UTC it watched for card numbers typed into a site’s own forms. Cards entered on a payment provider’s hosted form were out of its reach.
- Sent iPhone and iPad visitors elsewhere. It loaded known tools for attacking Apple devices. Hudson Rock, a threat intelligence company, says this shows delivery, not that any device was compromised. SOCRadar says no public report has confirmed an infected device.
The first infected snippet was seen at 04:21 UTC on 16 November, and all were clean by 23:11 UTC. Optimizely says it has fixed the flaw, removed the code, “taken steps to secure affected user accounts” and added protections against unauthorised code.
What to do now
If you use Optimizely, Report URI suggests checking your own code in the service for scripts you didn’t write. Review users, access tokens and connected services, and change credentials. Treat cards entered on your site on 16 November as possibly exposed. Consider whether you need to tell your customers.
The wider lesson applies to any code from outside that runs on your web pages, such as testing, analytics or chat tools. The Blueprint requirements this tests:
- RW-SUP-01 A list of your suppliers (Foundation). It records “what data or access” each supplier has. Code that runs on every page is access.
- RW-DEV-02 A list of the software and services you run (Foundation). Include the outside scripts on your website.
- RW-SUP-02 Supplier access limited to the job (Foundation). A testing tool may not need to run on payment or sign-in pages.
- RW-LAW-07 Card payments taken safely (Foundation). Cards on hosted payment forms were out of the code’s reach.
- RW-SUP-15 Critical suppliers in your incident plans (Advanced). Know who to call at a supplier, and how to switch its code off quickly.
- RW-DET-05 Incidents reported on time (Foundation). If card or personal data may have been taken, check what the law and your contracts require you to report.
How RiskWitness helps
Do we use it, and where? Suppliers and Assets. Record Optimizely, or any similar tool, as a supplier, with its criticality and the access it has. Link it to the websites it runs on.
Has anything happened to us? Incidents. Log an incident with a handler, linked to the supplier, the website and the risk. Record which regulators may need telling, and their deadlines.
What did the supplier tell us? Suppliers. Keep Optimizely’s notices and answers as assurance evidence. Send a questionnaire to other suppliers whose code runs on your pages.
What’s the risk from now on? Risks. Add a risk such as “Code from a supplier runs on our payment pages”. Give it an owner, a score and a review date.
What will we change? Controls and Actions. Link controls such as hosted payment forms and limits on which scripts can run. Map them to the Blueprint requirements above, and test them. Give each change an owner and a due date.
Does leadership know? Reports. Share a PDF report or slide deck on the incident and the plan.
Every step is kept in a history that shows who did what and when, with the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you handled it, the answer is already written down.
Is RiskWitness affected?
No. RiskWitness doesn’t use Optimizely. Both the RiskWitness app and this website only run code served from their own address. Payments are taken on Stripe’s own checkout pages.
Sources
- Web Experimentation Security Incident, Optimizely status page, 17 November 2026
- World’s Largest Brands Infected With Malware Via Optimizely, Report URI, 16 November 2026, updated 17 November 2026
- Poisoned Scripts on BBC, Zoom and Other Major Websites Linked to iPhone Exploit Loaders, Hudson Rock (InfoStealers), 16 November 2026
- Optimizely Vulnerability Exploited to Serve Malware on Major Websites, SecurityWeek, 17 November 2026
- Optimizely Attack Hits Zoom, BBC, CNN With Skimmer, iOS Kits, SOCRadar, 17 November 2026
