Optimizely Attack Briefly Affects UK Telecom Websites

Hackers used the Optimizely Web experimentation platform in a recent attack to deliver malicious JavaScript to website visitors, and Virgin Media and O2, alongside TalkTalk, appear to have been affected briefly. Report-URI linked the incident to 178 organisations worldwide, which loaded scripts onto their websites from the trusted third-party service and so brought the harmful code into visitors’ browsers.

How Visitors Received the Malicious JavaScript

Website operators use the Optimizely Web experimentation platform to try out changes on their pages, and according to Report-URI, customers load a small file of JavaScript called a snippet. JavaScript runs inside a visitor’s browser, so changing that file can also change what happens when a person opens a page on a website.

Optimizely sends these files through its Content Delivery Network (CDN), which distributes content to visitors, and a snippet usually holds the customer’s experiments as well as Optimizely code. Customers can also write code in the dashboard using an optional field, Project JavaScript (projectJS), and that code runs on all pages that use the project. During this incident, an attacker got into the Optimizely setup and put malicious code into the files that were being sent out to people visiting the affected websites.

Optimizely said a party without authorisation had taken advantage of a vulnerability in Experimentation, which allowed that party to put malicious JavaScript into projects belonging to some customers. Optimizely has not given any further explanation of how the attacker got into its setup, beyond the details it provided in that statement about the vulnerability.

Malicious Code Came Through Trusted Scripts

Report-URI said the malicious code could replace someone’s cryptocurrency wallet address with an address belonging to the attacker, and it could also take payment card details, browser cookies and screenshots. Cookies store information inside a browser, which websites use to remember details about a visitor or the session that person has open on the site.

The malicious code could carry out several attacks:

  • Swap cryptocurrency wallet addresses for the attacker’s
  • Skim payment cards from website visitors
  • Steal browser cookies and capture screenshots
  • Deliver Coruna and DarkSword exploits on iPhones and iPads

For people using iPhones or iPads, the malicious code delivered Coruna and DarkSword, two iOS exploit kits made up of code that takes advantage of weaknesses in those devices’ operating system. Report-URI described what the code could do, while the account did not give a figure for how many visitors had information stolen or how many devices were affected.

The operators’ own systems were not directly compromised, according to the account, and the problem came from a trusted outside service that was loaded through their official websites. That outside service was taken over briefly, so pages on otherwise legitimate websites could send malicious code to the people opening them, without the operators themselves being directly compromised. For people responsible for network security, the exposure described in the account involved code supplied through an outside service and then loaded as part of a visit to an official website.

Operators Assess Incident After Code Is Removed

Report-URI found that the number of infected snippets had dropped sharply on 16th Nov 2026, with 169 recorded at 20:56 UTC and only 1 still infected at 21:52 UTC. There were initially 188 infected snippets across 178 organisations during the incident, according to Report-URI.

The last snippet that Report-URI found still infected was on TalkTalk’s website, although TalkTalk has since resolved the issue, while Optimizely says the vulnerability is now fixed. Optimizely also says it has removed the malicious code added to affected projects, taken action to secure the affected accounts and introduced extra protections to stop unauthorised code reaching visitors.

A Virgin Media O2 spokesperson said its teams were looking into the report to establish what had happened, while TalkTalk also provided a statement about its response to the incident. In the update posted at 7:26am on 18th Nov 2026, a TalkTalk spokesperson said the affected code was now removed and it was working with Optimizely as it assessed the incident.

Subscribe to our weekly news digest.

Join now and become a part of our fast-growing community.

Invalid Email Address
Thanks for Subscribing!
We'll be sending you our best soon!
Something went wrong, please try again later