Optimizely confirms malicious JavaScript in customer projects

Contents
At a glance
Optimizely says it removed injected JavaScript. Separate research describes cryptocurrency address swapping; the full extent of visitor losses remains unclear.
What the provider confirmed
Optimizely has confirmed that an unauthorized party exploited a vulnerability in Experimentation to insert malicious JavaScript into some customer projects. In a notice posted on November 17 at 01:02 UTC, the company said it had fixed the vulnerability, removed the injected code and taken steps to secure affected accounts. The incident remained under monitoring when checked.
The notice identifies Web Experimentation snippet delivery as the affected service. It does not provide a complete list of affected visitors or a verified total of financial losses. Its statement that the code was removed describes the provider’s remediation, rather than proving that every consequence for earlier visitors has been resolved. [1][3]
How trusted scripts reached visitors
A separate technical investigation by Report URI describes malicious code observed on November 16. The researchers say the attacker modified the Project JavaScript field in customer projects. The resulting snippets continued to arrive from the trusted Optimizely domain; the report distinguishes this from poisoning a CDN cache.
According to that investigation, the payload could replace cryptocurrency addresses in page content and clipboard operations. It also describes collection of payment-card data from forms on the affected page. These are findings attributed to the researchers, not proof that every visitor made a payment or lost funds. A familiar website address alone therefore cannot establish that every script running inside the page remained unchanged. [2]
What the evidence does not establish
The two sources answer different questions. Optimizely confirms unauthorized modification and reports its response. Report URI explains observed script behaviour. Neither provides a complete, independently verified account of all affected users and their losses. A count of modified scripts or customer organisations must not be presented as a count of people whose money was stolen.
For site owners, the practical question is whether their own project served the modified code during the relevant period. For a reader checking a transfer, it is whether the actual destination matches the intended recipient, rather than whether the page looked familiar. The vendor notice and the technical investigation should be read together, with their different evidence limits kept explicit. [1][2][3]
Evidence & sources
Source record: · Checked:
Record limits · Optimizely says it removed injected JavaScript. Separate research describes cryptocurrency address swapping; the full extent of visitor losses remains unclear.
- Source reported
Optimizely reports malicious JavaScript in customer projects and remediation.
Supporting excerpt: Optimizely: Web Experimentation security incident
removed the injected code
Optimizely: Web Experimentation security incident ↗ - Source reported
Report URI describes changes to Project JavaScript and cryptocurrency address swapping.
Supporting excerpt: Report URI: investigation of the Optimizely incident
Project JavaScript
Report URI: investigation of the Optimizely incident ↗ - Source reported
The official notice identifies Web Experimentation snippet delivery.
Supporting excerpt: Optimizely: Web Experimentation security incident
Web Experimentation (Snippet Delivery)
Optimizely: Web Experimentation security incident ↗


