🔍 Read the full analysis: Why AI Users Should Review Their Accounts After The Optimizely Malware Attack on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Optimizely confirmed that an unauthorized party exploited a vulnerability to add malicious JavaScript to some customer projects; Report URI says the code reached visitors to sites associated with 178 organisations on November 16. The code attempted to steal or alter information, but delivery does not prove a device or account was compromised. Users should update Apple devices, review financial and account activity, and follow notices from affected services.
Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation platform to add malicious JavaScript to some customer projects, exposing visitors to sites associated with 178 organisations to code that attempted to steal or alter data. For AI users and other visitors, the incident is a reason to review account and payment activity, but security researchers stress that the code being delivered does not prove a device was compromised.
Security researcher Scott Helme of Report URI said the malicious code was served on November 16 through Optimizely Web snippets embedded on customer websites. Report URI checked 1,611 snippets and found the code in 188, which it associated with 178 organisations. The firm said the actual number could be higher. BleepingComputer separately reported that urlscan.io scans showed the script loading or attempting to load on sites including the BBC, CNN, Zoom, GitLab, KLM and Salesforce.
Report URI said the script attempted to replace cryptocurrency wallet addresses, capture payment-card details entered into a site’s own forms, collect cookies and screenshots, and direct some iPhones and iPads toward exploit kits. Its account says payment information entered into hosted payment frames, such as those used by Stripe or Adyen, was outside the script’s reach. The code’s actions depended on the visitor’s device and activity; an attempted capability is not evidence that it succeeded against a particular user.
According to Report URI, the first injection it observed was at 04:21 UTC on November 16, and infected Optimizely files had been cleaned by 23:11 UTC that day. Optimizely said it had fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens and reset access for affected accounts. It also told BleepingComputer that it had notified affected customers.
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
Why Visitors Should Review Accounts
The incident matters because visitors can encounter malicious code through a trusted third-party script on a familiar website, without the website itself being hacked. Report URI described this as a supply-chain attack: customer sites had deliberately loaded Optimizely’s experimentation snippet, and the injected code was delivered through that trusted route. A brand appearing on the affected list does not mean its entire website, checkout system or customer base was exposed.
For people who visited an affected page during the exposure window, sensible steps include checking recent bank, card, cryptocurrency and email account activity, watching for unfamiliar transactions or account changes, and contacting the relevant provider if anything appears suspicious. Users should avoid reusing passwords and should change credentials if they have specific reason to believe an account was accessed. Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock cautioned that its iPhone findings showed delivery of exploit-kit content, not demonstrated device compromises.
The incident also shows why an organisation’s own security controls matter even when a supplier is trusted. Report URI found that only 24 of 159 organisations it checked blocked the code with their security policies, while 68 had no policy. Those figures describe the sites examined, not every organisation or every security measure in place.
Products Worth Considering

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

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Samsung Galaxy Tab A11+ Tablet (6GB RAM, 128GB Storage, Gray)
As an affiliate, we earn on qualifying purchases.
How the Optimizely Script Was Abused
Optimizely Web lets customers run experiments on their pages through a small JavaScript snippet. Each customer’s file can include an optional Project JavaScript field, where custom code runs across pages. Report URI said the attacker inserted code into that field in customer projects while leaving the rest of each snippet unchanged. The affected sites continued to load the file from an Optimizely address they already trusted. Report URI said its findings did not point to a content-delivery network cache-poisoning attack.
The published list covers organisations across sectors, including 32 in banking and finance, 23 in technology and software, and 20 in retail, according to Report URI. It includes well-known companies and institutions, but often identifies individual subdomains or tools rather than an organisation’s entire web presence. Hudson Rock explicitly warned that an affected subdomain alone does not establish exposure across a company’s other sites, products, customers or checkout systems.
Report URI also described an earlier wave beginning November 13, when an injector it attributed to the same actor appeared in scripts from Kissmetrics, StorifyMe and Minute Media. Those sites are separate from the list of 178 organisations. Hudson Rock 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 its status-page notice posted November 17
What the Investigation Has Not Established
Optimizely has not publicly explained the vulnerability’s technical mechanics or how a flaw in the Experimentation account signup flow enabled changes to many unrelated customer projects. Report URI said it could not determine how the attacker obtained write access at that scale; Hudson Rock said the disclosure did not explain the bug at code level.
It is also not known from the available reporting how many visitors had sensitive information captured, how many devices were successfully compromised, or whether any resulting fraud occurred. Report URI’s count of affected snippets is an observation from its sample, and its statement that the real total may be higher is an estimate, not a confirmed number. Likewise, the presence of a company or subdomain on the list does not establish that every visitor or service was affected.
Hudson Rock’s findings concern observed delivery, not proven iPhone infection. The published material also does not resolve how the earlier code reached the three other services. These distinctions matter: malicious capability, attempted delivery and confirmed harm are separate findings.
User Checks and Company Follow-Up
Visitors who used a listed site on November 16 should review recent payment and account activity, with extra attention to card details typed directly into website forms and cryptocurrency addresses copied while an affected page was open. If they see an unfamiliar transaction, login or account change, they should contact the financial institution or service through its official app or website. Users should install current device software updates, including the Apple versions cited by Report URI, and follow any direct notice from a company whose site they visited.
Optimizely’s immediate response, as reported, included fixing the flaw, removing injected code and revoking or resetting access. Further public details about the vulnerability and the investigation would help customers understand whether additional review is needed. Until those details or evidence of specific compromise emerge, the affected-site list should be treated as an indicator of possible exposure, not proof that a particular account or device was breached.
Key Questions
Does appearing on the affected list mean a company’s whole website was compromised?
No. The list can identify a particular subdomain or tool. Hudson Rock said that an affected subdomain does not establish exposure across an organisation’s entire website, products, customers or checkout system.
Does visiting an affected site mean my phone or account was hacked?
Not on the evidence reported. The code attempted several malicious actions, but delivery does not show that they succeeded for a particular visitor. Hudson Rock said its iPhone findings were delivery observations, not demonstrated device compromises.
What should visitors check after the incident?
Review bank, card, cryptocurrency and online account activity for unfamiliar transactions or changes. Update devices, and contact the relevant provider through its official channel if anything looks suspicious.
What did Optimizely say it did?
Optimizely said it fixed the vulnerability and removed injected code from affected projects. It also said it ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers.
How did the malicious code reach visitors?
Report URI said the attacker added code to the Project JavaScript field in customer projects. Websites then loaded the altered snippets from an Optimizely address they already trusted.
Source: ThorstenMeyerAI.com
