🔍 Read the full analysis: The Optimizely Malware Incident And AI Users: A Question-and-Answer Guide 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 signup flow, and that it fixed the flaw, removed injected code and notified affected customers. The extent of any resulting data theft or device compromise has not been established.
Malicious JavaScript delivered through Optimizely appeared on websites associated with 178 organizations on Nov. 16, according to security researcher Scott Helme’s Report URI investigation. Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation service to add code to some customer projects, creating potential risks for people browsing those sites; evidence that the code was delivered does not establish that every visitor or organization suffered a compromise.
Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188. Its report identifies 178 organizations whose sites served or attempted to serve the code and says the actual number may be higher. BleepingComputer reported that urlscan.io scans independently showed the script loading or attempting to load on sites including those associated with Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listing can represent a particular subdomain, not a company’s entire website or services.
According to Report URI, the attacker inserted code into the optional Project JavaScript field in customer experiments. The rest of each snippet was reportedly unchanged, and the file continued to be delivered from Optimizely, a provider those sites had already chosen to trust. Report URI said this was not a content-delivery-network cache-poisoning attack. It recorded the first injection at 04:21 UTC on Nov. 16 and said infected files had been cleaned by 23:11 UTC, a period of about 19 hours.
The payload was designed to behave differently depending on a visitor’s device and activity. Report URI says it attempted to replace cryptocurrency wallet addresses in page text, forms and clipboard contents; collect payment-card details entered into a site’s own form fields; and capture cookies and screenshots. It also reported that the script could direct some iPhones and iPads toward the Coruna and DarkSword exploit kits. Hudson Rock described its findings on the iPhone stage as delivery observations, not demonstrated iPhone compromises. Report URI said card details entered in hosted payment frames, such as Stripe or Adyen, were outside 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
Risks From Trusted Website Scripts
The incident illustrates how a problem at a third-party service can affect visitors to many separate organizations without those organizations’ own websites being directly hacked. A customer site that loads an experimentation script gives that supplier’s code a route into pages viewed by customers. If that code is altered, visitors may have little visible indication that anything has changed.
The reported payload targeted information with direct financial and privacy implications, including wallet transactions, payment details, cookies and screenshots. But the distinction between malicious code being available and a person’s information or device actually being compromised matters: the source material does not establish how many visitors encountered each function or what data, if any, was successfully taken.
Report URI also checked security policies on affected organizations’ own sites. It says 24 of 159 blocked the code, while 68 had no policy in place. Those figures point to a possible gap in defenses against unauthorized scripts, but they do not by themselves show whether any individual organization suffered a confirmed breach.
Products Worth Considering

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Bluetooth 5.3, USB-C Charging, and IPX4 Water Resistance

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Sony WH-1000XM6 Wireless Noise-Canceling Headphones, Black
As an affiliate, we earn on qualifying purchases.
How Optimizely’s Snippets Were Altered
Optimizely Web supports experiments that change or test website content. Customer sites load a small JavaScript snippet from the platform; the snippet carries the customer’s experiments and may include custom Project JavaScript that runs on pages. Report URI says the attacker wrote into that custom-code field across customer projects while leaving the remainder of the snippets intact.
Optimizely’s status page, posted at 01:02 UTC on Nov. 17, said an unauthorized party had exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects. The company said it had fixed the vulnerability and removed injected code from affected projects. It also told BleepingComputer that the flaw was in the Experimentation account signup flow, and said it had ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers.
Report URI says the same actor’s injector appeared from Nov. 13 in scripts associated with three other providers—Kissmetrics, StorifyMe and Minute Media—on sites outside its Optimizely list. Hudson Rock also reported that pattern. The material provided does not establish how the code entered those services or whether those earlier instances were connected through the same access route.
“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 on Nov. 17
Exposure and Intrusion Route Unclear
The number of affected visitors and any confirmed theft remain unknown in the source material. Report URI documented the script’s presence and described what it attempted to do, but Hudson Rock cautioned that its iPhone findings show delivery rather than demonstrated device compromise. No confirmed count of stolen card numbers, wallet losses, exposed cookies or compromised phones is provided.
Optimizely has not publicly explained, in the statements cited here, how a flaw in the signup flow allowed an attacker to write code into projects belonging to unrelated customers. Report URI says the injector was rebuilt 26 times during the day, but that observation does not establish how many versions reached visitors or what each version successfully collected. The listed organizations’ exposure also varied by subdomain; presence on one listed site does not establish that an organization’s full website, checkout system or customer base was affected.
Report URI advised iPhone 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 earlier. This is precautionary advice in light of the reported exploit-kit targeting, not confirmation that users with older software were infected.
Customer Reviews and Technical Disclosure
Optimizely says it has fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens, reset access for affected accounts and notified customers it identified as affected. The next public milestones would be further technical details about the signup-flow flaw, clearer information about how the attacker gained write access and customer disclosures describing any confirmed impact.
Organizations named in the reporting may need to determine which specific pages loaded the code, review relevant web and security records, and assess whether visitors entered information into affected forms during the exposure period. The available reporting does not say which organizations have completed those reviews or whether any have confirmed data theft. People concerned about the reported iPhone targeting can check that their devices run a version recommended by Report URI, while treating the exploit-kit delivery report as evidence of risk rather than proof of compromise.
Report URI says the injection it observed through Optimizely had been removed by late Nov. 16, but the earlier reports involving three other providers remain a separate unresolved thread. Further information from Optimizely, affected organizations or investigators may clarify whether those incidents were connected and whether any effects persisted after the injected code was cleaned.
Key Questions
What happened in the Optimizely incident?
Report URI says an unauthorized party used Optimizely’s Experimentation platform to serve malicious JavaScript to visitors of sites associated with 178 organizations on Nov. 16, 2026. Optimizely confirmed that a vulnerability had been exploited to add code to some customer projects.
Does being on the list mean an organization’s whole website was affected?
No. The reporting includes individual sites and subdomains. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s entire website, product, customer base or checkout system.
Was information or money confirmed stolen?
The source material describes code intended to collect or alter information, but does not provide a confirmed total for stolen data, card fraud or cryptocurrency losses. Code delivery alone does not prove that a particular visitor’s information was taken.
Were iPhones confirmed compromised?
No confirmed number of compromised iPhones is reported. Hudson Rock characterized its findings as observations of exploit-kit delivery, not demonstrated iPhone compromises. Report URI advised users to update to iOS 18.7.3 or later, or iOS 26.3 or later.
What has Optimizely said it did?
Optimizely said it fixed the vulnerability and removed injected code from affected projects. It also told BleepingComputer it ended active sessions, revoked tokens, reset access for affected accounts and notified customers it identified as affected.
Source: ThorstenMeyerAI.com
