---
title: "One Optimizely flaw put malware in 188 site scripts, at Zoom, CNN and the BBC"
summary: "Report URI’s check of 1,611 Optimizely scripts and Optimizely’s notice, 16–17 November: how one flaw let attackers rewrite 178 organisations’ code, and what it stole."
url: https://www.thetechbag.com/blog/optimizely-scripts-188-malware-zoom-cnn-bbc
format: Note
desk: "Security"
area: "Threats & vulnerabilities"
region: Global
published: 2026-11-17
facts_checked: 2026-11-17
author: TechBag (The TechBag Journal)
tags: ["Optimizely hack","Optimizely malware","Optimizely supply chain attack","Optimizely security incident","Optimizely","Optimizely Web Experimentation","Report URI","Scott Helme","card skimmer","crypto clipper","Coruna exploit kit","DarkSword exploit kit","Content Security Policy","third-party JavaScript","supply chain attack","Magecart","Zoom","BBC","CNN"]
cover: https://www.thetechbag.com/blog/covers/optimizely-scripts-188-malware-zoom-cnn-bbc.png
---

# One Optimizely flaw put malware in 188 site scripts, at Zoom, CNN and the BBC

*Report URI’s check of 1,611 Optimizely scripts and Optimizely’s notice, 16–17 November: how one flaw let attackers rewrite 178 organisations’ code, and what it stole.*

Note · Security · Threats & vulnerabilities · By TechBag · Published 2026-11-17 · Facts checked 2026-11-17 · Canonical: https://www.thetechbag.com/blog/optimizely-scripts-188-malware-zoom-cnn-bbc

For about 19 hours on 16 November, the JavaScript that Optimizely serves to its customers’ websites carried malware. Report URI, a script-monitoring company, fetched 1,611 Optimizely snippets it could find and found the code in 188 of them, belonging to 178 organisations, among them Zoom, the BBC, CNN, Salesforce, GitLab and HSBC.[1] The 1,611 is Report URI’s sample, not Optimizely’s customer count; it says the real number is likely higher. Optimizely said early on 17 November that an unauthorised party “exploited a vulnerability in Experimentation” to add malicious JavaScript to some customer projects, and that the flaw is fixed and the code removed.[2]

188

infected snippets among the 1,611 Report URI checked

Report URI

178

organisations those 188 snippets belong to

Report URI

~19h

from the first injection seen to every file clean

Report URI

~US$7,000

in crypto received by the attackers’ wallets on 16 November

Report URI

## Trusted file, rewritten contents

Optimizely’s experimentation product works by having each site load a snippet from `cdn.optimizely.com`. Besides Optimizely’s own code and the customer’s experiments, the snippet carries “Project JavaScript”, custom code the customer writes in its dashboard that runs on every page. The attacker wrote a loader into that field and left the rest untouched, so the file still came from Optimizely’s own host, with its certificate. Report URI found three versions: a plain script tag, the same address hidden in base64, and a full inline copy that runs if the address is blocked. Sites that serve the snippet from their own domain were hit too, because the content comes from the same Optimizely project. Smartsheet’s snippet was cleaned once and then infected again, and the snippets for Optimizely’s own website and login page carried the code as well.[1] Optimizely told BleepingComputer the flaw sat in its “Experimentation account signup flow”; it says it has blocked that path, ended sessions, revoked tokens, reset affected accounts and notified all affected customers.[3]

The payload, rebuilt 26 times during the day, swapped cryptocurrency wallet addresses on the page and in the clipboard, skimmed card numbers typed into a site’s own forms (not hosted payment frames such as Stripe’s), sent cookies and screenshots out, and on iPhones and iPads loaded the Coruna and DarkSword exploit kits.[1] BleepingComputer says scans on urlscan.io show the script loading, or trying to load, on sites including Zoom, KLM, the BBC, CNN, Smartsheet and Salesforce; Salesforce said it had disabled Optimizely scripts across its instances while it investigates.[3]

**Figure: Malware ran in Optimizely snippets for about 19 hours before every file was clean**

*Optimizely Web snippet compromise, 16 to 17 November 2026, in UTC (IST in each detail)*

