Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

NewsIncident

Optimizely: code planted in customers' projects made the BBC, Zoom, CNN and HSBC sites serve malware for hours

Scott Helme of Report URI reported on November 16, 2026 that an attacker had written malicious JavaScript into the Project JavaScript field of Optimizely Web customers' projects, so Optimizely's own CDN served it on every page. Report URI found it in 188 of the 1,611 snippets it checked, belonging to 178 organisations, among them Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax and Ledger. The code swapped cryptocurrency addresses, skimmed card numbers, expiry dates and security codes typed into a site's own form fields, took readable cookies and screenshots, and tried to load iOS exploit kits on older iPhones and iPads. Report URI saw the first injection at 04:21 UTC, counted about 7,000 dollars in the attacker's wallets by 19:25 UTC, and found one snippet still infected at 21:52 UTC. Optimizely said early on November 17 that an unauthorized party had exploited a vulnerability in Experimentation to add malicious JavaScript to some customer projects, that it had fixed the flaw and removed the injected code, and it has not said how many customers were affected. Report URI says its count is probably low, and it cannot see how many cards or cookies were taken. Later on November 17, Salesforce told Reuters it had disabled the altered scripts as a precaution, and Equifax said it had stopped using Optimizely and found no evidence its own systems were compromised. Report URI's list by sector is banking and finance 32, technology 23, retail 20, streaming 12, news and media 10, airlines and travel 9, telecoms 7, crypto and trading 6 and insurance 6. The clean-up is not confirmed complete: StepSecurity found the main payload domain on registry hold from 00:37 UTC on November 17 but two attacker hosts still resolving at its last check, and reports that Smartsheet's snippet was re-infected after an earlier clean-up. No actor is confirmed, and Helme told Newsweek he saw no evidence of AI involvement.

Why it matters

The sites were the real ones and the file came from a trusted domain, so nothing looked wrong. Treat every third-party script on a checkout or sign-in page as part of your own code: limit who can edit it, watch what it changes and restrict where the page can send data. If you paid on a big site on November 16, check your card statement and confirm any crypto address on your wallet's own screen.

Sources

Read it with the rest of the news in the Learning Center