🔍 Read the full analysis: The 178-Site Optimizely Malware Incident: An AI User’s Safety Checklist on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Report URI says malicious JavaScript was served to visitors of 178 organizations through Optimizely Web on Nov. 16, 2026. Optimizely confirmed an unauthorized party exploited a vulnerability in its Experimentation signup flow; the company says it fixed the flaw, removed injected code and notified affected customers. The extent of any data theft or device compromise has not been established.
Malicious JavaScript was served to visitors of 178 organizations through Optimizely’s web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation service to add code to some customer projects, making the incident a third-party supply-chain exposure rather than evidence that each affected organization was hacked directly.
Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188. It identified 178 organizations associated with affected sites and said the true total could 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. A listed organization does not mean all of its pages or services were affected.
Optimizely’s status page said the attacker exploited a vulnerability and that the company had fixed the flaw and removed injected code from affected projects. The company told BleepingComputer that the weakness was in the Experimentation account signup flow. It also said it had ended active sessions, revoked tokens, reset access for affected accounts and notified customers it considered affected.
Report URI observed the first injection at 04:21 UTC on Nov. 16 and said the infected Optimizely files had been cleaned by 23:11 UTC, an observed period of about 19 hours. According to Report URI, the attacker inserted code into the “Project JavaScript” field in customer projects; the rest of each snippet remained unchanged. The affected sites continued to load the script from Optimizely, a supplier they had chosen to trust.
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
How a Trusted Script Reached Visitors
The incident shows how a compromise at a shared web-service provider can expose visitors across many separate organizations. Sites using Optimizely loaded a script for experiments, and the injected code could run in visitors’ browsers without each organization having to host the malware itself. That creates a risk for both businesses and people using their sites, even when the organizations’ own systems were not shown to have been breached.
Report URI’s review also points to a gap in protections on the affected sites: it found that 24 of 159 organizations had security policies that blocked the code, while 68 had no policy at all. This is a count from the researcher’s review, not a measure of confirmed theft or compromise. Content Security Policy can limit which scripts a site allows, but the figures do not establish whether a policy would have blocked every part of this incident.
For users, the potential consequences depend on the page, device and actions taken while the code was active. Report URI says the payload sought to replace cryptocurrency addresses, capture payment-card details entered into a site’s own form fields, and collect cookies and screenshots. Those behaviors describe what the code attempted; they do not establish that a particular visitor’s information was captured or misused.
Popular right now

Vitamix Nano Personal Blender with SmoothiePilot Technology, Black

TCL 55-Inch R7D Series QLED 4K UHD HDR Roku Smart TV (55R7D, 2026)

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
As an affiliate, we earn on qualifying purchases.
How Optimizely’s Snippets Were Altered
Optimizely Web delivers a JavaScript snippet that customer websites use to run experiments on page designs. Each project can include optional Project JavaScript, custom code that runs on pages where the snippet is installed. Report URI says the attacker changed that field in customer projects while leaving the remainder of each snippet intact. It also said this was not a content delivery network cache-poisoning attack.
Report URI says the payload was rebuilt 26 times during Nov. 16, and that visitors received the same script, with its actions varying according to device and behavior. Its account describes cryptocurrency address substitution, card-field monitoring and collection of cookies and screenshots. It also reports that the code could direct older iPhones and iPads toward the Coruna and DarkSword exploit kits. Hudson Rock, which analyzed the mobile-device stage, cautioned that its findings were “delivery observations, not demonstrated iPhone compromises.”
The reported list spans sectors, including 32 banking and finance organizations, 23 technology and software organizations, and 20 retailers. It includes major brands and smaller subdomains. Hudson Rock warned that an affected subdomain does not prove exposure across an organization’s full website, products, customer base or checkout system. Report URI also described an earlier wave beginning Nov. 13 involving scripts from Kissmetrics, StorifyMe and Minute Media; 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 update posted Nov. 17
Exposure and Intrusion Path Still Unknown
The available accounts do not establish how many visitors saw the malicious code, whether any card details, cookies or screenshots were successfully stolen, or whether any iPhone or iPad was compromised. The reported payload behaviors are not proof that each function succeeded. Nor does an organization’s presence on the list show that its entire site or all of its customers were exposed.
Optimizely has identified a flaw in the Experimentation account signup flow but has not publicly explained the vulnerability’s code-level mechanics or how it enabled changes to many unrelated customer projects. Report URI says it cannot determine how the attacker obtained that write access. Hudson Rock also says the route by which the same actor’s injector appeared in scripts from three other providers remains unresolved. The full scope of those earlier incidents is not specified in the supplied reporting.
Customer Reviews and Security Checks
Optimizely says it has removed the injected code, fixed the vulnerability, ended active sessions, revoked tokens, reset access for affected accounts and contacted affected customers. Organizations using the service will need to review Optimizely project activity, their own site and security logs, and any customer data that may have been handled during the exposure window. The supplied information does not give a timeline for a public technical postmortem or a final accounting of affected visitors.
People concerned about the incident can update supported devices and consult guidance from their service providers. Report URI advises iPhone users to install iOS 18.7.3 or later, or iOS 26.3 or later, versions it says had been released months before the incident. That recommendation is a precaution; it does not mean an individual device was infected. Users should also treat unexpected wallet-address changes and unusual account activity as potential warning signs and contact the relevant provider if they suspect information was exposed.
Key Questions
What happened in the Optimizely incident?
Report URI says an attacker used Optimizely Web to serve malicious JavaScript to visitors of sites associated with 178 organizations on Nov. 16, 2026. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects.
Were all pages and customers of the listed organizations affected?
That has not been established. Some entries were individual subdomains, and Hudson Rock cautioned that an affected subdomain does not prove exposure across an organization’s entire site, products or customer base.
Does the report confirm that visitors’ data was stolen?
No. Report URI describes code that attempted to collect information such as card details entered into site-owned forms, cookies and screenshots. The available reporting does not confirm how many visitors were affected or whether data was successfully stolen.
Did the incident confirm iPhones were compromised?
No. Hudson Rock said its findings showed exploit-kit delivery observations, not demonstrated iPhone compromises. Report URI advised users to update supported iPhones and iPads as a precaution.
What has Optimizely done so far?
Optimizely says it fixed the vulnerability, removed the injected code from affected projects, ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers. Its public account does not explain the technical mechanics of the flaw or the full impact on visitors.
Source: ThorstenMeyerAI.com
