🔍 Read the full analysis: AI User Safety: What To Check After Malware Spread Via Optimizely on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation signup flow to add malicious JavaScript to some customer projects. Report URI says the code reached visitors to sites associated with 178 organisations, with a window of about 19 hours before infected files were cleaned. The scope of possible data theft and whether any devices or accounts were compromised have not been established.
Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation platform to insert malicious JavaScript into some customer projects, exposing visitors to affected pages to code designed to steal information and redirect devices. Security researcher Scott Helme of Report URI says the code was served through snippets associated with 178 organisations on November 16; the company says it fixed the vulnerability and removed injected code from affected projects.
Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188. It identified 178 organisations whose visitors received the script, while warning that the actual number may be higher. BleepingComputer separately reported that urlscan.io scans showed the script loaded, or attempted to load, on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listing does not mean every page or service operated by an organisation was affected.
According to Report URI’s analysis, the script could replace cryptocurrency wallet addresses in page text, form fields and the clipboard; monitor card details entered into a website’s own form fields; and collect cookies or screenshots. It also attempted to direct some iPhones and iPads to the Coruna and DarkSword exploit kits. Report URI says payment details entered into hosted payment iframes, including those used by Stripe or Adyen, were outside the script’s reach. These are reported capabilities, not evidence that every action succeeded or that every visitor’s data was taken.
Report URI first observed an Optimizely injection at 04:21 UTC on November 16 and says all infected Optimizely files had been cleaned by 23:11 UTC, about 19 hours later. Optimizely told BleepingComputer it had notified affected customers, ended active sessions, revoked tokens and reset access for affected user accounts. Its status-page update, posted at 01:02 UTC on November 17, said the vulnerability was fixed and the injected code removed.
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
What Visitors and Site Owners Face
The incident shows how a compromise at a trusted software supplier can expose people who never visited or interacted with the supplier itself. Affected sites loaded Optimizely’s JavaScript snippet as part of their normal operation, so the malicious code could arrive through a source those websites had already permitted. That makes the event a third-party supply-chain incident, rather than evidence that each named organisation’s own website was separately hacked.
For visitors, the possible consequences depend on the device, page and activity during exposure. Someone who copied a cryptocurrency address while an affected tab was open could have had it replaced, according to Report URI. Someone who entered payment details into a site’s own form may have faced a different risk from a person using a hosted payment iframe. The source material does not establish how many visitors entered sensitive details, whether the data was successfully transmitted, or whether any accounts or devices were compromised.
For organisations, the event highlights the reach of scripts that run across many pages and the value of limiting and monitoring third-party code. Report URI says that, among 159 affected organisations it checked, only 24 blocked the code through their security policies, while 68 had no policy. That finding points to uneven protections in that sample; it does not establish that a policy would have prevented every effect or that the remaining organisations had no other safeguards.
Popular right now

Bose QuietComfort Wireless Noise-Cancelling Headphones, Moonlight Grey

De'Longhi Rivelia Automatic Espresso Machine with Milk Frother

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
As an affiliate, we earn on qualifying purchases.
How the Optimizely Snippets Were Altered
Optimizely Web experimentation works by having a customer site load a small JavaScript file, or snippet, from the platform. The snippet carries experiments for that customer and can include a field called Project JavaScript, where a customer’s custom code runs on pages using the snippet. Report URI says the attacker inserted code into that field in customer projects while leaving the rest of each snippet unchanged. The files continued to come from Optimizely, an address the affected sites already trusted.
Report URI says this was not a CDN cache-poisoning attack. Optimizely’s own websites also carried the code, according to the researcher. The company told BleepingComputer that the vulnerability was in the Experimentation account signup flow, but neither its status-page notice nor its comment to the publication described the flaw’s technical mechanics or explained how it enabled access to unrelated customer projects.
Report URI also describes an earlier wave beginning November 13, when the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media. Those sites are separate from the 178-organisation Optimizely list. Hudson Rock reported a similar pattern and said how the code entered those three services remained unresolved.
“An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.”
— Optimizely, in its November 17 status-page update
The Extent of Data Exposure
The available reports do not establish how many people were affected, whether the code successfully stole payment details, cookies or screenshots, or whether any iPhone or iPad was compromised. Hudson Rock explicitly distinguishes observing exploit-kit delivery from demonstrating a successful device compromise. Report URI’s analysis describes what the code attempted to do, but attempts should not be treated as confirmed data theft.
It also remains unclear exactly how the signup-flow vulnerability gave the attacker write access to many customer projects, how many projects were altered beyond those observed, and whether information taken by the code was used. Report URI says its scan found 188 affected snippets among 1,611 checked and that the real number may be higher. The 178 organisations identified are not proof that every page, product, checkout flow or customer account at those organisations was exposed.
Report URI advises iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. The source material says both versions were released months before this incident. This is a precaution based on the reported exploit-kit delivery; it is not evidence that every visitor needs a particular account reset or that an unpatched device was compromised.
Customer Notices and Security Review
Optimizely says it has fixed the vulnerability, removed injected code from affected projects, notified affected customers and revoked sessions and tokens while resetting access for affected accounts. Customers that use Optimizely should follow the company’s notices and their own incident-response procedures, including reviewing relevant access and website records for the exposure window. The source material does not specify a date for a fuller technical report.
Visitors who used an affected page during the reported period can take proportionate precautions: update Apple devices to the versions advised by Report URI, check whether copied wallet addresses were changed before sending funds, and contact a card issuer if they entered card details into a site’s own form and are concerned. These steps do not confirm that information was stolen. Further detail from Optimizely and independent investigators may clarify how the flaw worked, how many projects were affected and whether any data or devices were successfully compromised.
Key Questions
What happened in the Optimizely incident?
Optimizely said an unauthorized party exploited a vulnerability in its Experimentation account signup flow to add malicious JavaScript to some customer projects. Report URI says the code was served through snippets associated with 178 organisations on November 16, 2026.
Does the list of 178 organisations mean all their websites were affected?
No. The list identifies organisations associated with affected snippets, not exposure across every page or service they operate. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s full website, customer base or checkout system.
Was personal or payment information definitely stolen?
That has not been established in the available reports. Report URI says the script attempted to capture certain information, including card details entered into a site’s own form fields, but its analysis does not confirm how many people entered data or whether theft succeeded.
Were iPhones confirmed compromised?
No confirmed number of compromised iPhones or iPads is provided. Report URI observed attempts to send some Apple devices to exploit kits, while Hudson Rock described its findings as delivery observations rather than demonstrated device compromises.
What should visitors do now?
Report URI advises updating iPhones and iPads to iOS 18.7.3 or later, or iOS 26.3 or later. Visitors concerned about card details entered into a site’s own form can contact their card issuer, and anyone who copied a cryptocurrency address while an affected tab was open can verify the destination before sending funds. These are precautions, not confirmation that a user was affected.
Source: ThorstenMeyerAI.com
