Attackers Used Optimizely to A/B Test Malware on Top Websites

Curated from Krebs on Security

Third-party JavaScript is production code you don't control, and this incident shows what that costs. When an experimentation or personalization vendor is compromised, every site that loads its tag inherits the attack, however well hardened its own servers are. The core issue is less about one vendor than about the trust we default to for scripts that run inside our pages with full access to the DOM. Teams often treat a testing snippet as configuration rather than as a dependency, so it rarely gets reviewed, pinned, or monitored. That makes it an attractive path for attackers who want to reach many unrelated brands through one upstream component. The article is worth reading for its account of how that distribution works in practice. **Takeaway:** Build a current inventory of every third-party script your pages load, and enforce a Content Security Policy with explicit script-src allowlists and violation reporting.

At least 178 top web destinations unwittingly served a variety of malware exploits against visitors over the past 24 hours thanks to a security vulnerability involving Optimizely, a company that helps websites customize user experiences and test out new features.

— Krebs on Security

Read the full article on Krebs on Security →