TL;DR
Optimizely confirmed that an attacker exploited a vulnerability to add malicious JavaScript to some customer projects. Report URI says the code was served to visitors of 178 organisations on Nov. 16 and attempted to steal information and redirect some iPhones to exploit kits. The infected files were cleaned, but confirmed victim numbers and whether any devices were compromised remain unknown.
Optimizely confirmed on Nov. 17 that an unauthorized party exploited a vulnerability in its Experimentation product to add malicious JavaScript to some customer projects. Security researcher Scott Helme’s Report URI said the script was served to visitors of 178 organisations on Nov. 16, including visitors to sites run by major companies and media outlets; the code attempted to steal data and deliver iPhone exploit kits.
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 said it checked 1,611 Optimizely snippets and found the malicious code in 188. Its count of organisations reached was 178, and the researcher cautioned that the actual number may be higher. The affected sites did not necessarily have their own systems breached: the code arrived through a JavaScript file their pages loaded from Optimizely, a vendor used for web experiments.
According to Report URI, the attacker inserted code into the Project JavaScript field in customer projects. The script attempted to replace cryptocurrency wallet addresses on web pages and in copied clipboard data, capture payment-card details entered into site forms, and collect cookies and screenshots. Report URI also documented delivery attempts involving the Coruna and DarkSword exploit kits, which target older iPhones and iPads.
Report URI first observed an infected Optimizely file at 04:21 UTC on Nov. 16. It said all infected Optimizely files had been cleaned by 23:11 UTC that day. Optimizely’s status-page update at 01:02 UTC on Nov. 17 said the company had fixed the vulnerability and removed injected code from affected projects. The company also told BleepingComputer it had ended active sessions, revoked tokens and reset access for affected accounts.

Risks for Site Visitors and Businesses
The incident shows how a security problem at a third-party service can expose visitors across many otherwise separate websites. Because the script came from an address the sites had deliberately trusted, visitors and site operators could have difficulty distinguishing the malicious code from the vendor’s expected content. The report says the organisations themselves were not necessarily hacked.
For visitors, the reported behavior makes recent activity worth checking, especially if they used a cryptocurrency wallet or entered payment details on an affected site during the exposure window. That is a precaution, not evidence that a particular person’s information was stolen. For businesses, the event highlights the limits of trusting a vendor script without additional controls: Report URI said only 24 of 159 organisations it reviewed blocked the code through their security policies, while 68 had no such policy. Those figures describe its review sample, not every affected organisation.
Products Worth Considering

Logitech MX Creative Console with 9 Customizable Keys, Graphite

DJI Mini 5 Pro Fly More Combo with DJI RC 2, 1-Inch CMOS

Jackery Explorer 1000 v2 Portable Power Station, 1024Wh LiFePO4 Battery
As an affiliate, we earn on qualifying purchases.
How the Trusted Script Was Abused
Optimizely Web delivers a JavaScript snippet that customer sites use to run experiments. Report URI says the attacker placed malicious code in the Project JavaScript field, which can run on pages where the customer’s snippet is loaded. The file continued to come from Optimizely’s usual address, making the alteration less visible to a website that trusted that source.
Report URI said the incident was not a CDN cache-poisoning attack. Its timeline also records earlier malicious activity through scripts associated with Kissmetrics, StorifyMe and Minute Media on Nov. 13. The source material does not establish whether those incidents had the same cause or were connected to the Optimizely activity.
Optimizely said the vulnerability was in the Experimentation account signup flow. The company’s public update did not provide technical details about how that flaw enabled access to customer projects. Report URI said Optimizely’s own websites also carried the malicious code.
“An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.”
— Optimizely, in its status-page update on Nov. 17
What Researchers Have Not Confirmed
Neither the number of people whose data was accessed nor the number of successful compromises has been established in the supplied reporting. Hudson Rock said its findings on iPhones were observations of exploit delivery, not proof of device compromise. Report URI’s count of snippets and organisations is its own assessment, and it said the full reach may be larger.
The precise mechanics of the signup-flow vulnerability also remain undisclosed. Optimizely said it fixed the flaw and took steps to reset access, but its statements did not explain how the attacker gained write access to unrelated customer projects or list all affected customers publicly. The available material does not confirm whether any payment information, cryptocurrency or account credentials were actually taken.
Checks for Visitors and Site Operators
Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. Users who entered card details on an affected site during the incident can review transactions and contact their card issuer if they find unfamiliar activity. Cryptocurrency users should verify wallet addresses carefully before confirming transfers, particularly if they copied an address from a page during the exposure period.
These steps are precautionary and do not mean an account or device was affected. Site operators should check Optimizely’s notices, confirm their projects and access credentials are secure, and review browser security policies that can restrict scripts from trusted vendors. Optimizely says affected customers were notified, but the supplied sources do not give a public list of those customers.
The next useful updates would clarify the vulnerability’s technical cause, the full set of affected projects and whether investigations found confirmed data theft or device compromise. Until those details are published, the reported delivery and attempted behaviors should not be treated as proof that every visitor to an affected site was harmed.
Key Questions
Were the websites themselves hacked?
Not necessarily. Report URI said the malicious code was delivered through an Optimizely script that customer sites had chosen to load. Optimizely confirmed an attacker exploited a vulnerability to alter some customer projects.
Was my iPhone compromised?
The available reporting does not establish that any particular iPhone was compromised. Hudson Rock described its findings as observations of exploit delivery, not demonstrated device compromises. Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later.
What did the malicious code try to do?
According to Report URI, it attempted to replace cryptocurrency wallet addresses, capture card details entered into site forms, collect cookies and screenshots, and send some iPhones or iPads to exploit kits.
How many organisations were affected?
Report URI said it found the code in snippets associated with 178 organisations and in 188 of 1,611 Optimizely snippets it checked. The researcher said the real number may be higher. These findings do not establish how many visitors were affected or suffered data loss.
What should visitors do now?
Keep Apple devices updated, review card transactions if you entered payment details on an affected site during the incident, and verify cryptocurrency addresses before sending funds. These are precautions; the sources do not confirm that every visitor’s information or device was compromised.
Source: Thorsten Meyer AI
