ReportURI identified 188 malicious scripts among 1,611 Optimizely scripts examined, associated with 178 organizations. The code was served through Optimizely’s legitimate infrastructure and targeted cryptocurrency addresses, payment-card data, browser information and iOS devices. ReportURI said its list of organizations might not be exhaustive.
A script can arrive through a trusted service and still carry malicious code if the script served there has been altered.
What the 178-organization finding counts
The 178 figure is the number of organizations associated with malicious scripts identified by ReportURI. In the sample reported later, researchers found 188 malicious scripts among 1,611 Optimizely scripts they examined. Those figures describe the investigation’s script findings and associated organizations.
How the code reached websites
The altered customer JavaScript was delivered through Optimizely’s legitimate infrastructure and a valid domain certificate. ReportURI described the incident as distinct from CDN cache poisoning: the service delivered modified scripts through its own system.
A subsequent account relayed Optimizely’s explanation that an unauthorized party exploited a vulnerability in the Experimentation account-signup flow to add JavaScript to customer projects. Optimizely said it blocked access to the vulnerable path and deployed a fix. The company also said it removed injected code, ended active sessions, revoked tokens and notified affected customers.
What the code tried to do
The reported code had several functions:
- It searched for addresses for nine cryptocurrencies and replaced matching addresses with ones controlled by the attackers. ReportURI said some funds had been stolen.
- It watched site-controlled payment requests for card numbers, expiration dates and CVVs. Cards entered in hosted payment iframes such as Stripe and Adyen were reported unaffected by this component.
- Under the described address-swapping conditions, it collected browser cookies and page screenshots.
- It delivered iOS exploit-kit stages. Coruna was reported for iOS 13–17 and DarkSword for iOS 18.x; a separate iOS 26 chain fingerprinted devices.
The reported iOS behavior was conditional exploit delivery. For separate context on reported crypto-loss figures tied to iPhone users, see NeoTeo’s earlier comparison of two reports.
What was reported about the timeline
The first malicious injection was reported on a BBC script at 04:21 UTC on November 16, 2026. ReportURI said all infected Optimizely files were clean by 23:11 UTC that day.