On 16 November 2026, threat actors exploited a vulnerability in Optimizely’s Web Experimentation platform to inject malicious JavaScript into customer projects, in a supply-chain campaign dubbed OPTIMJACK. The compromised scripts were delivered through Optimizely’s legitimate content delivery network, causing websites operated by at least 178 organizations to serve the malicious code to visitors. Affected organizations included major brands such as the BBC, CNN, Zoom, Salesforce, GitLab, HSBC and IKEA. The attackers exploited a flaw in the platform’s account signup flow to impersonate customer users and modify project code. Optimizely confirmed that the incident did not involve stolen customer passwords or a compromised administrator account.
The injected JavaScript was designed to replace cryptocurrency wallet addresses with attacker-controlled addresses and capture payment card details entered into forms directly on affected websites. It also collected certain page information, including cookies and screenshots in connection with cryptocurrency address manipulation. A separate payload targeted iPhones and iPads running older versions of iOS and iPadOS, attempting to deliver additional exploit code. Optimizely reported that the first malicious code was written at 07:51 UTC on 16 November. The company detected the activity at 13:34 UTC, fixed the vulnerability at 16:10 UTC and removed the injected code from all affected projects by 22:24 UTC. The company said hosted payment iframes, such as those used by Stripe and Adyen, were outside the skimmer’s reach. The investigation remained ongoing, and the number of visitors whose information was successfully stolen had not been established.
The incident highlights the risks posed by trusted third-party scripts that execute directly in users’ browsers. A compromise of a single service provider allowed attackers to reach visitors across numerous organizations without directly breaching each organization’s infrastructure. Organizations using Optimizely Web Experimentation should review project modifications and website activity during the exposure window, assess whether affected pages handled payment or cryptocurrency transactions, and investigate suspicious outbound browser connections. Security teams should also enforce restrictive Content Security Policies, limit third-party scripts on sensitive pages and isolate payment collection through secure, cross-origin iframes.