🔍 Read the full analysis: Optimizely Malware And 178 Major Websites: What AI Users Should Know 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 delivered through Optimizely Web was present in snippets associated with 178 organizations on November 16, 2026. Optimizely says an attacker exploited a vulnerability in its Experimentation signup flow, removed the injected code and notified affected customers; the full attack mechanics and any resulting compromise remain unclear.
Malicious JavaScript delivered through Optimizely Web appeared in snippets associated with 178 organizations on November 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 customer projects; the code attempted several forms of data theft and device targeting, but the available reporting does not establish how many visitors were affected or whether their devices were compromised.
Report URI says it checked 1,611 Optimizely snippets and found malicious code in 188 of them, a count that does not directly equal the number of organizations. The researcher said the actual total could be higher. BleepingComputer separately reported that scans through urlscan.io showed the script loading or attempting to load on sites including Zoom, the BBC, CNN, GitLab, KLM and Salesforce. A name on the list does not mean every page or service run by that organization was affected.
According to Report URI’s analysis, the payload attempted to replace cryptocurrency wallet addresses on web pages and in clipboard contents, collect payment-card details entered into sites’ own forms, and capture cookies and screenshots. The report also describes attempts to direct some iPhones and iPads to the Coruna and DarkSword exploit kits. Hudson Rock, which analyzed the mobile-device stage, cautioned that its findings showed delivery observations, not demonstrated iPhone compromises. Report URI says card details in hosted payment frames such as Stripe or Adyen were outside the script’s reach.
Report URI observed the first Optimizely injection at 04:21 UTC on November 16 and says infected files had been cleaned by 23:11 UTC, a period of about 19 hours. Optimizely’s November 17 status update said it had fixed the vulnerability and removed 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 it considered affected.
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 Exposed Visitors
The incident shows how an attack on a third-party web service can reach visitors through code that customer sites have deliberately included. Optimizely Web snippets run as part of the page experience, so the malicious JavaScript could be delivered from a source already trusted by the affected sites. Report URI says the attacker inserted code into customer projects’ optional Project JavaScript field, while the rest of each snippet remained unchanged. The researcher said the incident was not a CDN cache-poisoning attack.
For visitors, the risk depended on the page, device and activity. Report URI’s analysis describes attempts to alter wallet addresses, collect card details in certain forms, and capture browsing information; it does not show that every listed organization’s customers entered sensitive information or that every attempted action succeeded. For businesses, the event underscores the exposure created when an external platform can run custom scripts across customer pages. Report URI found that only 24 of 159 assessed organizations blocked the code with their security policies, while 68 had no policy, according to its review. Those figures describe the assessed sites, not all 178 organizations.
Products Worth Considering

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

LG 27GR83Q-B 27-inch Ultragear QHD IPS Gaming Monitor

Jackery Explorer 300 Portable Power Station, 292Wh
As an affiliate, we earn on qualifying purchases.
How the Optimizely Snippets Were Altered
Optimizely Web uses a small JavaScript snippet loaded by a customer website. The snippet can carry experiments and optional Project JavaScript: custom code that a customer can configure to run on pages. Report URI says the attacker wrote malicious code into that field in customer projects, while the snippets continued to be served from Optimizely addresses the sites already trusted.
Optimizely’s public status update, posted at 01:02 UTC on November 17, said the vulnerability had been fixed and injected code removed. The company told BleepingComputer that the flaw was in the Experimentation account signup flow. Report URI says the payload was rebuilt 26 times during the day. The report also describes an earlier wave, beginning November 13, in which the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media on sites outside the 178-organization list; 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
Exposure Scope and Attack Mechanics
It is not yet clear how the signup-flow vulnerability enabled access to multiple unrelated customer projects, how many visitors received the payload, or whether any attempted theft or device exploitation succeeded. Optimizely has not publicly explained the vulnerability’s code-level mechanics in the information cited here. Its notification to affected customers does not establish what each customer found in its own investigation.
Report URI’s 178 organizations are a list of affected organizations or sites, not evidence that each organization’s entire website, checkout system or customer base was exposed. Hudson Rock specifically cautioned that an affected subdomain does not establish exposure across an organization’s broader services. The report also says the earlier activity involving three other providers remains unresolved. No complete public accounting of confirmed losses or compromised devices is provided in the source material.
Customer Checks and Security Updates
Optimizely says it has fixed the vulnerability, removed injected code, revoked tokens and reset access for affected accounts, and notified affected customers. The company and customers can provide further detail on the signup-flow flaw, which projects were accessed, and whether investigations found successful data theft or device compromise. Until then, the scale of confirmed harm remains unknown.
Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later, which it said Apple had released months earlier. Users and organizations can check for available software updates and follow notices from Apple, Optimizely and their affected service providers. Report URI’s assessment of site security policies also points to a practical follow-up for businesses: review which third-party scripts can run, and whether site policies can block unauthorized code.
Key Questions
What happened in the Optimizely incident?
Report URI says malicious JavaScript was served through Optimizely Web snippets associated with 178 organizations on November 16, 2026. Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation service to add code to some customer projects.
Were all pages on the listed websites affected?
No such conclusion follows from the list. Some entries were individual sites or subdomains, and Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s entire website, products or customer base.
Was information stolen or were iPhones compromised?
The reporting describes code that attempted to collect some information and deliver exploit-kit content to certain Apple devices. It does not establish how many attempts succeeded or confirm a count of compromised iPhones or stolen payment details.
What did Optimizely do after discovering the issue?
Optimizely said it fixed the vulnerability and removed injected code from affected projects. It also told BleepingComputer it had ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers.
What should iPhone and iPad users do?
Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later. The source says those versions had been released months before the incident; users should check Apple’s current software-update guidance for their device.
Source: ThorstenMeyerAI.com
