Security IncidentNov 17, 2026

BBC, CNN and Zoom Sites Served Malware Through Optimizely: What Happened and What to Do

Sudip Bhandari
Sudip Bhandari
Co-founder, Sequirly
BBC, CNN and Zoom Sites Served Malware Through Optimizely: What Happened and What to Do

On Monday, November 16, an attacker used a flaw at Optimizely, a company that helps websites test different versions of their pages, to put malicious code on the websites of at least 178 organizations. They include the BBC, CNN, Zoom, Salesforce, HSBC and IKEA.

These sites load a script from Optimizely's servers, and the attacker changed what that script contained. So anyone who opened an affected page that day could have received code built to swap crypto wallet addresses, skim card details and attack older iPhones.

Nothing published so far says the sites' own servers were breached, and Optimizely says it has fixed the flaw and removed the code. What you need to check depends on what you did on those sites, so let's start with how a testing tool ended up delivering malware.

Note
This post reflects what Optimizely and security researchers had published as of November 17, 2026. Every fact below links to its source.

What happened

Optimizely sells software that lets companies test changes to their websites, such as a different headline or button. A company that uses it adds one line to its pages, and that line loads a script from Optimizely's servers every time someone visits.

Each company's script has a field called Project JavaScript, where customers can add their own code. The attacker wrote malicious code into that field for many customers at once. Security firm Report URI found the code in 188 of the 1,611 Optimizely scripts it checked, spread across 178 organizations.

The file still came from Optimizely's servers with Optimizely's security certificate, so browsers treated it as safe. Scott Helme of Report URI summed it up this way: "trusted JavaScript doesn't always remain trustworthy."

Optimizely says an unauthorized party exploited a vulnerability in the account sign-up flow of its Experimentation product to add the code, according to BleepingComputer. It hasn't explained how that flaw gave the attacker access to unrelated customers' projects.

It also says it fixed the flaw, removed the code, ended active sessions, revoked tokens and told affected customers, according to its incident notice and its statement to BleepingComputer. Report URI confirmed that every infected file was clean by 23:11 UTC on November 16.

The timeline

All times are UTC, and Eastern Time is five hours behind.

Time (UTC)What happened
Nov 16, 04:21First infected script seen, on the BBC's Optimizely file (11:21 p.m. Eastern on Sunday, Nov 15)
Nov 16, 08:28Code that swaps crypto wallet addresses first seen on bbc.com
Nov 16, 13:43Card-skimming code added
Nov 16, 17:13 to 17:57Code that attacks iPhones and iPads running iOS 18.6 or older added
Nov 16, about 20:40 to 21:10Clean-up begins, including Ledger, Smartsheet and the BBC
Nov 16, 21:52One infected file left, at TalkTalk
Nov 16, 23:11Report URI confirms every infected file is clean
Nov 17, 01:02Optimizely posts its incident notice

The times come from Report URI and Optimizely. The attacker rebuilt the code 26 times that day, so what visitors received changed through the day.

What the malicious code did

Researchers found four things in the code.

1.It swapped crypto wallet addresses. When a visitor copied or typed a valid wallet address, the code replaced it with one that belongs to the attacker. Researchers traced roughly $7,000 to wallets linked to the attack.
2.It skimmed card details. From 13:43 UTC, it tried to read card numbers, expiry dates and security codes typed into a site's own payment forms.
3.It collected cookies and screenshots. On pages where it swapped an address, it sent the page address, the cookies the page's scripts could read and a screenshot to the attacker.
4.It attacked older iPhones and iPads. Report URI identified the exploit kits as Coruna and DarkSword, which target iOS 13 to 18. On iOS 26, the code only collected details about the device.

Some things were out of its reach. Card fields inside a payment provider's own hosted frame, such as Stripe or Adyen, couldn't be read, and neither could cookies marked HttpOnly. StepSecurity's analysis also found that the skimmer didn't collect the cardholder's name or billing address.

Who was affected

Report URI says the real number is probably higher than 178. The biggest groups were 32 banks and financial firms, 23 technology companies, 20 retailers, 12 streaming services and 10 news organizations. Named victims include:

  • News: BBC, CNN, Fox News and NPR
  • Technology: Zoom, Salesforce and GitLab
  • Banking and finance: HSBC in several countries, Equifax and ABN AMRO
  • Retail and travel: IKEA, ASOS and Air France-KLM
  • Telecoms and streaming: TalkTalk, Virgin Media and Peacock
  • Crypto: Ledger

Newsweek published the full list of 178. Being on it means researchers found the code in that organization's Optimizely script, and how many visitors actually lost data is unknown.

Salesforce says it disabled Optimizely scripts across its preview and production sites as a precaution and is investigating. As of November 17, we found no public statement from the BBC or CNN.

Sequirly
Limited time · No credit card required

Prevent accidental data leaks to ChatGPT, Claude, and Gemini.

Sequirly scans your prompts and uploaded files before they're sent. If it finds credentials, client records, or API keys, it stops you before the request goes out.

What we don't know yet

