Attackers exploit a Web Experimentation platform to embed malicious code that harvests payment-card data, cryptocurrency details, cookies, screenshots…
On 16 November 2026 a supply-chain attack exploited a vulnerability in Optimizely’s Web Experimentation platform, causing malicious JavaScript to be served to visitors of websites belonging to 178 organizations, including the BBC, CNN, Zoom, Salesforce, HSBC, IKEA and Equifax (Note: URLs to these entities are not embedded in case of attack recurrence.)
Security researcher Scott Helme and his firm, Report URI, had disclosed details of the incident.)
The team said it had identified 188 infected Optimizely JavaScript files after analyzing 1,611 scripts associated with the platform. The malicious code was injected into customer “Project JavaScript”, which then affected websites loaded from Optimizely’s content delivery network.
What the code did
Once loaded in a visitor’s browser, the JavaScript attempted to replace copied cryptocurrency wallet addresses with attacker-controlled addresses, capture payment-card details entered into forms, steal cookies and take screenshots. It also attempted to deliver the Coruna and DarkSword exploit kits to vulnerable iPhones and iPads.
The attack did not necessarily mean that each of the 178 organizations had suffered a direct breach of its own systems. Rather, a third-party service used by those organizations was abused to distribute malicious code to their visitors, according to MacRumors.
Why it matters
Optimizely has confirmed that an unauthorized party exploited a vulnerability in its Experimentation product to add malicious JavaScript to some customer projects. The firm said it has fixed the vulnerability, removed the injected code, secured affected accounts and engaged third-party investigators.
The episode illustrates how a compromise in a widely-used website-testing or personalization service can expose visitors across many unrelated organizations. Because the malicious JavaScript was delivered through a trusted third-party domain, it could run on affected pages without attackers needing to compromise each company’s web infrastructure directly, as explained by a ComputerWorld report.
Security teams should audit third-party scripts, limit which script sources can load on sensitive pages, and avoid exposing checkout or authentication fields to unnecessary marketing, analytics and experimentation tags.
