🔍 Read the full analysis: Malware Reached 178 Major Websites Via Optimizely—Could AI Users Be Affected? on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Report URI says visitors to 178 organisations received malicious JavaScript through Optimizely Experimentation on November 16, 2026. Optimizely says it fixed a vulnerability and removed the code, but the technical route to access across customer projects remains unexplained. Researchers documented attempted data theft and iPhone exploit-kit delivery; they have not established that devices were compromised.
Malicious JavaScript reached visitors to 178 organisations through the Optimizely Experimentation platform on November 16, according to security researcher Scott Helme and Report URI. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to customer projects; the incident matters because visitors’ browsers can load a supplier’s script even when the customer’s own site has not been hacked.
Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188 snippets associated with 178 organisations. It cautioned that the actual number may be higher. BleepingComputer separately reported that urlscan.io scans showed the script loading or attempting to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. The published list also included sites associated with HSBC, IKEA, Equifax, Ledger, Peacock, Air France-KLM and UNICEF USA. A listed organisation does not mean its entire website or every service was affected.
According to Report URI, the attacker inserted code into the optional Project JavaScript field in customer projects. The rest of each snippet was unchanged and continued to be served from Optimizely, an address the affected sites already trusted. Report URI said the first injection it observed was at 04:21 UTC on November 16; it reported that infected files had been cleaned by 23:11 UTC, a window of about 19 hours. Optimizely said on November 17 that it had fixed the vulnerability and removed the code from affected projects.
Report URI’s analysis says the payload was rebuilt 26 times during the day and that its behaviour depended on the visitor’s device and activity. It attempted to replace cryptocurrency wallet addresses in page text, form fields and clipboard activity; collect payment-card details entered into sites’ own forms; and capture cookies and screenshots. The researcher said card information entered into hosted payment iframes, such as those used by Stripe or Adyen, was outside the script’s reach. It also attempted to direct some iPhones and iPads to the Coruna and DarkSword exploit kits.
Optimizely script attack · Nov 13 – Nov 17, 2026
How one trusted script carried malware to 178 websites
The sites were not hacked themselves. The code arrived inside a file they loaded on purpose.
The route (schematic)
Whether any iPhone was compromised has not been shown.
Timeline (UTC)
- Nov 13Earlier wave through three other providers’ scriptsKissmetrics, StorifyMe, Minute Media
- Nov 16 04:21First Optimizely injection seen
- 08:28Address-swapping payload first seen on a site
- 13:43Card skimmer added
- 17:13iPhone exploit delivery widened
- 19:24Report URI sweep: 186 of 1,611 snippets infected
- 21:52Only 1 of 188 infected snippets left
- 23:11All infected Optimizely files cleaned
- Nov 17 01:02Optimizely confirms the incident on its status page
Sources: Report URI (Scott Helme), Nov 16, 2026, timeline and update of Nov 17; Optimizely status page, Nov 17, 2026; Hudson Rock (Infostealers.com), Nov 16–17, 2026. The route is a schematic.
Graphic: Powered by Thorsten Meyer AI
Why Trusted Site Scripts Matter
The incident illustrates how a compromise of a third-party web service can expose visitors across many unrelated organisations. A site can load a supplier’s code by design, so a change to that code may reach users without an attacker breaking into each customer’s own infrastructure. The script was delivered from a source the affected sites already trusted, according to Report URI.
For readers, the potential exposure depends on the page visited, the device used and actions taken while the code was active. Report URI described attempts to capture certain information and redirect vulnerable Apple devices, but those observations do not establish that a particular person’s card, account or phone was compromised. Hudson Rock said its iPhone findings were delivery observations, not demonstrated compromises.
The researchers also identified gaps in site-level protections. Report URI said just 24 of 159 organisations it assessed blocked the code through their security policies, while 68 had no policy. Those figures concern the organisations and policies checked; they are not a measure of confirmed infections or stolen data.
Popular right now

