Trending: On-device modelsSearch
iHeartGeek
iTECH

Optimizely says malicious JavaScript hit customer projects

Optimizely says a vulnerability let an unauthorised party add malicious JavaScript to some customer projects before the company removed the code and secured affected accounts.

Official Optimizely vendor image used to represent the company in a security incident report

Optimizely says an unauthorised party exploited a vulnerability in its Experimentation service and used it to add malicious JavaScript to some customer projects. The company says the incident affected Web Experimentation's snippet delivery, the system that places Optimizely code on customer websites.1

According to Optimizely's incident notice, the company fixed the vulnerability, removed the injected code from affected projects and secured affected user accounts. It also says it has added protections intended to prevent unauthorised code from being delivered again.1

The notice was posted on 17 November 2026 at 1:02 a.m. UTC and was marked as monitoring rather than fully resolved. That status means Optimizely was continuing to watch the situation after applying its immediate fixes. The company's notice does not provide a final victim count, a complete forensic timeline or a full account of what the injected scripts did, so those points should not be treated as settled.1

Our opinion

The important distinction here is between fixing the delivery mechanism and proving the full impact. Optimizely says it removed the injected code and secured affected accounts, which is a meaningful response, but customers still need a clear incident timeline and practical guidance on checking their own projects. Until that detail is published, organisations using Web Experimentation should review recent snippet changes, rotate credentials where appropriate and treat the company's remediation statement as an update rather than the final word.1