🔍 Read the full analysis: 178 Major Sites Were Hit By Malware—What AI Users Should Review 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 of 178 organizations through Optimizely Web on Nov. 16, 2026. Optimizely says an unauthorized party exploited a vulnerability, removed the code and notified affected customers; the precise route to access across customer projects remains unclear.
Malicious JavaScript was served to visitors of 178 organizations through the Optimizely Web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects; the incident matters because visitors encountered it through scripts their organizations had chosen to load from a trusted supplier.
Report URI says it found the code in 188 of 1,611 Optimizely snippets it checked and considers the actual number potentially higher. The researchers reported the first injection they observed at 04:21 UTC and said all infected Optimizely files had been cleaned by 23:11 UTC, about 19 hours later. BleepingComputer separately reported confirming that the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce.
The malicious script was added to a customer-specific field called Project JavaScript, according to Report URI. Optimizely Web snippets load from the platform and can carry custom experiments and code. Report URI said the rest of each affected snippet remained untouched and ruled out a content-delivery-network cache-poisoning attack. Optimizely said it fixed the vulnerability and removed injected code, and told BleepingComputer it had ended active sessions, revoked tokens and reset access for affected accounts.
Report URI said the payload changed during the day and could attempt to replace cryptocurrency wallet addresses, capture payment-card details entered into a site’s own form fields, and collect cookies or screenshots. It also described code that could direct older Apple devices toward the Coruna and DarkSword exploit kits. Hudson Rock cautioned that its iPhone findings were delivery observations, not evidence that devices were compromised. Report URI said card details entered in hosted payment frames such as Stripe or Adyen were beyond the code’s reach.
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
The Risk of Trusted Website Scripts
The incident shows how a compromise at a third-party service can expose visitors across many unrelated organizations without attackers having to break into each organization’s website. The script arrived through Optimizely, a service already authorized by affected sites, making it harder for visitors to distinguish the malicious code from normal page functions.
For people who visited affected pages, the possible exposure depends on the site, device and actions taken while the script was active. Report URI described attempts to alter wallet addresses and collect information, but the available reporting does not establish that every visitor was targeted successfully or that data was stolen in every case. Hudson Rock specifically said the iPhone activity it examined did not demonstrate device compromise.
The findings also raise questions about customer-side safeguards. Report URI checked security policies on affected organizations’ sites and said 24 of 159 blocked the code, while 68 had no policy in place. Those figures describe the sample it examined, not all 178 organizations, and do not by themselves establish the full effect of any policy on individual visitors.
Products Worth Considering

Jackery Explorer 300 Portable Power Station, 292Wh

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
As an affiliate, we earn on qualifying purchases.
How the Optimizely Snippets Worked
Optimizely Web supports experimentation on customer websites by loading a small JavaScript snippet. Customers can add custom code through a Project JavaScript field, which runs on pages that load the snippet. Report URI said the attacker inserted code into that field in customer projects, while the files continued to be delivered from an Optimizely address that the affected sites already trusted.
Report URI published a list of 178 organizations, including companies and organizations in finance, technology and retail. Its sector counts put banking and finance at 32, technology and software at 23, and retail at 20. A listing does not mean an organization’s entire website or customer base was affected: some entries were individual subdomains or tools. Hudson Rock warned that an affected subdomain alone does not establish exposure across an organization’s website, products, customers or checkout system.
Report URI also described an earlier wave beginning Nov. 13, in which the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media on sites outside the 178-organization list. Hudson Rock said how the code entered those services remains unresolved. The available accounts do not establish whether those incidents shared the same access route as the Optimizely compromise.
“An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.”
— Optimizely, in a status-page update posted Nov. 17
What the Investigation Has Not Established
Optimizely has said the vulnerability involved the Experimentation account signup flow, but its public account, as described in the source material, does not explain the flaw’s technical mechanics or how it allowed changes to many unrelated customer projects. Report URI said it could not determine how the attacker gained that write access; Hudson Rock likewise said Optimizely’s disclosure did not explain the bug at code level.
The reported figure of 178 is based on organizations identified by Report URI, and the researcher said the real total may be higher. The scope of exposure within each organization is also uncertain: inclusion of one site or subdomain does not prove that all of a company’s pages were affected. The reporting does not establish how many people saw the code, whether particular data was successfully collected, or whether any phones were compromised.
It is also unclear whether the earlier activity involving Kissmetrics, StorifyMe and Minute Media had the same underlying access method. Those services were associated with an earlier appearance of the same actor’s injector, but Hudson Rock described how the code entered them as unresolved.
Customer Reviews and Security Updates
Optimizely said it had fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers. The supplied reporting does not give a timetable for a detailed technical post-incident account or say whether further public updates are planned.
Organizations using Optimizely should review the platform’s notice and their own project configuration, while checking for unauthorized changes to custom JavaScript and relevant access records. Site operators can also examine whether their security policies restrict unexpected scripts. These are practical review steps, not confirmation that any particular organization suffered data theft.
Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. The source says both versions had been released months before the incident. Users and organizations should rely on device and vendor guidance for current updates; the reporting does not identify a confirmed count of compromised devices or provide a complete list of affected visitors.
Key Questions
What happened to the 178 organizations’ websites?
Report URI says malicious JavaScript was delivered through Optimizely Web snippets associated with 178 organizations on Nov. 16, 2026. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects.
Does being on the list mean an organization’s whole website was affected?
No. The reporting identifies affected sites or subdomains, and some entries were individual tools or subdomains. Hudson Rock said an affected subdomain does not establish exposure across an organization’s full website, products, customer base or checkout system.
What information could the malicious script target?
Report URI said the code could attempt to replace cryptocurrency addresses, capture card details entered into a site’s own form fields, and collect cookies or screenshots. It said hosted payment frames such as Stripe and Adyen were beyond the card-skimming code’s reach. The reporting does not establish that every attempt succeeded.
Were iPhones confirmed compromised?
No confirmed count of compromised iPhones is provided. Hudson Rock said its findings showed delivery activity, not demonstrated iPhone compromises, and Report URI advised users to update to iOS 18.7.3 or later, or iOS 26.3 or later.
What remains unknown about the attack?
The public accounts do not explain the vulnerability’s code-level mechanics or how it gave an attacker write access to many customer projects. The number of visitors affected, whether information was successfully stolen, and whether the earlier activity through three other providers used the same access method also remain unclear.
Source: ThorstenMeyerAI.com
