Cybersecurity Research

Optimizely Flaw Let Attacker Slip Malicious Code Into Snippets on Major Websites

Sophos · 17 Nov 2026 · updated 18 Nov 2026
Key Takeaway If your website uses Optimizely Web Experimentation, review your projects for unexpected code added on 16 November and follow the vendor's incident page.

Optimizely has reported that an attacker exploited a vulnerability in its Web Experimentation product and added malicious JavaScript to some customer projects. The company disclosed the incident on November 17, 2026, and says the injection took place on November 16. According to Unit 42, which has nicknamed the campaign OPTIMJACK, the code was placed in the custom Project JavaScript field of customer accounts.

Third-party reporting cited by Sophos indicates the code was placed into snippets belonging to 178 organisations, including CNN, the BBC and Zoom. Unit 42 gives a similar figure, saying the code reached visitors of at least 178 organizations, and describes them as well-known media, technology and financial services brands. The two reports agree on the number, though Unit 42 frames it as a minimum. Web Experimentation tools are used to test different versions of a web page, and they work by loading a snippet of code on the customer's own website. That is why a problem on the vendor side can end up running on a customer's site.

According to Unit 42, the tampered snippets were delivered from Optimizely's own legitimate content delivery network (CDN), under the vendor's own security certificate. The affected organizations unknowingly served the code to their visitors, and nothing about the delivery looked unusual. Unit 42 also says Optimizely patched the flaw, removed the injected code and secured affected accounts early on November 17. Optimizely states that it has fixed the vulnerability and removed the malicious code.

Unit 42 says the code took three actions once loaded in a visitor's browser, but the material we have does not detail them. It does note that swapping valid cryptocurrency wallet addresses on a page is a quick and persistent way to redirect payments to an attacker. Neither report explains how the flaw worked or how many visitors were affected, so those details remain unknown.

Sophos X-Ops advises organisations that use Optimizely Web Experimentation to check their projects for code injected on November 16, and to monitor the Optimizely incident page for the latest guidance. SophosLabs says it continues to watch for activity linked to this threat and will release detections and protections as they become available. Unit 42 recommends strict segmentation so a compromised vendor script can never touch sensitive user inputs, and says affected sites still need to carry out cleanup steps even though the flaw is patched.

Why it matters

A trusted third-party script can be changed without anyone touching your own website or servers, and here it was served from the vendor's own CDN under its own certificate, so it looked legitimate. Unit 42 argues that any third-party script on your page has the same privileges as your own developers, so vendor snippets deserve the same scrutiny as your own code. A vendor fix does not undo what already ran in visitors' browsers.

What to do

  • Check your Optimizely Web Experimentation projects, including the custom Project JavaScript field, for code injected on November 16.
  • Monitor the Optimizely incident page for the latest guidance.
  • Segment third-party scripts so they cannot access sensitive user inputs such as payment or login fields.
  • Complete cleanup steps on any affected site even though the flaw has been patched.
Optimizely supply chain JavaScript injection web security third-party risk
Also reported by Unit 42
Answering to more than one framework? Run them as one security and AI governance programme ->

Summarised by CISO AI from Sophos, with the same story also reported by Unit 42, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.