🔍 Read the full analysis: Could The Malware On 178 Websites Affect Your AI Use? What To Check 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 delivered to visitors of 178 organizations through Optimizely’s web experimentation platform on Nov. 16, 2026. Optimizely says an unauthorized party exploited a vulnerability, removed the code and notified affected customers. The script attempted several forms of data theft and device-specific exploitation, but confirmed successful compromises have not been established in the source material.
Malicious JavaScript was delivered to visitors of sites associated with 178 organizations through Optimizely’s web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely says an unauthorized party exploited a vulnerability to add code to some customer projects; the code attempted to steal information and target some mobile devices, though the available findings do not establish how many visitors were successfully compromised.
Report URI says it found the code in 188 of 1,611 Optimizely snippets it checked and believes the actual number may be higher. It observed the first injection at 04:21 UTC on Nov. 16, and says infected files had been cleaned by 23:11 UTC, about 19 hours later. Optimizely said it fixed the vulnerability, removed injected code from affected projects and notified affected customers.
The malicious script was placed in the Project JavaScript field of customer projects, according to Report URI. Optimizely snippets can load custom code on a customer’s pages. The affected sites themselves did not necessarily have to be breached: the visitors’ browsers received code through a third-party service their sites already used. Report URI says the rest of each snippet was untouched and rules out a CDN cache-poisoning attack.
Report URI says the script tried to replace cryptocurrency wallet addresses in page text, form fields and clipboard contents; collect payment card details typed into sites’ own form fields; capture cookies and screenshots; and direct some iPhones and iPads toward the Coruna and DarkSword exploit kits. It says card details entered in hosted payment iframes, such as Stripe or Adyen, were outside the script’s reach. These are reported capabilities and attempts, not evidence that every listed action succeeded.
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 Vendor Script Reached Visitors
The incident shows how a compromise at a third-party software provider can expose visitors across many otherwise separate websites. Sites load Optimizely’s code to run experiments; when that trusted code was altered, a visitor’s browser could receive malicious instructions from a source the site had authorized.
The range of organizations named by Report URI includes media, finance, technology and retail sites. But a listing does not mean every page, service or customer of an organization was affected. Hudson Rock cautioned that an affected subdomain alone does not establish exposure across an organization’s whole website, checkout system or customer base.
For people using AI services, the report does not identify a specific AI product or show that AI systems were compromised. The practical concern is broader: if an AI service or its users visited an affected page, the reported risks would depend on the page, browser, device and actions taken. The source does not confirm that AI accounts, prompts or data were stolen.
Products Worth Considering

Jackery Solar Generator 1000 v2 with 200W Solar Panel, 1024Wh LiFePO4 Battery

Bose QuietComfort Wireless Noise-Cancelling Headphones, Sandstone

Jackery Explorer 300 Portable Power Station, 292Wh
As an affiliate, we earn on qualifying purchases.
What the Optimizely Snippet Did
Optimizely Web lets customers run experiments on their websites by loading a small JavaScript snippet. Report URI says the attacker added code to the Project JavaScript field in customer projects, allowing it to run on pages that loaded those snippets. That mechanism helps explain why a vulnerability in a supplier’s service could affect many organizations without each organization being hacked directly.
Report URI’s published list names 178 organizations, including sites associated with Zoom, the BBC, CNN, HSBC, Salesforce and IKEA. 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. 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 in the source material.
The report says the payload was rebuilt 26 times during the day. That is a count of rebuilds, not a measure of successful infections or stolen data. Report URI also found gaps in affected organizations’ security policies: 24 of 159 checked blocked the code, while 68 had no policy. These figures describe the sites it assessed, not all organizations or all websites.
“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
The available account does not establish how many people were affected, whether the script successfully stole card details, cookies or screenshots, or whether any devices were compromised. Hudson Rock specifically describes its iPhone findings as observations of delivery rather than demonstrated compromises. The presence of a site or subdomain on the list is not proof that every visitor or page was exposed.
Optimizely said the flaw was in its Experimentation account signup flow, but its public statements cited here do not explain how that flaw enabled write access to unrelated customer projects. Report URI and Hudson Rock both said the technical mechanics were not clear. The earlier code observed in scripts from three other providers is also unresolved, and the source does not establish whether those incidents shared the same entry method.
Checks for Users and Site Operators
People who visited a listed site during the reported window can update their devices and browsers, review financial accounts for unusual activity and contact their bank if they see suspicious card transactions. Report URI advises iPhone and iPad users to install iOS 18.7.3 or later, or iOS 26.3 or later. Users who copied a cryptocurrency address while an affected tab was open should verify the destination address independently before sending funds. These steps are precautionary; the report does not establish that every visitor was exposed to a successful theft.
Organizations should check whether their own domains and subdomains appear in Report URI’s list, review their Optimizely projects and ask the provider for incident-specific guidance. Optimizely said it had ended active sessions, revoked tokens and reset access for affected user accounts, in addition to removing the code. Site operators can also review their browser security policies and third-party scripts, since Report URI found that many checked sites lacked a policy that blocked the code.
The next significant information would be a fuller technical account from Optimizely, findings on whether data or devices were actually compromised, and clarification about the separate services whose scripts reportedly carried similar code. Until then, exposure should be treated as a reported risk rather than proof of a successful compromise for any particular visitor.
Key Questions
Were 178 websites themselves hacked?
Not necessarily. Report URI says malicious code was added to Optimizely customer projects and delivered through snippets that affected sites had chosen to load. That does not mean each website’s own systems were breached.
Does the report show that AI services or AI data were compromised?
No specific AI service, account, prompt or dataset is identified as compromised in the source material. It reports code on sites associated with 178 organizations, not a confirmed breach of AI systems.
What did the malicious code try to do?
Report URI says it attempted to replace cryptocurrency addresses, collect card details entered into sites’ own form fields, capture cookies and screenshots, and direct some Apple mobile devices to exploit kits. Those reported attempts do not prove that each one succeeded.
What should someone do after visiting an affected site?
Update the device and browser, check financial accounts for suspicious activity and verify cryptocurrency addresses carefully before sending funds. Report URI recommends iOS 18.7.3 or later, or iOS 26.3 or later, for iPhone and iPad users.
Is the number of affected visitors known?
No. Report URI identified the code in 188 of 1,611 snippets it checked and said the real number might be higher, but the source does not give a count of exposed or successfully compromised visitors.
Source: ThorstenMeyerAI.com
