TL;DR
Optimizely confirmed that an unauthorized party exploited a vulnerability to add malicious JavaScript to some customer projects. Report URI found the code in scripts associated with 178 organizations; it attempted to redirect crypto payments, capture payment data and deliver exploit kits to iPhones and iPads. Researchers have not shown that any iPhone was compromised.
Optimizely confirmed that an unauthorized party exploited a vulnerability to add malicious JavaScript to some customer projects, code that Report URI says was served to visitors of 178 organizations on November 16. The injected script attempted to alter cryptocurrency wallet addresses, capture payment information and direct some iPhone and iPad users toward exploit kits, though researchers have not demonstrated that an Apple device was compromised.
Get hardware and tech essentials delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Security researcher Scott Helme of Report URI said the code was delivered through Optimizely Web, a platform companies use to test variations of their websites. Organizations had deliberately added Optimizely’s script to their sites; according to Report URI, the malicious code was inserted into customer projects while the surrounding script continued to be served from the trusted Optimizely address. The affected sites were not necessarily hacked directly.
Report URI said it checked 1,611 Optimizely snippets and found malicious code in 188. Its report identified visitors to 178 organizations as having received the code and cautioned that the actual number could be higher. The code was seen from 04:21 UTC on November 16; Report URI said all infected Optimizely files had been cleaned by 23:11 UTC, about 19 hours later.
According to Report URI, the script attempted to replace crypto wallet addresses on webpages and in clipboard contents, collect card numbers entered into site forms, and take cookies and screenshots. It also directed some Apple-device traffic toward the Coruna and DarkSword exploit kits. Optimizely said it fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens and reset access for affected accounts.

Risks Across Trusted Website Scripts
The incident shows how a compromise at a third-party web service can expose visitors across many otherwise unrelated organizations. A site can load a vendor script for legitimate functions, but code added to that script may run in visitors’ browsers with access to information they enter or see on the page. A familiar brand or secure-looking web address does not, by itself, establish that every script loaded by the site is safe.
For crypto users, the reported address-changing behavior could matter if a visitor copied or followed a substituted wallet address while making a payment. Cryptocurrency transfers are often difficult or impossible to reverse, so users should independently check the destination address before confirming a transaction. For shoppers and account holders, the reported form-skimming behavior could put payment details at risk if they were entered on an affected page during the exposure window. The source material does not establish that stolen data was successfully used.
The iPhone component also warrants careful wording. Hudson Rock said its findings were delivery observations, not demonstrated iPhone compromises. The report indicates an attempted route to exploit kits, not proof that a device was infected or that its owner’s data was taken. Apple-device users should keep software updated; this report does not establish that all iPhones or all visitors to the named organizations were affected.
Products Worth Considering

Bose Portable Smart Speaker with Alexa and Google Assistant, Black

Jackery Explorer 300 Portable Power Station, 292Wh

Samsung 27-Inch Odyssey OLED G5 QHD Gaming Monitor (G50SF)
As an affiliate, we earn on qualifying purchases.
How the Optimizely Script Was Used
Optimizely Web provides customer-specific snippets that sites load to run experiments and other page features. Report URI said the attacker added code to a customer project’s Project JavaScript field, which can run across that customer’s pages. Because the script still came from an address the sites already trusted, simply permitting the Optimizely address did not block the injected code.
Optimizely’s November 17 status-page notice said an unauthorized party exploited a vulnerability in Experimentation and used it to add JavaScript to some customer projects. The company told BleepingComputer the flaw was in the Experimentation account signup flow and said it had notified affected customers. Report URI said the incident was not a content delivery network cache-poisoning attack. The source also describes an earlier, separate wave on November 13 involving scripts from Kissmetrics, StorifyMe and Minute Media; that earlier activity should not be confused with the Optimizely incident.
Report URI also examined affected organizations’ security policies: it said 24 of 159 blocked the code, while 68 had no policy. Those figures describe the organizations it checked, not all Optimizely customers or all websites. They point to a limitation of policies that trust a vendor’s script address: those policies may permit harmful code if that vendor’s own delivery or customer-project controls are compromised.
“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 Shown
The available accounts do not say how the signup-flow vulnerability gave the attacker write access to numerous customer projects, or how many people viewed a page while the code was active. Report URI’s count of 178 organizations reflects its findings, and the researcher said the total could be higher; it is not a confirmed count of people affected or of successful thefts.
It is also unclear whether any crypto address was successfully replaced in a transaction, whether card details or session cookies were collected and misused, or whether any iPhone or iPad was successfully compromised. Hudson Rock explicitly described its iPhone findings as delivery observations. The source material reports what the code attempted, not confirmed financial losses, stolen information or device infections.
Customer Reviews and Security Updates
Optimizely said it had fixed the vulnerability, removed the injected code, notified affected customers and revoked or reset access tied to affected accounts. Customers using Optimizely should review the company’s notices and examine their own project configurations and logs for activity during the November 16 exposure period. The source material does not give a date for a final investigation report or say whether Optimizely plans to publish further technical findings.
Visitors who entered payment information or handled a crypto transaction on a potentially affected site during the window can check relevant account and transaction activity and contact the service or payment provider if they see anything suspicious. For Apple devices, Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later; users should check Apple’s current update information for their device. These steps do not establish that a particular visitor was affected. The extent of any data theft or successful device compromise remains unconfirmed.
Key Questions
What happened in the Optimizely incident?
Optimizely said an unauthorized party exploited a vulnerability to add malicious JavaScript to some customer projects. Report URI found the code in scripts associated with 178 organizations on November 16, 2026.
Were iPhones confirmed to be hacked?
No confirmed iPhone compromises are reported in the source material. Hudson Rock said it observed delivery of exploit-kit content, not demonstrated infections of iPhones.
Could crypto users have lost funds?
Report URI said the code attempted to replace wallet addresses on webpages and in clipboard contents. The available reporting does not confirm that a transaction was redirected or funds were lost. Crypto users should check destination addresses carefully before approving transfers.
Were payment card details or cookies stolen?
The code reportedly attempted to capture card numbers entered into website forms and collect cookies. The source material does not establish whether information was successfully collected or misused.
What should visitors do now?
Check transactions and account activity from the exposure period, contact a relevant provider if anything looks suspicious, and install current software updates. These general precautions do not mean a specific visitor was affected.
Source: Thorsten Meyer AI
