Skip to content
TrustList
Security advisories

Attacker injected malicious JavaScript into Optimizely customer projects

Editorial

By TrustList Editorial

The experimentation vendor says it has fixed the flaw and removed the code; a researcher counted 188 infected scripts, a figure Optimizely has not confirmed.

About Attacker injected malicious JavaScript into Optimizely customer projects

Attacker injected malicious JavaScript into Optimizely customer projects

17 November 2026: Optimizely says an unauthorised party exploited a vulnerability in its Web Experimentation product and used it to add malicious JavaScript to some customers' projects, code that would then have run in the browsers of visitors to those customers' websites. The company says it has fixed the flaw, which has no CVE number, and removed the injected code; it has not said how many customers were affected or for how long.

Not yet independently verified. Optimizely's status notice of 17 November 2026 does not name the vulnerability, the number of customers affected or the period of exposure, and gives customers no instructions. The counts of infected files and organisations, and the description of what the injected code did, come from a researcher quoted by BleepingComputer; we have not read the researcher's own write-up. We will update this when it can be confirmed, and remove this note.

What Optimizely has confirmed

The statement is an entry on the company's status page, opened early on 17 November UTC against the Snippet Delivery component of Web Experimentation and marked as being monitored. It reads: "Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. We've fixed the vulnerability and removed the injected code from affected projects. We've also taken steps to secure affected user accounts and put additional protections in place".

That is the whole of the vendor's account so far. It gives no technical description, no list of affected customers and no advice.

What a researcher reports

BleepingComputer reports the findings of the security researcher Scott Helme, who examined 1,611 Optimizely scripts on 16 November and found 188 of them infected, belonging to 178 organisations. By his account the injected code loaded a second script from an outside server that could swap cryptocurrency addresses, skim payment card details, and take cookies, page addresses and screenshots. He found one of the 188 files still infected late on 16 November.

These figures are the researcher's, relayed by the press. Optimizely had not answered the outlet's questions when it published, and it is not yet clear how one flaw gave access to so many separate customer projects.

Why an experimentation snippet is a high-value target

An A/B testing tool works by loading a script from the vendor on every page under test, and that script is designed to rewrite the page. Whoever controls it controls what the visitor sees and types. That makes the snippet as sensitive as the site's own code, although it is usually added by a marketing team and reviewed by nobody in security.

Checks for a site that loads the snippet

Optimizely's notice asks nothing of customers, so the following is drawn from the nature of the incident, not from the vendor.

A site owner can compare the project's current custom code and experiment code in the Optimizely console against what the team wrote, and review the project's change history and user list for entries nobody recognises. Web server and content security policy reports for 16 November will show whether browsers were asked to load scripts from an unfamiliar host. If the site takes payments on pages that carry the snippet, the payment provider and the card scheme rules on reporting apply, and the question to put to Optimizely in writing is whether the project was among those altered.

A longer-term control is a content security policy that limits which hosts a page may load scripts from, which would have stopped the second-stage script.

Our A/B testing software category lists 11 products that work the same way and carry the same exposure. Optimizely's status entry remains open and is the place where an update will appear.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in

The French regulator's final recommendation covers the vendors that build replay tools and the sites that run them. No exemption applies, purposes must be set before collection, and mouse movement should be masked where login codes are typed.