Visitors to CNN, the BBC, Zoom and 175 other organisations may have been served harmful code through a trusted third-party tool. Here is what happened, what is still unknown and the steps you can take.
This article reflects public reports available on 18 November 2026. Details may change as investigations continue.
On Monday 16 November 2026, security researchers discovered that visitors to the websites of CNN, the BBC, Zoom and 175 other organisations may have been shown malicious code. The key detail is how it happened: the websites themselves were not hacked one by one. The attackers went through a tool that all of them trusted.
What happened
Researcher Scott Helme and his team at Report URI found harmful JavaScript in files connected to Optimizely, a service companies use to test and personalise their web pages. Websites load Optimizely through a small snippet of code, which means a change at Optimizely appears automatically on every site that uses it.
Optimizely confirmed that an unauthorised party exploited a vulnerability in its Experimentation product and added malicious code to some customer projects. Because the code was delivered from Optimizely's own servers, visitors' browsers treated it as trusted.
In total, 178 organisations were affected. Named examples include the BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. Banks and financial companies were the largest group. Researchers say the real number may be higher.
What the code tried to do
- Swap cryptocurrency wallet addresses so that payments would go to the attackers instead of the intended recipient.
- Copy card details (number, expiry date and security code) typed into a website's own payment forms. Forms run by a separate payment provider were out of its reach.
- Steal cookies and screenshots, which can help someone stay signed in to your accounts.
- Attack older iPhones and iPads. On devices running iOS 18.6 or older, it tried to deliver exploit kits, which are tools designed to break into a device.
Researchers reported that the attackers' crypto wallets had received roughly US$7,000, which is small. That does not mean nothing else was taken.
What has been done
Optimizely says it fixed the vulnerability, removed the injected code, notified affected customers, secured affected accounts and added protections. Report URI reported that all the infected files it was monitoring were clean by 23:11 UTC on 16 November and stayed clean afterwards.
What is still unknown
- How many people actually had card details or other data taken.
- How long the attackers had access before they were noticed.
- Who is behind it. No group has been named.
- It does not prove that the BBC's, CNN's or Zoom's own servers were breached, and the researchers do not say so.
What it means: a supply-chain attack
Think of a bakery chain that buys its flour from one supplier. If someone poisons the flour, every bakery is affected even though none of them was broken into. This is a supply-chain attack. It matters because even careful companies depend on outside tools for analytics, chat, adverts, testing and payments. Each of those tools is a possible way in.
What you can do as a visitor or customer
- Update your phone. Install the latest iOS or iPadOS, especially if you visited an affected site on 16 November.
- Check your card. If you paid on any affected site that day, look at your statement, turn on transaction alerts and call your bank if anything looks wrong.
- Double-check crypto payments. If you sent cryptocurrency that day, confirm the receiving address with the recipient through another trusted channel.
- Look for unfamiliar activity. Check the devices and sessions signed in to important accounts, and sign out those you do not recognise.
- Use up-to-date security software and be cautious with emails or messages about this incident. Criminals often follow news stories with fake warnings.
What you can do as a website owner
- List every outside script on your site: analytics, chat, testing, adverts. Remove what you no longer use.
- Use a strict Content Security Policy. This is a rule set that tells the browser which scripts may run and where data may be sent. Researchers found only about 15% of the affected organisations had one strict enough to stop this attack.
- Be careful with settings that allow code to run from text (such as JavaScript's eval). One affected site was exposed through such a setting.
- Use the payment provider's own secure payment fields instead of collecting card details in your own form.
- Watch for changes. Use monitoring that alerts you when a third-party script changes, and limit who can edit scripts inside testing and tag tools.
- Ask your vendors how they protect their accounts and how fast they tell you about incidents.
Sources
- Malwarebytes: CNN, BBC, Zoom and other sites served malicious code in supply-chain attack
- Help Net Security: Malware spread through Optimizely hits 178 organizations
Need a hand?
The Sisihub team can set this up for you, from the first idea to launch and support. Request a quotation on WhatsApp and tell us what you need.
Software & products

