Timeline

What happened, in order

  1. DiscoveredInvestigating

    Report URI's investigation found 188 infected Optimizely Web snippets across 178 organizations serving several malicious payloads.

    via Primary investigation
  2. MitigationMonitoring

    Most observed scripts were clean by the investigator's final sweep. Total impact is unknown.

    via BleepingComputer
  3. Permanent fixMonitoring

    Optimizely confirmed the exploitation of an Experimentation vulnerability and stated that it fixed the vulnerability, removed injected code, secured affected accounts and added protections. Report URI observed all previously infected snippets clean by November 16 at 23:11 UTC and reported attacker domains being disabled. The number of affected visitors and final exposure remain unknown.

    via Optimizely Web Experimentation Security Incident & Report URI November 17 follow-up

Root cause

Confirmed cause

Optimizely confirmed exploitation of a vulnerability in its Experimentation platform that allowed unauthorized insertion of JavaScript into customer projects. It has not published the detailed initial access or vulnerability mechanics.

via Optimizely Web Experimentation Security Incident

Permanent fix

Shipped November 17, 2026

Optimizely states it fixed the exploited vulnerability, removed malicious code from affected customer projects, secured affected accounts and added safeguards against unauthorized code delivery; technical specifics and independent validation of the permanent fix are not yet published.

Postmortems

None published yet

An official or independent postmortem will be linked here when one appears.