Optimizely compromised, served malware on Zoom and GitLab
Report-URI’s blog reports that Optimizely, a third-party optimization script used by many websites, was compromised and used to serve malware through customer pages including Zoom and GitLab. The incident is a script supply-chain compromise: sites that embedded Optimizely’s JavaScript were exposed through the vendor rather than through a breach of their own servers. The supplied material does not specify the affected script versions, the malware payload, or the number of sites affected, and Optimizely’s own account is not included.
Verified and unconfirmed
- Verified: Report URI’s write-up, attributed to researcher Scott Helme, states that someone gained write access to the Optimizely Web experimentation script that Optimizely serves across its customers’ websites — not just one customer’s account — and injected malicious JavaScript that ran on pages at Zoom, GitLab, CNN, BBC and others on 16 November 2026; the same post reports that, as of 19:25 UTC that day, the attacker’s wallets had received about $7,040 over roughly nine hours.
- Not yet confirmed: No statement from Optimizely itself appears in the supplied material, and Gizmodo frames the spread of the attack as “reportedly” affecting Zoom and 170-plus other sites, so the full list and count of affected customers is unverified; also unconfirmed are the total number of visitors exposed, whether anything beyond the reported $7,040 in cryptocurrency was taken (for example credentials or payment data), and the reported symptom that pages on iOS 18.6 or earlier reload every 60 seconds to retry the exploit.
Background
Optimizely is an experimentation and personalization platform that customers embed site-wide through a third-party JavaScript snippet, so a single change to that script executes in the browser of every visitor to every participating site. That is what makes third-party scripts — tag managers, analytics, A/B testing — a supply-chain surface: as a commenter on the Hacker News thread put it, site operators include such code willingly and explicitly, and by his account the failure was not a CDN cache-poisoning attack, since the CDN served what it was given (tool-1-1). Report-URI’s own scanning tracked the cleanup, finding the malicious code in 169 of 188 infected snippets at 20:56 UTC and in only 1 by 21:52 UTC (tool-1-3).
Why it matters
Any site that loads Optimizely’s script should treat the vendor as part of its attack surface: a compromised third-party script can execute in visitors’ browsers with the page’s origin privileges. The practical consequence is that site operators cannot rely solely on their own server security; they need controls such as subresource integrity, version pinning, or self-hosting for third-party scripts.
Community discussion
Commenters debated accountability, with one arguing Optimizely should have had release cool-downs, phased rollouts, and automated security checks, and another saying large publishers should vendor third-party scripts rather than load them from vendors. Others questioned why major sites would handle sensitive data on the same origin and cited a reported $7,040 loss over nine hours as surprisingly low; these are commenter opinions, not verified figures.
Comments
Comments use a GitHub account and are moderated. Comment rules