| Date | Event | Detail |
| --- | --- | --- |
| 16 Nov, 04:21 UTC | First injection seen | In the BBC’s snippet; 9:51am IST |
| 16 Nov, 08:28 UTC | Payload on bbc.com | Wallet-address swapper; 1:58pm IST |
| 16 Nov, 13:43 UTC | Card skimmer added | 7:13pm IST |
| 16 Nov, 17:13 UTC | iOS exploit added | Every visit on iOS 18.6 or earlier; 10:43pm IST |
| 16 Nov, 19:24 UTC | 186 of 1,611 infected | Report URI’s sweep; 12:54am IST, 17 Nov |
| 16 Nov, 23:11 UTC | All files clean | 4:41am IST, 17 Nov |
| 17 Nov, 00:37 UTC | Payload domain held | Stops resolving; 6:07am IST |
| 17 Nov, 01:02 UTC | Optimizely’s notice | Status page; 6:32am IST |

Source: Report URI (investigation and 17 November update); Optimizely status page · as of 17 November 2026, 10:30pm IST

## What a site owner and a visitor should check

Report URI crawled the affected organisations’ own sites. Of the 159 it could rate, 68 had no Content Security Policy and 50 had one that let both the payload and the data theft through; 24 blocked the payload outright with a restrictive list of script sources. Allowing `cdn.optimizely.com` did not help, since the code came from there; HSBC’s policy stopped the remote file but allowed `unsafe-eval`, which Optimizely’s own documentation tells customers to permit, so the inline copy still ran.[1]

ReportedReport URI’s checklist

Site owners: read every project’s Project JavaScript and every experiment’s custom code for `1688360.cc`, `atob(` or anything unfamiliar; review users, API tokens and integrations with write access and rotate them; treat cards typed into your own forms on 16 November, and secrets in cookies not marked HttpOnly, as exposed. Visitors: update to iOS 18.7.3 or 26.3 or later, check any crypto address you pasted, and watch card statements.[1] The one Indian domain on Report URI’s list is Crocs India.[1] How one supplier reaches many customers is also the story of [three npm worm waves](https://www.thetechbag.com/blog/npm-worm-valid-provenance-supply-chain).

How we did this

Figures as of 17 November 2026, 10:30pm IST

The 1,611, 188 and 178, the timeline, the payload and the crawl are Report URI’s; its sweep at 19:24 to 19:59 UTC found 186, and its final count is 188. The 159 is our sum of its four crawl results (68, 50, 17 that blocked only the data theft, and 24). Report URI put the wallets’ receipts at about US$7,040 by 19:25 UTC on 16 November; its next-day figures add up to about US$7,150, and BleepingComputer notes some wallets were in use before the attack. Neither counts cards, cookies or infected phones. Optimizely has posted one status update, and has not said how many customers it notified. “About 19 hours” is 04:21 to 23:11 UTC.

Spotted an error? Write to us; corrections are published at the foot of the piece.

Sources

1. [Scott Helme (Report URI), World’s Largest Brands Infected With Malware Via Optimizely](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/) — 16 November 2026, updated 17 November 09:17 UTC
2. [Optimizely Service Status, Web Experimentation Security Incident](https://status.optimizely.com/incidents/ftw0fh9wx43z) — 17 November 2026, 01:02 UTC
3. [BleepingComputer, Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware (with Optimizely’s and Salesforce’s statements)](https://www.bleepingcomputer.com/news/security/optimizely-supply-chain-attack-delivers-malware-to-cnn-fox-news-bbc-salesforce-sites/) — 16 November 2026, 21:12 ET

**Disclosure.** TechBag is a software reseller: it earns when companies buy through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.

**Read this next:** [Amadeus breach hit at least ten airlines through one booking system](https://www.thetechbag.com/blog/amadeus-breach-airlines-one-supplier) — Another breach through one supplier: how Amadeus’s booking system exposed records at ten airlines, and why the counts cannot be added.

Go deeper on TechBag

- [Valid provenance, malicious code: what three npm worm waves broke](https://www.thetechbag.com/blog/npm-worm-valid-provenance-supply-chain) — trusted code from a supplier, turned malicious in transit
- [A 3×3×3 multivariate test needs 14.4 lakh visitors; an A/B test, 1.1 lakh](https://www.thetechbag.com/blog/concept-multivariate-testing) — what experimentation platforms such as Optimizely are used for
- [Third parties were in 48% of breaches](https://www.thetechbag.com/blog/third-party-risk-management-security-ratings-must) — how organisations assess the suppliers whose code they run
