The Code Ran for About 17.5 Hours on Sites Such as the BBC, CNN and Zoom

Report URI counted 178 organisations after checking 1,611 Optimizely snippets and finding malicious code in 188 of them, and says 178 is a floor. Its timeline puts the first injection at 04:21 UTC on 16 November and the mass clean-up between 20:40 and 21:10 UTC. BleepingComputer confirmed the script loading on sites including the BBC, CNN, Zoom, Salesforce, GitLab, Air France and HSBC Insurance. The payload swapped crypto wallet addresses, skimmed card numbers typed into a site's own forms, and sent cookies and screenshots to the attacker. Attacker wallets had received about USD 7,000 by that evening.

This Was a Vendor Account Failure, Not a Cache Poisoning

Optimizely says an unauthorized party exploited a vulnerability in its Experimentation account signup flow and added JavaScript to customer projects. It has blocked the path, removed the code, ended sessions and revoked tokens. Report URI's own reading is blunt: the CDN served exactly what it was given. That matters because the sites did nothing wrong in the usual sense. They loaded a trusted tag from a trusted vendor, and the vendor's own editing field became the delivery route. Treat every marketing or testing tag with write access to your pages as part of your payment page, because attackers now do.

What to Do This Week

Open each Optimizely project and search its Project JavaScript and experiment code for 1688360, atob( and any .icu address, then check proxy and CSP logs back to 04:00 UTC on 16 November. Audit who and what can write to the account, including API tokens, and rotate them. Treat cards entered on your own checkout that day as exposed and tell your payment provider. Remove unsafe-eval, tighten connect-src and keep third-party tags off checkout pages, which is also what PCI DSS 4.0 requirement 6.4.3 asks for on payment pages. Under NIS2 and GDPR a tag vendor is a supplier whose failure becomes your incident report. iPhone visitors were pushed toward exploit kits, so staff should update to iOS 18.7.3 or 26.3 or later.