Zoom, the BBC and HSBC Served Malicious Code They Never Wrote

Report URI, which sells monitoring for third-party website scripts, says malicious JavaScript reached visitors of 178 organizations on Nov. 16, 2026, carried by the website testing platform Optimizely. Zoom, the BBC, CNN, Salesforce, IKEA and HSBC were among them, and none of their own systems had to be breached.
Scott Helme, the security researcher who published the analysis, explains how. Optimizely Web has each customer load a small JavaScript file, a snippet, from Optimizely's own network. The snippet carries a field for custom code the customer writes in its Optimizely dashboard, which runs on every page of its site. Helme reports the attacker wrote code into that field and left the rest of the file untouched, so it still arrived from Optimizely's address, with Optimizely's certificate, from a host the site already trusted.
Report URI fetched 1,611 Optimizely snippets and found the malicious code in 188 of them. It says the real total is probably higher, because it could only check the snippets it could find.
Helme reports that the code swapped cryptocurrency wallet addresses shown on a page for the attacker's, captured card numbers typed into a site's own payment fields, took cookies and screenshots, and on iPhones and iPads loaded attack kits aimed at older versions of iOS. Report URI advises anyone who visited an affected site that day to update to iOS 18.7.3 or later, and to check any card payment or cryptocurrency transfer they made.
Helme writes that he does not know how the attacker obtained write access to so many unrelated customer projects, and that it is for Optimizely to explain. Most snippets were cleaned within hours, and an update on Nov. 17, 2026 says every infected file Report URI tracks is now clean and that Optimizely has acknowledged the incident on its status page.
Report URI also checked how 256 affected organizations restrict what their pages may load, and reports the script was blocked outright at 24 of them. Permitting Optimizely's own address was no help, because the code arrived from it.
