🔍 Read the full analysis: Optimizely Malware Hit 178 Major Sites: A Checklist For AI Users on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Report URI says malicious JavaScript was served to visitors on Nov. 16 through Optimizely Web scripts associated with 178 organisations. Optimizely says an attacker exploited a vulnerability, removed the injected code and notified affected customers; the entry point and any resulting data theft remain unclear.
Malicious JavaScript reached visitors to sites associated with 178 organisations on Nov. 16 through scripts supplied by Optimizely’s web experimentation platform, according to security researcher Scott Helme of Report URI. Optimizely confirmed an unauthorized party exploited a vulnerability to add code to some customer projects, creating a supply-chain incident that could affect site visitors even though their own organisations were not hacked.
Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188. Its report attributes the figure of 178 organisations to sites where the code was served; the researcher cautioned that the actual number could be higher. BleepingComputer separately reported confirming that the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A company or brand appearing on the list does not mean its entire website or all its customers were exposed.
According to Report URI, the first observed injection appeared at 04:21 UTC on Nov. 16, and infected Optimizely files had been cleaned by 23:11 UTC. That is roughly 19 hours. Optimizely’s status notice, posted at 01:02 UTC on Nov. 17, said it had fixed the vulnerability and removed the injected code from affected projects. The company also told BleepingComputer it had ended active sessions, revoked tokens, reset access for affected accounts and notified customers.
The JavaScript’s reported functions included replacing cryptocurrency wallet addresses on pages or in the clipboard, monitoring card details entered into a site’s own forms, and collecting cookies and screenshots. Report URI said the code also directed some iPhones and iPads toward the Coruna and DarkSword exploit kits. These are researchers’ findings about the script’s behavior, not confirmation that every targeted action succeeded or that visitors’ devices or accounts were compromised.
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
Third-Party Scripts Can Reach Many Sites
The incident shows how a weakness in a supplier’s platform can put visitors to many unrelated websites at risk. Optimizely’s experimentation snippets run as part of customer sites, so code altered within customer projects could be delivered from a source those sites already trusted. That can make malicious activity difficult for visitors to distinguish from normal page functions.
The reported payload targeted several kinds of information and behavior, but the exposure depended on a visitor’s device and actions. Report URI said payment details entered into a site’s own form fields could be observed, while card details entered inside hosted payment frames such as Stripe or Adyen were outside the script’s reach. It also found that only 24 of 159 organisations it checked had security policies that blocked the code, while 68 had no policy. Those figures describe the organisations examined, not every affected site.
For readers, the practical distinction is between a script being delivered and a confirmed theft or compromise. The source material does not establish that every visitor was affected, that every listed organisation’s checkout or entire site was exposed, or that data was successfully taken. The incident nevertheless gives businesses a reason to review third-party scripts and the protections that restrict what page code can do.
Products Worth Considering

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)

Bose QuietComfort Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones, Eucalyptus Green

Bose QuietComfort Wireless Noise-Cancelling Headphones, Sandstone
As an affiliate, we earn on qualifying purchases.
How the Optimizely Snippet Was Changed
Optimizely Web lets customers run page experiments through a small JavaScript snippet loaded by their websites. Report URI says each customer project can include an optional Project JavaScript field containing custom code that runs on pages where the snippet is installed. The researcher’s analysis found that the attacker added code to this field while leaving the rest of the snippet intact. That meant affected sites continued loading a file from an Optimizely address they already trusted.
Optimizely said the vulnerability was in the Experimentation account signup flow. Its public notice and statement to BleepingComputer did not explain how that flaw let an attacker write to multiple unrelated customer projects. Report URI said it could not determine how the attacker gained that access; Hudson Rock likewise said Optimizely’s disclosure did not explain the bug’s code-level mechanics.
Report URI said the payload was rebuilt 26 times during the day and that visitors received the same script, with behavior varying according to the device and activity on the page. It also reported an earlier wave beginning Nov. 13 involving the same actor’s injector in scripts from Kissmetrics, StorifyMe and Minute Media. Hudson Rock said how the code entered those services remained unresolved. Report URI said the Optimizely incident was not a CDN cache-poisoning attack.
“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
The Reach and Impact Remain Unclear
It is not yet clear how the signup-flow vulnerability enabled writes to multiple customer projects, or whether the available figures capture every affected site. Report URI said its count came from checking snippets and that the real total could be higher. The published list covers organisations and particular sites or subdomains; Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s whole website, product range, customer base or checkout system.
The source material also does not confirm how many visitors had information captured, whether any stolen information was used, or whether any iPhones or iPads were successfully exploited. Hudson Rock described its iPhone findings as observations of delivery rather than demonstrated compromises. The reported card-skimming behavior was limited to details entered into a site’s own form fields, according to Report URI, and did not reach hosted payment iframes it examined.
Optimizely says it removed the injected code and took steps to reset access. The available statements do not detail the full investigation, the number of confirmed affected customers, or the complete timeline for customer notification. Those details may emerge through further company updates or independent analysis.
Customer Reviews and Fix Verification
Optimizely says the vulnerability has been fixed, the injected code removed, access reset for affected accounts and customers notified. The next public signals to watch for are further details from the company about how the signup-flow flaw worked, how many projects were affected, and whether its review found evidence of successful data theft or device compromise.
Organisations that use Optimizely can review the company’s notices and check their own projects and site scripts for unexpected changes. They can also review their browser security policies, including whether those policies restrict unapproved scripts. Visitors concerned about the reported iPhone targeting can follow Report URI’s advice to use iOS 18.7.3 or later, or iOS 26.3 or later; the source says both versions had been released months earlier. These steps do not establish whether a particular visitor was affected, and the investigation’s final scope remains unknown.
Key Questions
What happened in the Optimizely incident?
Report URI says malicious JavaScript was delivered to visitors through Optimizely Web scripts associated with 178 organisations on Nov. 16. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects.
Were all 178 organisations fully compromised?
No. The figure refers to organisations associated with affected scripts, not proof that every page, service or customer account was exposed. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s entire website or business.
What did the malicious code attempt to do?
Report URI said it could replace cryptocurrency wallet addresses, monitor payment-card details entered into sites’ own forms, and collect cookies and screenshots. It also reported that some iPhones and iPads were directed toward exploit kits, but that does not confirm successful device compromises.
Has Optimizely removed the code and fixed the flaw?
Optimizely said it fixed the vulnerability and removed injected code from affected projects. It also told BleepingComputer that it ended active sessions, revoked tokens, reset access for affected accounts and notified customers.
What remains unknown?
The public statements do not explain how the signup-flow flaw enabled access to unrelated customer projects. The number of visitors affected, whether information was successfully stolen, and whether any devices were compromised have not been established in the supplied reporting.
Source: ThorstenMeyerAI.com
