🔍 Read the full analysis: Could Your AI Accounts Be At Risk After Malware Hit 178 Websites? 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’s web experimentation platform on Nov. 16, 2026. Optimizely says an unauthorized party exploited a vulnerability in its Experimentation account signup flow, added code to some customer projects, and that it has fixed the flaw and notified affected customers. The scope of any successful data theft or device compromise has not been established.
Malicious JavaScript reached visitors to 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, creating a supply-chain incident that could put information entered on affected pages at risk; the available findings do not establish how many visitors were harmed.
Report URI said it found the code in 188 of 1,611 Optimizely snippets it checked and identified 178 organizations whose visitors were served the malicious script. It said the true number may be higher. BleepingComputer independently reported that urlscan.io scans showed the script loading or attempting to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listing does not mean an organization’s entire website or customer base was affected: some entries were specific subdomains or tools.
The payload attempted to replace cryptocurrency wallet addresses on pages and in the clipboard, monitor card details entered into sites’ own form fields, and collect cookies and screenshots. Report URI said card details entered into hosted payment frames, such as those provided by Stripe or Adyen, were beyond the script’s reach. The code also directed some iPhones and iPads toward the Coruna and DarkSword exploit kits. Hudson Rock cautioned that its analysis found delivery observations, not demonstrated iPhone compromises.
Report URI saw the first injection at 04:21 UTC on Nov. 16 and said all infected Optimizely files had been cleaned by 23:11 UTC, about 19 hours later. Optimizely’s Nov. 17 status update said it had fixed the vulnerability and removed injected code from affected projects. The company 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
Risks for Site Visitors
The incident shows how a compromise at a web-service provider can put visitors at risk even when the sites they visit were not themselves hacked. Customer pages loaded Optimizely snippets as a trusted part of their web experience; the attacker’s code was inserted into customer project settings and delivered through that expected route, Report URI said. Visitors generally would have had little reason to distinguish the injected code from the legitimate script.
For people who visited affected pages, the reported capabilities make crypto transactions and information entered into page forms areas of concern. Report URI said the script could replace a wallet address copied while the affected tab was open, and could watch card details typed into a site’s own fields. These are reported capabilities, not proof that an attacker successfully captured or used any particular visitor’s information. The sources do not provide a confirmed count of stolen credentials, payment details or compromised devices.
The findings also point to uneven defenses among affected organizations. Report URI said it checked security policies on the organizations’ own sites and found that 24 of 159 blocked the code, while 68 had no policy. That snapshot does not establish why each site’s controls differed or whether a policy would have prevented every part of the attack. It does show why organizations’ protections against unauthorized scripts matter alongside the security of third-party suppliers.
Products Worth Considering

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

DJI Mini 5 Pro Fly More Combo with DJI RC 2, 1-Inch CMOS

Apple Watch SE 3 GPS 40mm Smartwatch
As an affiliate, we earn on qualifying purchases.
How Optimizely Snippets Were Altered
Optimizely Web lets customers run experiments on their pages using a small JavaScript snippet. According to Report URI, each customer’s snippet includes project settings and can run optional customer-written code called Project JavaScript across pages. The attacker added code to that field in customer projects, while the rest of each snippet remained unchanged, the researcher said. The affected sites continued requesting the file from an Optimizely address they already trusted.
Report URI said the incident was not a content delivery network cache-poisoning attack. Optimizely’s own websites also carried the malicious code, according to the researcher. Optimizely attributed the breach to a flaw in the Experimentation account signup flow. Its status update, posted at 01:02 UTC on Nov. 17, said the vulnerability was fixed and the injected code removed.
Report URI also described an earlier wave beginning Nov. 13, when the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media. Those sites are separate from the list of 178 organizations linked to the Optimizely incident. 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 a status-page update posted Nov. 17
Scope and Impact Still Unclear
The published findings do not establish how many visitors saw the code, whether the attempted collection resulted in stolen information, or whether any user’s wallet, payment card or device was successfully compromised. Hudson Rock’s iPhone findings concern delivery to exploit kits, not confirmed infections. Report URI said its count came from checking 1,611 Optimizely snippets and that the real number could be higher; the completeness of that estimate remains uncertain.
It is also unclear how a vulnerability in the signup flow enabled access to so many unrelated customer projects. Optimizely’s statements say the flaw was fixed and affected customers notified, but the supplied material does not explain the technical path or identify the unauthorized party. The presence of a company or subdomain on Report URI’s list does not show that every page, checkout process or customer account was exposed. The separate Kissmetrics, StorifyMe and Minute Media activity also has no publicly resolved entry route in the source material.
Customer Checks and Investigation
Optimizely says it has fixed the vulnerability, removed injected code, ended active sessions, revoked tokens, reset access for affected user accounts and notified customers it identified as affected. Organizations using the service will need to review those notices and investigate their own project configurations, access logs and web-security controls to determine whether their pages were exposed and what information may have been at risk.
Visitors who used an affected page should treat unexpected wallet-address changes with caution and review relevant account or payment activity if they entered sensitive information into a site’s own form. Report URI advises iPhone users to update to iOS 18.7.3 or later, or iOS 26.3 or later; the source says those releases came out months before the incident. That advice does not mean every device that visited an affected page was compromised.
Further reporting from Optimizely and security researchers may clarify the signup-flow vulnerability, the number of affected projects and whether investigators found evidence of successful theft or device compromise. Until then, the confirmed picture is a period of malicious script delivery through a trusted third-party service—not a verified count of victims or losses.
Key Questions
What happened in the Optimizely incident?
Report URI says an unauthorized party added malicious JavaScript to some customer projects through Optimizely’s Experimentation platform. The code was served to visitors of 178 organizations on Nov. 16, 2026, according to the researcher.
Does being on the list mean a company’s whole website was affected?
No. Report URI’s list includes organizations and specific sites or subdomains. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s full website, products, customer base or checkout system.
Were visitors’ cards or iPhones confirmed stolen or compromised?
The available findings describe what the script attempted to do, not confirmed outcomes for individual visitors. Report URI said the code watched for card details entered into sites’ own form fields. Hudson Rock said its iPhone analysis showed delivery toward exploit kits, not demonstrated device compromises.
What should visitors do now?
Review relevant payment and account activity if you entered sensitive information on a page you believe was affected, and be alert to wallet addresses changing when copied. Report URI advises iPhone users to install iOS 18.7.3 or later, or iOS 26.3 or later. The source material does not establish that every visitor was exposed or compromised.
Has Optimizely fixed the problem?
Optimizely said on Nov. 17 that it fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens, reset access for affected users and notified customers it identified as affected. The supplied material does not explain the flaw’s technical mechanics or confirm the full scope of impact.
Source: ThorstenMeyerAI.com