Shark AI Ultra Robot Vacuum with Matrix Clean and Self-Empty Base

Roborock Q10 S5+ Robot Vacuum and Mop with Self-Emptying Station

KitchenAid Commercial Series 8-Quart Bowl-Lift Stand Mixer, White
As an affiliate, we earn on qualifying purchases.
How Optimizely Code Reached Sites
Optimizely Web Experimentation lets customers test page variations using a small JavaScript snippet loaded by their sites. Customers can add custom code through a Project JavaScript field, which can run across pages using that project. Report URI says the attacker wrote malicious code into this field in customer projects while leaving the surrounding snippet intact. It said this was not a content delivery network cache-poisoning attack.
Optimizely’s status-page notice, posted at 01:02 UTC on November 17, said an unauthorized party exploited a vulnerability in Experimentation to add malicious JavaScript to some customer projects. The company told BleepingComputer that the flaw was in the Experimentation account signup flow, and said it had notified affected customers. It also said it ended active sessions, revoked tokens and reset access for affected user accounts.
Report URI described an earlier wave beginning November 13 involving the same actor’s injector in scripts from Kissmetrics, StorifyMe and Minute Media, on sites not included in the 178-organisation list. Hudson Rock also reported that pattern and said how the code entered those services remains unresolved.
“An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.”
— Optimizely, in its status-page notice
What Investigators Have Not Established
The public accounts do not explain how the signup-flow vulnerability enabled access to multiple unrelated customer projects, or the precise code-level mechanics. Optimizely has said it fixed the flaw and took account-security measures, but has not publicly detailed those mechanics in the source material. Report URI and Hudson Rock have also said the route by which the earlier injector appeared in scripts from three other providers is unresolved.
It is also unclear how many visitors encountered the code, whether any information was successfully taken, or whether any device was compromised. Report URI’s scan count and organisation list describe observed snippets and affected project associations, not confirmed victims. The available findings do not show that every page, checkout flow or customer account belonging to a listed organisation was exposed. Hudson Rock specifically cautioned that an affected subdomain alone does not establish exposure across an organisation’s wider services.
Customer Notifications and Security Updates
Optimizely says it has notified affected customers, removed injected code and fixed the vulnerability. It also reported ending active sessions, revoking tokens and resetting access for affected accounts. Customers using the service will need to review any further notices from Optimizely and assess their own project configurations and logs; the source material does not specify a public schedule for additional technical findings.
Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. Its advice concerns reducing exposure to the exploit kits observed in the campaign; it is not evidence that a particular device was infected. Further clarity will depend on Optimizely’s technical account of the vulnerability and on any subsequent findings about data theft or successful device compromises.
Key Questions
Was Optimizely itself hacked?
Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation product and added malicious JavaScript to some customer projects. The company said the flaw was in the account signup flow. The available statements do not give a full technical explanation of how the attacker gained access to those projects.
Were all pages of the named organisations affected?
No. The list identifies organisations associated with observed affected snippets, but it does not establish that every page or service was exposed. Hudson Rock cautioned that an affected subdomain does not prove exposure across an organisation’s entire website, product, customer base or checkout system.
Did the malicious code steal card details or compromise iPhones?
Report URI said the code attempted to capture card details entered into sites’ own forms and direct some Apple devices to exploit kits. The reporting provided does not establish how many details, if any, were stolen or whether any iPhones or iPads were successfully compromised.
What should iPhone and iPad users do?
Report URI advised users to update to iOS 18.7.3 or later, or iOS 26.3 or later. That is a security recommendation based on the exploit-kit delivery observed; it does not mean every visitor or device was affected.
How long was the Optimizely code observed?
Report URI said it first observed an injection at 04:21 UTC on November 16 and that infected Optimizely files had been cleaned by 23:11 UTC. That is about 19 hours, based on the researcher’s observations.
Source: ThorstenMeyerAI.com
