🔍 Read the full analysis: How The Optimizely Malware Hit 178 Websites—and What AI Users Can 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 served through Optimizely Web snippets to visitors of 178 organizations on Nov. 16, 2026. Optimizely says an attacker exploited a vulnerability in its Experimentation signup flow, and the company has removed the code and notified affected customers. Researchers say the script targeted cryptocurrency addresses, payment-card details and some Apple devices, but confirmed device compromises have not been established.
Malicious JavaScript was served to visitors of websites belonging to 178 organizations 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 to add code to some customer projects; the incident matters because visitors received it through a third-party script their organizations had chosen to load.
Report URI says it checked 1,611 Optimizely snippets and found malicious code in 188. The researcher’s report counted 178 affected organizations and said the actual number could be higher. The list includes sites associated with Zoom, the BBC, CNN, HSBC, Salesforce and IKEA. A listed organization does not mean its entire website or all of its customers were exposed: some entries were specific subdomains or tools.
Optimizely said on its status page that an unauthorized party exploited a vulnerability in Experimentation and used it to add JavaScript to some customer projects. The company told BleepingComputer that the flaw was in the Experimentation account signup flow, and said it had notified affected customers. It also said it fixed the vulnerability and removed injected code; according to its statement to BleepingComputer, it ended active sessions, revoked tokens and reset access for affected accounts.
Report URI observed 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. BleepingComputer separately reported that urlscan.io scans showed the script loading or attempting to load on a number of sites, including those associated with Zoom, KLM, GitLab, the BBC, CNN and Salesforce.
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 One Script Reached Many Sites
The incident shows how a compromise at a shared software provider can reach visitors across unrelated organizations without attackers separately breaking into each organization’s website. Optimizely Web snippets load on customer sites to run experiments; according to Report URI, the attacker changed a custom-code field within customer projects while leaving the rest of each snippet intact. The code was then delivered from an address those sites already trusted.
That delivery route makes the event relevant to both businesses and people using AI services. Organizations that embed external scripts—including scripts supporting experimentation, analytics or personalization—may need to check their own deployment and security controls. AI users should not assume that a familiar brand or an AI-related website is safe merely because its main service was not itself reported as compromised. The source material does not establish that AI products or AI accounts were specifically targeted.
Report URI said the script attempted to replace cryptocurrency wallet addresses in page content and the clipboard, collect card details entered into sites’ own forms, and capture cookies and screenshots. It also described code that directed some iPhones and iPads toward exploit kits. These are reported capabilities and actions attempted, not proof that every visitor suffered theft or that devices were compromised.
Products Worth Considering

Apple Watch Series 8 GPS 41mm Smartwatch with Midnight Aluminum Case and Midnight Sport Band (S/M)

DJI Osmo 360 Road Cycling First-Person Combo Action Camera

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black
As an affiliate, we earn on qualifying purchases.
What the Optimizely Snippet Did
Optimizely Web runs through a JavaScript snippet placed on a customer’s site. Each project can include experiments and an optional Project JavaScript field for custom code that runs on pages using the snippet. Report URI said the attacker inserted code into that field and said the incident was not a content-delivery-network cache-poisoning attack.
Report URI said the payload was rebuilt 26 times during the day, while visitors received the same script. Its behavior depended on the device and on what a visitor did. The researcher reported that the code watched for payment-card numbers, expiration dates and security codes entered into a site’s own form fields. It said details entered into hosted payment iframes, such as those from Stripe or Adyen, were out of the script’s reach.
The incident followed an earlier wave: Report URI said that from Nov. 13 the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media on sites outside the 178-organization list. Hudson Rock also reported that pattern, but said how the code entered those services remained unresolved. Report URI separately found weaknesses in affected organizations’ security policies: 24 of 159 blocked the code, while 68 had no policy, according to its review.
“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 Shown
Optimizely has identified the affected service and said the vulnerability was in the account signup flow, but its public account does not explain the flaw’s technical mechanics or how it allowed access to many unrelated customer projects. Report URI said it did not know how the attacker obtained write access, and Hudson Rock said the disclosure did not explain the bug at code level.
The number of affected organizations may also change: Report URI said its count could be an underestimate. The published list identifies organizations and, in some cases, particular subdomains; it does not establish that every page, checkout flow, product or customer account was exposed. Nor do the reports show how many visitors saw the code, entered sensitive information, or experienced data theft.
For Apple devices, Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock cautioned that its findings showed delivery observations rather than demonstrated iPhone compromises. The available material does not confirm successful exploitation of a visitor’s device or provide a verified count of affected people.
Customer Checks and Investigation
Optimizely said it had fixed the vulnerability, removed injected code, notified affected customers, ended active sessions, revoked tokens and reset access for affected accounts. Organizations using Optimizely Web can check their projects and pages against the company’s notices, confirm that the snippet and custom JavaScript are clean, and review whether their security policies restrict unexpected scripts. Report URI’s findings indicate that policy coverage varied among the organizations it assessed.
Visitors concerned about exposure can update Apple devices to the versions listed by Report URI and remain alert to suspicious changes when copying cryptocurrency addresses or entering payment details. These steps are precautions, not evidence that a particular person was affected. Businesses that entered card details into their own site forms may wish to follow their incident-response procedures and seek guidance from their payment provider.
Further clarity depends on Optimizely’s account of how the signup-flow vulnerability enabled project changes, along with any updated findings from researchers or affected organizations. The current source material does not give a confirmed total of compromised devices, stolen credentials or financial losses.
Key Questions
What happened in the Optimizely incident?
Report URI says malicious JavaScript was served to visitors through Optimizely Web snippets on sites associated with 178 organizations on Nov. 16, 2026. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects.
Were all pages of the named organizations affected?
No such conclusion is established by the reports. The list includes specific sites and subdomains, and Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s entire website, products, customer base or checkout system.
What did the malicious code try to do?
Report URI said it attempted to replace cryptocurrency wallet addresses, collect card details entered into sites’ own forms, capture cookies and screenshots, and direct some Apple devices toward exploit kits. Those reported behaviors do not prove that every attempt succeeded.
Does the report confirm that iPhones were hacked?
No. Hudson Rock described its findings as delivery observations, not demonstrated iPhone compromises. Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later, as a precaution.
What should Optimizely customers check?
Customers can review Optimizely’s notifications, inspect affected projects and custom JavaScript, confirm their snippets are clean, and review controls that restrict unexpected scripts. The reports do not specify a single check that can establish whether an individual visitor’s data was taken.
Source: ThorstenMeyerAI.com
