The Library

Optimizely Hack: Malicious JavaScript Reached Visitors of 178 Organizations Including the BBC, CNN and Zoom, and What to Check on Your Own Website

On 16 November 2026, Optimizely snippets served malicious JavaScript to visitors of 178 organizations. Researchers say it hunted for card details and delivered iOS exploit kits. Here is what is confirmed and what to check this week.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Optimizely Hack: Malicious JavaScript Reached Visitors of 178 Organizations Including the BBC, CNN and Zoom, and What to Check on Your Own Website
On this page 7 sections

On 16 November 2026, malicious JavaScript reached visitors of 178 organizations through Optimizely, an outside service whose code snippets those organizations load on their websites. If your business website runs scripts from outside vendors, the risk is this: the code can change at the vendor's end and reach your customers, and nobody has to break into your own server.

The findings come from a write-up by Scott Helme on the Report URI blog. It says the injected code looked for payment card details and, on iPhones and iPads, delivered iOS exploit kits. Optimizely says it has fixed the vulnerability and removed the injected code. Below is what is confirmed, what is still unknown, and what to check on your own site this week.

What happened in the Optimizely hack

According to the Report URI write-up, 188 snippets belonging to 178 organisations were infected on 16 November 2026. The organizations it names include Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock.

The sources we checked do not report that any of these organizations' own servers were broken into. The code reached visitors through Optimizely snippets their pages already loaded. That is what a supply chain attack looks like: the weak point was a supplier, not the website owner.

Report URI says Optimizely has acknowledged the incident on its status page. In a statement quoted by Security Affairs, Optimizely said: "We've fixed the vulnerability and removed the injected code from affected projects."

The sources do not say what the vulnerability was, how the attacker got code into the snippets, or how long the code was live beyond the activity seen on 16 November.

What the malicious JavaScript did

A card skimmer on forms and checkout requests

The write-up says the script watched form submissions and every fetch/XHR POST request, the background requests many modern pages use to send data. It was looking for a card number, expiry date and CVV. Card numbers were Luhn-checked. That is a quick test of whether a number has the shape of a real card number, so the script was looking specifically for numbers that look like genuine cards.

iOS exploit kits for iPhones and iPads

On iPhones and iPads, the code delivered the Coruna and DarkSword iOS exploit kits. This time the code arrived through a trusted script on major brand websites.

The sources do not say which iOS versions these kits work against, whether they succeeded on any device, or how many iPhones and iPads loaded them.

Money reaching the attacker's wallets

Report URI says the attacker's cryptocurrency wallets received about $7,040, all within roughly nine hours on 16 November. The sources do not say where that money came from or whether it is the full total.

Optimizely breach: confirmed, claimed and not known

Point Status Source
Optimizely had a vulnerability and removed injected code Confirmed by Optimizely Statement quoted by Security Affairs; status page acknowledgement reported by Report URI
188 snippets belonging to 178 organisations infected Researchers' finding Report URI
Card skimming and iOS exploit kits in the injected code Researchers' finding Report URI
About $7,040 to attacker wallets in about nine hours Researchers' finding Report URI
How the attacker got in Not known Not in the sources
Number of cards or devices affected Not known Not in the sources
Which iOS versions are at risk Not known Not in the sources

Why third-party script hijacking matters for a company website

It is easy to think of website security as your own server, your own passwords and your own code. This incident shows what that view misses. A script loaded from a vendor runs on your page, next to your login and checkout forms. Here, the skimmer watched form submissions on the pages where it ran. Your developer can review your code before launch, but a vendor's code can change afterwards without your team doing anything.

The Report URI write-up puts it this way: "The important lesson here is that trusted JavaScript doesn't always remain trustworthy."

If your business takes payments or logins online, every outside script is part of your security, whether it does analytics, testing, chat or advertising.

What to do this week: Optimizely and third-party script checklist

Step How to check Why
Find out whether your site loads Optimizely Ask your web team, agency or marketing team, and search your page source and tag manager for optimizely You can only judge your exposure if you know the script is there
If it does, read Optimizely's notice Check Optimizely's status page and ask your Optimizely contact whether your project was affected The sources do not say whether each customer was told directly
If you take card payments, contact your payment provider Give them the date and ask about unusual activity on cards used on your site around 16 November The skimmer looked for card number, expiry date and CVV
List every third-party script on login and checkout pages Open each page and write down every outside domain it loads code from Any of them can change without your developer touching your site
Remove scripts you no longer use Delete old tags and finished test snippets from templates and tag managers Fewer scripts means fewer suppliers to trust
Tell staff about the iPhone risk Ask staff who visited affected sites on iPhones or iPads to install the latest Apple updates and report anything unusual The code delivered iOS exploit kits. The sources name no fixed iOS version, so we cannot confirm that any update blocks them
Watch outside scripts for changes Ask your developer to set up an alert when a third-party script on a sensitive page changes Trusted code can stop being trustworthy

Optimizely hack questions people are asking

Was my website affected by the Optimizely hack?

Only if your site loads an Optimizely snippet. Report URI says 188 snippets belonging to 178 organisations were infected, and it names Zoom, the BBC, CNN and others. If you use Optimizely, ask them directly whether your project was one of them.

Is the Optimizely vulnerability fixed?

Optimizely says it is. It said it fixed the vulnerability and removed the injected code from affected projects. The sources we checked do not explain what the flaw was.

Were credit card numbers stolen?

The script was built to capture card number, expiry date and CVV from forms and background requests. The sources do not confirm how many cards, if any, were captured.

What are Coruna and DarkSword?

They are iOS exploit kits, meaning tools built to attack iPhones and iPads. The injected code delivered both to Apple mobile devices. The sources do not say which iOS versions they target.

I only visited one of these websites. Should I worry?

If you entered card details on an affected site around 16 November, watch your statements and talk to your card issuer. If you visited on an iPhone or iPad, keep it updated and report anything unusual to your IT team.

What is a JavaScript supply chain attack?

It is when attackers tamper with code that a website loads from a supplier, so the malicious code reaches visitors from a source the site trusts. This Optimizely incident is an example.

The bigger lesson

Your website is only as trustworthy as every script it loads. The brands named here have large security teams, and their visitors still received malicious code through a supplier. Reviewing your own code before launch matters, but outside code needs someone to own it and watch it after launch too.

To have your site's third-party scripts listed, reviewed and monitored, see security hardening or request a quote.

Get security alerts like this one by email, with our free checklist, at security alerts.

Sources: Report URI, Scott Helme; Security Affairs.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.