Optimizely has published the root cause, timeline and preliminary infrastructure for its Web Experimentation compromise.
What changed
Treat the Optimizely event as a confirmed third-party script compromise requiring customer-specific incident evidence. Optimizely has published the root cause, timeline and preliminary infrastructure for its Web Experimentation compromise. The affected product was Optimizely Web Experimentation; Optimizely says Feature Experimentation, SDKs and legacy Full Stack were not affected.
Public record through 2026-11-18. Source references count citations across published briefings, including repeated sources. Explore the record and its limits →
What We Publish / What We Sell
D
Free · Public
The Daily
Five evidence-backed selections for security leaders, every weekday.
Security.io editorial scores use a 0–100 scale and are not source metrics. Exposure reflects dependency reach, urgency reflects the current investigation window, and business consequence reflects payment, privacy and notification impact. Exposure: 96. Urgency: 94. Business consequence: 95. Focus the chart and use the up and down arrow keys for detail. Source: Security.io editorial assessment informed by Optimizely, Report URI and Palo Alto Networks Unit 42.