🔍 Read the full analysis: AI Users And Website Malware: What To Check After The Optimizely Incident 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
Optimizely says an unauthorized party exploited a vulnerability to add malicious JavaScript to some customer projects on November 16, 2026. Report URI found the code in snippets associated with 178 organisations and says it attempted several forms of data theft and iPhone exploit delivery. The code was removed, but the scope of any resulting data or device compromise remains unclear.
Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation platform to add malicious JavaScript to some customer projects, code that Report URI says was served to visitors of sites associated with 178 organisations on November 16. The injected script attempted to steal or alter information and deliver exploit kits to some Apple devices; the episode shows how a compromise at a web-service provider can affect visitors to many separate organisations without those organisations’ own sites being directly hacked.
Security researcher Scott Helme of Report URI reported that the malicious code appeared in Optimizely Web snippets loaded by customer websites. Report URI checked 1,611 snippets and found the code in 188; it said the actual number could be higher. The 178 organisations in its published list include sites associated with Zoom, the BBC, CNN, HSBC, Salesforce and IKEA. A listed domain or subdomain does not establish that an organisation’s whole website, checkout or customer base was affected.
According to Report URI, the injected script attempted to replace cryptocurrency wallet addresses in page content and clipboard activity, collect payment-card details entered into a site’s own form fields, and capture cookies and screenshots. It also directed some iPhones and iPads toward the Coruna and DarkSword exploit kits. Report URI said the script was rebuilt 26 times during the day. Hudson Rock, which examined the iPhone-related activity, cautioned that its findings were delivery observations, not proof of successful device compromises.
Report URI first observed an Optimizely injection at 04:21 UTC on November 16 and said all infected Optimizely 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 Vendor Script Reached Visitors
The incident matters because many organisations load a third-party script to run experiments on their websites. In this case, Report URI says the malicious code was placed in the Project JavaScript field of customer projects. The rest of each snippet was not changed, and the file continued to arrive from an Optimizely address that the affected sites already trusted. That means a visitor could receive the code through a familiar page even if the site operator had not intentionally added it.
For users, the possible exposure depends on what they did on an affected page while the script was active and what device they used. Report URI said card details entered in a site’s own form fields could be in scope, while cards entered in hosted payment iframes such as Stripe or Adyen were beyond this script’s reach. It also warned that copying a wallet address while an affected tab was open could result in pasting an attacker-controlled address. These are descriptions of the script’s behavior and potential reach, not confirmation that a particular visitor lost money or had an account taken over.
The findings also raise questions for organisations that rely on external code. Report URI said only 24 of 159 affected organisations it checked had security policies that blocked the code, while 68 had no such policy. Those figures describe its review of the organisations’ site policies; they do not establish whether users at the remaining sites suffered harm.
Products Worth Considering

LG UltraGear 27-inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDR True Black 400

Apple Watch SE (2nd Generation) GPS 40mm Smartwatch with Starlight Aluminum Case and Starlight Sport Band (S/M)

Samsung 27-Inch Odyssey OLED G5 QHD Gaming Monitor (G50SF)
As an affiliate, we earn on qualifying purchases.
What Report URI Traced
Optimizely Web delivers a small JavaScript snippet for each customer site. The snippet can carry page experiments and an optional Project JavaScript field, where customers can add code that runs across their pages. Report URI said the attacker wrote code into that field in customer projects. It also said the incident was not a content-delivery-network cache-poisoning attack, and noted that Optimizely’s own websites carried the code.
Report URI described an earlier wave beginning November 13, when the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media, on sites outside the 178-organisation Optimizely list. Hudson Rock also found the pattern but said how the code entered those services remained unresolved. The available source material does not establish whether the earlier activity and the Optimizely compromise shared the same access route.
Report URI’s list spans multiple sectors, with banking and finance accounting for 32 organisations, technology and software 23, and retail 20. BleepingComputer reported independently checking scans showing the script loaded or tried to load on sites including the BBC, CNN, Zoom, KLM, GitLab and Salesforce. These checks support that the script was present or attempted on particular pages; they do not show that every page on those brands’ sites was affected.
“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 November 17, 2026
What the Evidence Cannot Confirm
Optimizely has not publicly explained the code-level mechanics of the signup-flow vulnerability or how it gave the attacker write access to unrelated customer projects. The company says it fixed the flaw, removed injected code and notified affected customers, but the available statements do not give a full technical account of the incident or state how many projects were changed.
It is also unclear how many visitors encountered the script, whether any data was successfully stolen, whether cryptocurrency was redirected, or whether any iPhones or iPads were actually compromised. Report URI’s count is based on the snippets it checked, and the researcher said the real number may be higher. A site’s appearance on the list does not prove that all of its pages or users were exposed.
For visitors, it may not be possible to determine from browsing history alone whether the script ran or what it captured. The source material does not report confirmed losses or provide a complete account of affected payment forms, accounts or devices. The earlier activity involving three other providers also remains unresolved.
Steps for Users and Site Operators
People who used a listed site on November 16 should review activity tied to any sensitive action they took during the exposure window. Anyone who entered a payment-card number into a site’s own form can contact the card issuer, monitor transactions and follow the issuer’s guidance if suspicious activity appears. Visitors who copied a cryptocurrency address while an affected page was open should verify the destination address carefully before sending funds. These are precautionary steps, not evidence that an individual was affected.
Report URI advised iPhone users to update to iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock’s findings do not confirm successful device infections, but keeping devices updated reduces exposure to known vulnerabilities. Users should also review account activity and use established security practices if they suspect credentials or session information may have been exposed.
Website operators should check whether their Optimizely projects or other third-party scripts were affected, follow the provider’s incident notices, and review access controls and security-policy protections for browser scripts. Optimizely says it has reset access for affected accounts and notified affected customers. Further technical details from the company and independent investigators could clarify the vulnerability, the number of projects involved and whether any data theft or device compromise was confirmed.
Key Questions
What happened in the Optimizely incident?
Optimizely said an unauthorized party exploited a vulnerability in its Experimentation platform and added malicious JavaScript to some customer projects. Report URI observed the code being served through snippets on sites associated with 178 organisations on November 16, 2026.
Does a listed company’s entire website have to be affected?
No. The published list includes specific sites and subdomains. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s entire website, products, customer base or checkout system.
Were visitors’ cards or iPhones confirmed stolen or compromised?
The source material does not confirm successful theft or device compromise. Report URI described code that could collect card details entered into a site’s own form fields and deliver exploit kits to some Apple devices. Hudson Rock said its iPhone findings showed delivery, not demonstrated compromise.
What should someone do if they visited an affected site?
Review payment and account activity, contact the card issuer if you entered card details into a site’s own form and see suspicious transactions, and verify cryptocurrency addresses before sending funds. iPhone users should install the recommended software updates. These precautions do not mean that a visitor was necessarily affected.
Has Optimizely fixed the vulnerability?
Optimizely’s November 17 status update said it had fixed the vulnerability and removed injected code from affected projects. The company also said it had ended active sessions, revoked tokens, reset access for affected accounts and notified customers it considered affected. A fuller explanation of how the flaw worked was not provided in the source material.
Source: ThorstenMeyerAI.com
