Optimizely Hack: What QA Should Test in Third-Party Scripts
Photo: Sai Kiran Anagani, " CSS code on a screen ", CC0 , via Wikimedia Commons. On Sunday 16 November 2026, visitors to Zoom, the BBC, CNN, Salesforce, GitLab and well over a hundred other big websites were served malware. None of those companies had their own servers hacked. The bad code arrived inside a script they already trusted: the snippet from Optimizely, a popular A/B testing and experimentation platform. This week's breakdown covers what we know about the Optimizely hack, what we still don't know, and, most importantly, what QA and web teams should test so that a trusted third-party script can't quietly turn your checkout into a skimmer. What happened in the Optimizely hack Optimizely Web Experimentation works by loading a JavaScript snippet from Optimizely's CDN on every page of a customer's site. That snippet carries Optimizely's own code, the customer's experiments, and an optional field called Project JavaScript, which is custom ...