1.How the attacker got access to so many customers. Optimizely points to its account sign-up flow, and hasn't said how that gave the attacker write access to unrelated customers' projects.
2.How many people were affected. Researchers say they have no way to see how many cards were skimmed, and nobody has published how many visitors received the code.
3.Whether Optimizely was the only supplier targeted. Report URI links the same attacker to similar code injected through other third-party scripts, including Kissmetrics, StorifyMe and Minute Media, between November 13 and 16.

If you visited an affected site on November 16

Don't panic. What you need to check depends on what you did on the site, and each check takes a few minutes.

1.You paid by card on an affected site. The code could read card details typed into the site's own payment form. Check your statements for charges you don't recognize, and call your bank if you see one.
2.You sent or copied a crypto address. The code could swap the address for the attacker's. Check where any transfer you made that day went, because crypto payments usually can't be reversed.
3.You used an iPhone or iPad running iOS 18.6 or older. The attacker's code tried to exploit these versions, so update to the latest iOS. Report URI says the exploit code's own comments name iOS 18.7.3 and iOS 26.3 as the patched versions.

Report URI's analysis doesn't list password theft among what the code did. Still, if you were signed in to a service while you copied a wallet address on an affected page, watch that account for login alerts you don't recognize.

If your website uses Optimizely

These steps come from Report URI and StepSecurity, and they're worth doing today.

1.Search every project's Project JavaScript and every experiment's custom code. Look for 1688360[.]cc, webshell[.]lol, the .icu domains listed in Report URI's write-up, atob( calls and any code you didn't write. Searching for one domain isn't enough, because the attacker loaded the payload in three different ways.
2.Review who has access. Check Optimizely users, API tokens and integrations, remove any you don't recognize and rotate your credentials.
3.Treat cards entered on November 16 as exposed. If your own forms collected card details that day, tell your payment provider and think about telling affected customers. Treat any secrets or session tokens in cookies that scripts can read as exposed too, and rotate them.
4.Search your logs back to 04:00 UTC on November 16. Look for requests to the attacker's domains.

How to limit the damage from any third-party script

Any site that uses outside scripts can end up in this position, so these steps apply well beyond Optimizely.

1.List every third-party script on your site. Include marketing, testing, chat and analytics tags, because each one runs with the same access as your own code.
2.Set a content security policy that limits where scripts can send data. Of the affected organizations whose sites Report URI checked, 68 had no policy at all, and only 24 blocked the payload. Allowing Optimizely's domain gave no protection, because the malicious code came from that domain. A policy that limits where scripts can send data (the connect-src setting) stopped card, cookie and screenshot theft on some sites, but it can't stop address swapping, which happens inside the page.
3.Avoid the unsafe-eval setting where you can. Optimizely's documentation recommends allowing it, and Report URI found that it let a backup copy of the code run on HSBC's site.
4.Keep payment fields in your provider's hosted frame and take third-party scripts off checkout pages. The skimmer couldn't read card fields inside a payment provider's frame.
5.Turn on content security policy reporting. It shows you blocked requests to domains you don't recognize. Report URI sells tools for this, so weigh its advice with that in mind.

Why this keeps happening

A site can be compromised through a third-party supplier without its own code or servers ever being breached, and a script that was safe yesterday can change overnight. In October we covered a similar attack on AI developers, where a poisoned release of a popular library stole cloud and AI provider keys. Here's how to check if your keys were exposed.

Common Questions

Was the BBC hacked?

Researchers found the attacker's code in the BBC's Optimizely script on November 16, so visitors to bbc.com received it. Nothing published so far says the BBC's own servers were breached, and we found no BBC statement as of November 17.

What is Optimizely?

Optimizely is a company whose software lets websites test different versions of their pages. Sites that use it load a script from Optimizely's servers on every visit.

Is it safe to visit these sites now?

Optimizely says it fixed the flaw and removed the code, and Report URI confirmed that every infected file was clean by 23:11 UTC on November 16. Keep your phone and computer updated as usual.

Was my card stolen if I visited one of these sites?

Only if you typed card details into a site's own payment form while the skimmer was running, which was from about 13:43 UTC until the clean-up that evening. Cards entered in a payment provider's hosted form couldn't be read, and nobody knows how many cards were taken.

What is a supply chain attack?

A supply chain attack is when criminals compromise a supplier that many organizations rely on, so the harm reaches all of its customers at once.

Do I need to change my passwords?

Report URI's analysis doesn't list password theft as part of this attack. Watch the accounts you were signed in to for login alerts you don't recognize, and change the password on any account that shows unusual activity.

How many websites were affected?

At least 178 organizations. Report URI found the code in 188 of the 1,611 Optimizely scripts it checked and says the real number is probably higher.

About this post

We build Sequirly, a browser extension that checks what you paste into AI tools. It had no part in this incident, and it doesn't protect you from malicious scripts on other websites. Here's how to check what any extension does with your data. We publish security news we can verify, and we tell you when we don't know something.

Sources:

Start Protecting Your Data

Ready to Prevent AI Data Leaks?

Sequirly catches sensitive data in real-time, before it leaves your browser. Set up in 2 minutes, runs locally, zero training required.

Sequirly is the safety layer of your AI stack. Local scanning, 2-minute setup, free plan.