Optimizely Breach Pushes Malware to Zoom, BBC, CNN, and 175 Other Major Sites
Optimizely Compromised, Served Malware on Zoom, GitLab

On November 16, 2026, attackers injected malicious JavaScript into Optimizely's Project JavaScript field, compromising 188 snippets across 178 organizations including Zoom, BBC, CNN, Salesforce, and GitLab. The payload stole cryptocurrency by swapping wallet addresses, skimmed payment cards, harvested cookies and screenshots, and delivered iOS exploit kits to iPhones and iPads. Over $7,000 in crypto was stolen before cleanup. The attack exploited trust in a third-party CDN, not a flaw in any victim's own infrastructure.
The important lesson here is that trusted JavaScript doesn't always remain trustworthy.
- stickfigure
The whole concept of Google Tag Manager was that you could give marketing departments the ability to add "tags" to the website without having to involve engineering. That's how we got 10MB of javascript with every news article.
I hope folks are re-evaluating that now.
- mcoliver
This stuff is so avoidable but unless we implement meaningful reprocussions things aren't going to change. There is no accountability.
In this case optimizely should have had better systems to spot a release like this (internal cool downs, check and balances, phased rolouts, automatic security checks). And sites that have massive user bases (cnn, bbc, etc..) have zero excuse to not have the same.
I would go so far as to say those sites should not be serving from vendors but should be vendoring their own scripts that they also are passing through security audits and serving them selves with cool downs.
How do these companies not have better dedication to protecting their users is beyond me.
- eax-eip
> We don't know how the attacker got write access to so many unrelated customer projects: a compromised Optimizely system, a compromised credential with cross-customer access, or something else. That's for Optimizely to explain. To be clear, Optimizely's CDN served exactly what it was given; this was not a CDN cache-poisoning attack. Optimizely's own sites were affected as well: the snippets for www.optimizely.com and login.optimizely.com both carried the code.
Interesting that it is not necessarily a supply chain attack a la LiteLLM/some of the other recent breaches. Possibly just a mass compromise of customer passwords.
- skybrian
There's a missing step in the explanation. Do major websites like CNN and BBC handle cryptocurrency or credit cards on the same website? Why? Or is there also a browser security bug?
- thought-gap
This is exactly the kind of use case for NoScript - reduce exposure to potentially malicious content.
- mattmatters
Optimizely is a pretty garbage platform so this is unsurprising. Love the work though folks like report uri are doing finding this.
- mcoliver
This stuff is so avoidable but unless we implement meaningful reprocussions things aren't going to change. There is no accountability.
In this case optimizely should have had better systems to spot a release like this (internal cool downs, check and balances, phased rolouts, automatic security checks). And sites that have massive user bases (cnn, bbc, etc..) have zero excuse to not have the same.
I would go so far as to say those sites should not be serving from vendors but should be vendoring their own scripts that they also are passing through security audits and serving them selves with cool downs.
How do these companies not have better dedication to protecting their users is beyond me.
- Animats
Why should browsers be allowed to read or write user files without user intervention and serious warnings?