🔍 Read the full analysis: The Optimizely Malware Story: What AI Users Should Look Into on ThorstenMeyerAI.com
Get smart everyday buys 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 organisations through Optimizely’s experimentation platform on Nov. 16, 2026. Optimizely confirmed an attacker exploited a vulnerability in its Experimentation signup flow, but the precise mechanics and extent of any resulting data theft or device compromise remain unclear.
Malicious JavaScript was served to visitors of sites associated with 178 organisations through Optimizely’s web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation account signup flow to add code to some customer projects, turning a flaw at one supplier into a risk for visitors to multiple customer sites.
Report URI says it checked 1,611 Optimizely snippets and found malicious code in 188; it identified the affected sites as belonging to 178 organisations and said the actual number could be higher. The report describes code that attempted to replace cryptocurrency wallet addresses, collect payment-card details entered into sites’ own forms, and capture cookies and screenshots. It also reported that some iPhones and iPads were directed toward exploit kits. These are reported capabilities and attempts, not proof that every action succeeded or that every visitor was compromised.
The malicious code was added to the Project JavaScript field in some customer projects, Report URI said. That field allows custom code to run on pages using an organisation’s Optimizely snippet. The rest of each snippet was unchanged, according to the researcher, and the code was still delivered from Optimizely’s usual address. Report URI said the incident was not a CDN cache-poisoning attack.
Optimizely’s status page said the company had fixed the vulnerability and removed injected code from affected projects. The company also told BleepingComputer that it had ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers. Report URI placed the first injection it observed at 04:21 UTC on Nov. 16 and said infected files had been cleaned by 23:11 UTC, a window of about 19 hours.
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 Across Trusted Website Scripts
The incident shows how a compromise at a third-party web service can expose visitors to malicious code without attackers directly breaching each customer’s own website. Sites load Optimizely snippets to run experiments; visitors may not know that an external script is active or that its contents have changed. The reported targets included organisations in finance, technology and retail, among other sectors.
For users, the practical risk depends on the page visited, device, browser and actions taken while the code was present. Report URI says the script looked for wallet addresses and could watch for card details typed into a site’s own form fields. It said card numbers entered into hosted payment iframes, such as those operated by Stripe or Adyen, were outside the code’s reach. The report also said the script could capture cookies and screenshots, but the available information does not establish how many records, if any, were successfully taken.
For businesses, the event raises questions about monitoring third-party scripts and limiting what they can do in a browser. Report URI checked security policies on affected organisations’ sites and said 24 of 159 blocked the code, while 68 had no policy. Those figures describe the researcher’s review of the sites and do not establish that a policy alone would have prevented the incident.
Products Worth Considering

Dell UltraSharp U4025QW 40-Inch Curved 5K2K WUHD LED Monitor

Samsung 27-Inch Odyssey G5 QHD Gaming Monitor (G50F)

Canon PIXMA MegaTank G3270 Wireless All-in-One Color Inkjet Printer
As an affiliate, we earn on qualifying purchases.
How the Optimizely Injection Worked
Optimizely Web uses a JavaScript snippet that customer websites load to run page experiments. According to Report URI, the attacker inserted code into the custom Project JavaScript field in affected customer projects. Because the snippets continued to load from an address that those sites already trusted, the malicious code could reach visitors through the normal page-loading process.
Report URI said the payload was rebuilt 26 times during the day and that visitors received the same script, with its actions depending on the device and the visitor’s activity. That count is a reported observation of payload changes; it does not mean there were 26 separate attacks. The researcher also reported an earlier wave beginning Nov. 13 involving scripts associated with Kissmetrics, StorifyMe and Minute Media. The material provided does not establish how the code reached those services or whether the incidents shared the same access route.
The organisation list includes names such as Zoom, the BBC, CNN, HSBC, Salesforce, IKEA, GitLab and UNICEF USA. BleepingComputer said it independently confirmed through urlscan.io scans that the script loaded or attempted to load on several listed sites. A listing does not mean an organisation’s entire website or every customer-facing service was affected; some entries were specific subdomains or tools.
“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 at 01:02 UTC
Scope and Intrusion Method Remain Open
Optimizely has not publicly explained the signup-flow vulnerability’s code-level mechanics or how it enabled changes across multiple unrelated customer projects. Report URI said it could not determine how the attacker obtained write access, and Hudson Rock said Optimizely’s disclosure did not explain the bug’s technical details.
It is also unclear how many visitors encountered the code, whether sensitive information was successfully captured, or whether any devices were compromised. Hudson Rock specifically described its iPhone findings as observations of exploit-kit delivery, not demonstrated compromises. The list of 178 organisations does not establish that all pages, products, customers or checkout systems at those organisations were exposed. Report URI said its count could be incomplete.
The earlier activity involving Kissmetrics, StorifyMe and Minute Media is also unresolved. The supplied reporting does not establish whether those cases were caused by the same vulnerability or how the code entered those services.
Customer Reviews and Technical Disclosure
Optimizely said it had notified affected customers, removed injected code and reset access for affected accounts. The next key information would be a fuller account of the vulnerability, the affected project scope, and whether the company or customers identify confirmed data theft or device compromise. No further disclosure schedule is specified in the available source material.
Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later, versions it said had been released months earlier. Users concerned about exposure can review updates from Apple and guidance from any affected organisation they used during the reported period. The source material does not establish that updating can reverse any past exposure.
Organisations using third-party scripts can review their Optimizely projects and account access, check vendor updates, and examine their own site security policies. These are prudent follow-up steps, not evidence that every listed organisation suffered a separate breach. Further findings from Optimizely, security researchers or affected customers may clarify the incident’s reach.
Key Questions
What happened in the Optimizely malware incident?
Report URI says malicious JavaScript was served to visitors of sites associated with 178 organisations through Optimizely on Nov. 16, 2026. Optimizely confirmed an unauthorized party exploited a vulnerability to add code to some customer projects.
Does being on the affected-site list mean a company was fully breached?
No. A listed organisation may have had a specific subdomain or tool affected. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s entire website, product, customer base or checkout system.
Was information or money confirmed stolen?
The reporting describes code designed to attempt actions such as wallet-address replacement and card-detail collection, but the source material does not confirm how many attempts succeeded or establish a total of stolen information or funds.
Were iPhones confirmed to be compromised?
No confirmed number of compromised iPhones is provided. Hudson Rock said its findings concerned exploit-kit delivery observations, not demonstrated iPhone compromises. Report URI advised users to install the specified iOS updates.
What has Optimizely said it did?
Optimizely said it fixed the vulnerability, removed injected code from affected projects, notified affected customers, ended active sessions, revoked tokens and reset access for affected user accounts. The precise method used to gain write access remains unclear in the available reporting.
Source: ThorstenMeyerAI.com
