TL;DR
Report URI researcher Scott Helme says malicious JavaScript was served to visitors of 178 organisations through Optimizely Web on November 16, 2026. Optimizely says an unauthorized party exploited a vulnerability to place code in some customer projects and that it fixed the flaw and removed the code. The code attempted several forms of data theft and iPhone exploit delivery, but confirmed device compromises have not been established.
Malicious JavaScript reached visitors to 178 organisations through the Optimizely Web experimentation platform on November 16, according to security researcher Scott Helme of Report URI. Optimizely says an unauthorized party exploited a vulnerability to add code to some customer projects, creating a supply-chain incident that exposed visitors of affected websites to scripts intended to steal information and deliver iPhone exploits.
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Report URI says it examined 1,611 Optimizely snippets and found malicious code in 188. The report counts 178 organisations among those affected and says the true number may be higher. These figures describe the researcher’s inspection and findings; the source material does not establish a final, independently verified count of all affected sites or visitors.
The code was added to the Project JavaScript field in customer projects, Report URI says. Websites continued to load the file from Optimizely’s trusted address, and the rest of each snippet was left intact. The code attempted to replace cryptocurrency wallet addresses on webpages and in clipboard activity, capture payment-card details entered into site forms, and collect cookies and screenshots. Report URI also observed delivery attempts involving the Coruna and DarkSword exploit kits aimed at iPhones and iPads.
Report URI first observed an injection at 04:21 UTC on November 16. It says the infected Optimizely files had all been cleaned by 23:11 UTC that day. Optimizely’s status-page notice appeared at 01:02 UTC on November 17. The company says it fixed the vulnerability and removed injected code from affected projects; it also told BleepingComputer it had notified affected customers, ended active sessions, revoked tokens and reset access for affected accounts.

How a Trusted Script Reached Visitors
The incident illustrates how a flaw at a web-services provider can expose people who visit customer sites, even when those sites have not themselves been hacked. Organizations had intentionally loaded Optimizely’s script for experimentation. When malicious code was placed in the vendor-hosted project file, the browser treated it as part of the site’s regular page content.
That route matters to businesses and users because the attempted actions targeted information entered or stored in the browser, including card details, cookies and clipboard contents. A visitor might have no visible reason to suspect that a familiar brand’s webpage was loading a compromised third-party script. The report describes what the code attempted, however, not proof that every target was successfully affected.
Report URI also assessed security policies on affected organisations’ sites. It says 24 of 159 blocked the code, while 68 had no policy in place. This suggests some site-level controls may have limited execution, but the source does not establish that a particular policy would have prevented every part of this incident. The figures are specific to the sites and checks in Report URI’s review.
Products Worth Considering

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black

Jackery Explorer 1000 v2 Portable Power Station, 1024Wh LiFePO4 Battery

Samsung 27-Inch Odyssey G5 QHD Gaming Monitor (G50F)
As an affiliate, we earn on qualifying purchases.
Inside the Optimizely Injection
Optimizely Web uses a small JavaScript snippet loaded by a customer’s website. Customers can use a field called Project JavaScript to add code that runs on their pages. Report URI says the attacker inserted code into that field while leaving the rest of the snippet untouched. Because the file still came from an address the websites already trusted, allowing that address did not, by itself, stop the injected code.
Report URI says this was not a CDN cache-poisoning attack. Optimizely’s status-page account attributes the incident to a vulnerability in its Experimentation service. The company told BleepingComputer the flaw was in the Experimentation account signup flow. The available statements do not explain in technical detail how that flaw allowed changes to unrelated customer projects.
Report URI’s timeline records changing capabilities during November 16: address-swapping code appeared at 08:28 UTC, a card skimmer at 13:43 UTC, and wider iPhone exploit delivery at 17:13 UTC. The same report notes an earlier wave on November 13 involving scripts from Kissmetrics, StorifyMe and Minute Media. That earlier activity is separate from the Optimizely incident and does not establish that the providers shared an attacker or cause.
““An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.””
— Optimizely, in its November 17 status-page notice
What the Investigation Has Not Established
The total reach remains uncertain. Report URI found malicious code in 188 snippets among 1,611 it checked, associated those findings with 178 organisations, and said the real number could be higher. The source material does not provide a confirmed count of individual visitors exposed, successful data thefts, or organisations beyond those identified by the researcher.
It is also not clear how the signup-flow vulnerability enabled access to many separate customer projects. Report URI says it does not know how the attacker obtained write access across unrelated accounts, while Hudson Rock says Optimizely’s disclosure did not explain the bug’s code-level mechanics. Optimizely’s reported response actions do not answer those questions.
No iPhone compromise has been demonstrated in the cited findings. Report URI recommends updating to iOS 18.7.3 or later, or iOS 26.3 or later, but Hudson Rock cautions that its evidence concerns exploit delivery rather than confirmed device infections. The source material also does not say whether any card data, credentials, cookies or cryptocurrency were successfully stolen.
Customer Review and Security Follow-Up
Optimizely says it fixed the vulnerability, removed injected code from affected projects and notified affected customers. It also told BleepingComputer that it ended active sessions, revoked tokens and reset access for affected user accounts. The company’s public statements cited here do not set out a schedule for a fuller technical account or describe any continuing investigation milestones.
Organisations that used Optimizely during the affected period will need to review the vendor’s notices and their own records to determine whether their projects were involved and what response is appropriate. Visitors concerned about the attempted iPhone exploit delivery can follow the operating-system update guidance cited by Report URI. The next key information would be a clearer explanation of the vulnerability, the confirmed scope of affected projects and any evidence of successful theft or device compromise.
Key Questions
Were the 178 organisations’ websites themselves hacked?
Report URI says the code arrived through Optimizely’s trusted script, not because each organisation’s own site was hacked. Optimizely says an unauthorized party exploited a vulnerability to add JavaScript to some customer projects.
What information did the malicious code try to collect?
According to Report URI, it attempted to replace cryptocurrency wallet addresses, capture card details entered into website forms, and collect cookies and screenshots. These are reported capabilities and targets, not proof that data was successfully stolen.
Were iPhones confirmed to be compromised?
Not in the cited findings. Hudson Rock described its evidence as observations of exploit delivery, not demonstrated iPhone compromises. The source material does not establish that any device was successfully infected.
What has Optimizely said it did?
Optimizely says it fixed the vulnerability and removed injected code from affected projects. It also told BleepingComputer that it notified affected customers, ended active sessions, revoked tokens and reset access for affected user accounts.
How many sites or visitors were affected?
Report URI says it found code in 188 of 1,611 snippets it checked and linked the findings to 178 organisations. It said the actual number may be higher. A confirmed count of exposed visitors or successful compromises has not been provided in the source material.
Source: Thorsten Meyer AI
