TL;DR: Would a Content Security Policy have stopped the Optimizely malware?
On 16 November 2026 malicious JavaScript rode inside Optimizely snippets onto the sites of 178 organisations. A Content Security Policy (CSP) stopped it at only 24 organisations, and 68 had no CSP at all. Allowing cdn.optimizely.com did nothing, and 'unsafe-eval' and 'strict-dynamic' opened the door. On client sites, start in report-only mode, restrict connect-src, read the reports, then enforce.
Developing story. Last updated 17 Nov 2026, 11:30 CET. We'll update this article as Optimizely publishes more.
Turn your skills into your first startup
The Fe/male Switch startup game takes you from idea to first paying customers in weekly quests, with an AI co-founder and a community of founders.
👉 Start the game