# Optimizely snippets hijacked on 178 brands' sites: card skimmer, crypto clipper and iPhone exploits. What to do

> For about 17 hours on November 16, malicious code was served through Optimizely Web snippets to visitors of at least 178 organisations, including Zoom, the BBC, CNN, HSBC and Equifax. It skimmed cards, swapped crypto addresses and pushed iOS exploit kits. Optimizely says it fixed the flaw. Site owners, shoppers and iPhone users each have checks to do.

Published Nov 17, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/optimizely-snippets-hijacked-178-sites-card-skimmer-crypto-clipper-ios-exploits-what-to-do

An attacker got malicious JavaScript into Optimizely Web, the A/B-testing service many large companies load on their pages. For most of Monday, November 16, it was served to visitors of at least 178 organisations, according to [researcher Scott Helme of Report URI](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/), who found the campaign. Named sites include Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. The code skimmed payment cards, swapped cryptocurrency wallet addresses, took screenshots and cookies, and tried to exploit older iPhones.

Why it matters: none of these companies had their own servers breached. The code came from Optimizely's CDN, carrying a valid certificate, inside the snippet the sites had chosen to trust. Any site that loads a third-party script is exposed to the same risk, and the incident was a live test of whether a site's Content Security Policy actually holds.

## How it worked

Report URI says the attacker wrote code into each customer's **Project JavaScript** field. That field runs before every experiment in a project. The report says this was not CDN cache poisoning, and that it doesn't know how the attacker got write access across customers. Optimizely's own sites, www.optimizely.com and login.optimizely.com, were infected too.

Optimizely told customers that an unauthorised party "exploited a vulnerability in Experimentation" to insert the code. The company says it has fixed the flaw, removed the injected code, secured affected user accounts and added protections against unauthorised code delivery. [BNO News](https://bnonews.com/index.php/2026/11/optimizely-hack-spreads-malware-to-several-websites-including-hsbc-bbc-and-cnn/) and [WindowsForum](https://windowsforum.com/news/optimizely-web-javascript-breach-admin-response-to-card-skimming-and-crypto-address-swaps.452629/) report the statement, the latter via a status-monitoring notice timestamped 01:02 UTC on November 17. Optimizely hasn't named the flaw or said how many accounts were involved. When Report URI published, it had received no reply from the company.

## Scale and timeline (UTC, November 16, per Report URI)

| Time | Event |
|---|---|
| 04:21 | First injection seen, in the BBC's snippet (11:21 p.m. ET Sunday) |
| 05:23 | Command-and-control domain 1688360.cc registered |
| 11:20 | Zoom's snippet modified |
| 13:03 | Stolen crypto swept to exchanges |
| 13:43 | Card skimmer added to the payload |
| 17:13–17:57 | iOS exploit routing added |
| 19:24–19:59 | Sweep finds 186 of 1,611 snippets infected |
| ~20:40–21:10 | Mass cleanup; by 21:52 only TalkTalk's snippet is still infected |

In total, Report URI found 188 infected snippets belonging to 178 organisations among the 1,611 it checked. It calls that a floor, because it could only check snippets it could find. The payload was rebuilt 26 times in one day. Banking and finance was the largest group with 32 organisations, followed by technology and SaaS (23) and retail and fashion (20).

## What the code did

- **Crypto clipper:** replaced wallet addresses for eight coins, including BTC, ETH, TRON and Solana, in page text, on the clipboard and in outgoing requests. By 19:25 UTC, about **$7,040** had reached the attacker's wallets, the largest piece being 0.08298 BTC.
- **Card skimmer:** captured card number, expiry and CVV from forms on the page. Hosted payment iframes, such as Stripe's or Adyen's, were out of reach, [Cyber Security News](https://cybersecuritynews.com/optimizely-websites-hijacked/) notes.
- **Data theft:** sent the page URL, any cookies not marked HttpOnly, and a screenshot to 1688360.cc.
- **iPhone and iPad exploits:** loaded the Coruna kit on iOS 13–17 and DarkSword on iOS 18.x. iOS 26 got a chain that only fingerprinted the device.

Nobody yet knows how many visitors lost card data. Report URI's dollar figure covers only the crypto it could trace.

## What to do

**If you run Optimizely Web**

1. Search every Project JavaScript field and every experiment's custom code for `1688360.cc`, `atob(` and any script you don't recognise. Use the change history to see whether each edit came through the API or the web UI.
2. Review users, API tokens and integrations, and rotate credentials.
3. Treat cards entered on your site on November 16, and any secrets kept in non-HttpOnly cookies, as exposed. Rotate session tokens and consider telling customers.
4. Block 1688360.cc, 5vobauua3ojpklx.icu, eil786npto9u5bq.icu, l7bcsnwc7nzr3uo.icu and webshell.lol.
5. Tighten your CSP. Report URI crawled 256 affected hosts: 68 had no CSP, 50 had one that let both the payload and the data theft through, and only 24 blocked the payload outright. It says a restrictive `script-src` made the difference, and that policies allowing `'strict-dynamic'` or `'unsafe-eval'` did not stop it. A restrictive `connect-src` blocked exfiltration on another 17. (Report URI sells CSP monitoring, so weigh its product pitch accordingly. The crawl numbers are its own.)

**If you visited these sites on November 16**

- Update iPhones and iPads to **iOS 18.7.3 or later, or iOS 26.3 or later**. Report URI says those versions are patched against both exploit kits. [Cyber Kendra](https://www.cyberkendra.com/2026/11/optimizely-malware-hits-zoom-bbc-cnn-what-to-do.html) points out that this guidance comes from Report URI, not from an Apple advisory.
- Check card statements. If you typed card details into a form on an affected site that day, ask your bank for a new card.
- Check any crypto transfers made that day, and always check the destination address before you send.

## What to watch

The questions now are how an attacker got write access to so many customers' projects, and whether this connects to a separate wave. Between November 13 and 16, Report URI saw webshell.lol injected through Kissmetrics, StorifyMe and Minute Media scripts. Expect breach notifications from affected retailers and banks if skimmed cards are confirmed.


## Sources

1. [Report URI — World's Largest Brands Infected With Malware Via Optimizely](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/)
2. [BNO News — Optimizely hack spreads malware to several websites, including HSBC, BBC and CNN](https://bnonews.com/index.php/2026/11/optimizely-hack-spreads-malware-to-several-websites-including-hsbc-bbc-and-cnn/)
3. [Cyber Security News — Hackers Infect 178 Major Websites via Optimizely to Steal Credit Cards and Target iPhones](https://cybersecuritynews.com/optimizely-websites-hijacked/)
4. [WindowsForum — Optimizely Web JavaScript Breach: Admin Response to Card Skimming and Crypto Address Swaps](https://windowsforum.com/news/optimizely-web-javascript-breach-admin-response-to-card-skimming-and-crypto-address-swaps.452629/)
5. [Cyber Kendra — Optimizely Malware Hits Zoom, BBC, CNN: What to Do](https://www.cyberkendra.com/2026/11/optimizely-malware-hits-zoom-bbc-cnn-what-to-do.html)
