The Optimizely Hack Explained: How 178 Sites Including Ledger, HSBC, and the BBC Served Crypto-Stealing Code
On November 16, 2026, hackers exploited a flaw in Optimizely's website-testing platform to plant crypto wallet-swapping malware on 178 organizations' sites, including Ledger, HSBC, Zoom, CNN, and the BBC. Here's exactly how the attack worked, what it actually stole, and how to protect yourself from the same trick.
▶ View as web storyOn November 16, 2026, attackers exploited a flaw in Optimizely, a website-testing platform used by thousands of companies to run A/B tests on their own sites, and used it to inject malware into 188 customer scripts belonging to 178 organizations — including Ledger, HSBC, Zoom, CNN, and the BBC. The malware, which researchers nicknamed OPTIMJACK, tried to quietly swap any cryptocurrency wallet address a visitor copied for one the attacker controlled, while also attempting to skim payment card numbers. Despite the scale, confirmed crypto losses stayed small — roughly $6,600 to $7,150 — because researchers caught and helped clean up the incident within about 19 hours.
This wasn’t a hack of Ledger, HSBC, or the BBC’s own servers. It was a supply-chain attack: a single compromised vendor, embedded as a small script on hundreds of unrelated websites, turned every one of those sites into a potential delivery mechanism for crypto-stealing code. Here’s exactly how it worked, who was affected, what the attackers actually got away with, and what it means for anyone who copies and pastes a wallet address.
What Actually Happened
Optimizely sells a “Web Experimentation” product: a snippet of JavaScript that companies paste into their own websites so Optimizely can run and measure A/B tests — showing different visitors different versions of a page to see which performs better. Because that snippet runs with broad access to the page it sits on, anyone who can tamper with it can effectively run arbitrary code on every site using it.
According to CoinDesk’s reporting, an unauthorized party exploited a vulnerability — since tracked as CVE-2026-132224, per a write-up from security firm BitSight — in Optimizely’s account signup flow. That flaw gave the attacker unauthorized write access to the “Project JavaScript” field inside existing customer projects: the customizable code block site owners use to add their own logic on top of Optimizely’s core script. Because the malicious code was inserted into that field rather than swapped into Optimizely’s own core files, it still loaded from Optimizely’s legitimate domain (cdn.optimizely.com) — which is part of why it went unnoticed at first. It looked like a trusted first-party request.
Security researcher Scott Helme, who runs the browser-security monitoring service Report URI, said his service scanned roughly 1,600 distinct Optimizely snippets in use across the web and found 188 of them — spread across 178 separate organizations — carrying the attacker’s injected code.
The Timeline: From First Injection to Full Cleanup
Reporting from multiple outlets, drawing on Report URI’s and incident-response firm StepSecurity’s analysis, places the key events (all times UTC) as:
- Around 4:21 AM, November 16, 2026 — The first known instance of the injected code appeared, found in the BBC’s Optimizely snippet.
- Through the morning — The same malicious code propagated across the other 177 affected organizations’ snippets, since all of them pulled from the same tampered project configurations.
- Roughly 1:03–1:05 PM — On-chain activity shows the attacker sweeping accumulated crypto toward exchange-linked addresses, according to researcher analysis.
- Around 7:24–7:59 PM — Report URI completed a scan confirming the scope of the compromise.
- Around 8:40 PM — Cleanup of the malicious scripts began.
- By roughly 11:11 PM, November 16 — Researchers reported that Optimizely-hosted files tied to the attack were clean.
- 1:02 AM UTC, November 17, 2026 — Optimizely posted a public security incident notice.
Optimizely’s own statement, as quoted by outlets including Security Affairs, said an unauthorized party had “exploited a vulnerability in the Experimentation account signup flow.” The company said it has since blocked the vulnerable signup path, patched the underlying flaw, ended active sessions tied to the intrusion, revoked affected access tokens, and notified every affected customer.
What the Malicious Code Actually Did
The injected script combined several attack techniques into one payload, based on technical breakdowns from researchers:
- Crypto clipper: The core function watched for cryptocurrency addresses copied to a visitor’s clipboard and silently replaced them with an attacker-controlled address before the visitor pasted it elsewhere. Because crypto transactions are irreversible once confirmed, anyone who pasted a tampered address while sending funds would have sent them straight to the attacker instead.
- Card skimmer: The code also attempted to capture payment card details entered into checkout forms on affected sites.
- Mobile exploit redirection: Some reports describe the code attempting to redirect visitors on outdated iPhones and iPads toward known exploit kits, rather than targeting Android devices.
- Data exfiltration: The payload reportedly also tried to grab screenshots and some cookie data from infected sessions.
This combination is why security researchers gave the campaign its own name, OPTIMJACK — a portmanteau of “Optimizely” and “hijack” — to track it as a distinct, coordinated incident rather than a routine malware sighting.
How a Crypto Clipper Like This One Actually Steals Funds
If you’ve never heard the term, a “clipper” is a long-standing category of crypto-targeting malware, and OPTIMJACK’s wallet-address-swapping behavior is a textbook example of it:
- The malicious code runs in the background of a page you’re visiting (or, in other clipper variants, inside a compromised app).
- It watches your device’s clipboard using pattern matching that recognizes the shape of common cryptocurrency addresses (Bitcoin, Ethereum, and others each have distinct, recognizable formats).
- The moment you copy an address — say, from an exchange’s withdrawal page — the malware replaces it with an address the attacker controls.
- More sophisticated clippers, rather than using a completely random replacement address, generate (“grind”) an attacker address that shares the same first and last few characters as the one you copied. Since most wallet interfaces only display a truncated version of a long address, a quick visual check often won’t catch the swap.
- You paste what looks like the right address, confirm the transaction, and the funds go to the attacker — permanently, since blockchain transactions generally can’t be reversed.
This is a different mechanism from “address poisoning,” another common crypto scam where attackers send you a tiny, worthless transaction from a lookalike address so it shows up in your transaction history, hoping you’ll copy it by mistake later. OPTIMJACK’s clipper didn’t need you to make that mistake — it altered what was already on your clipboard in real time.
Why the Dollar Losses Stayed Small Despite the Huge Reach
| Factor | What happened |
|---|---|
| Number of organizations affected | 178, including Ledger, HSBC, Zoom, CNN, and the BBC |
| Compromised scripts found | 188, across those 178 organizations |
| First known injection | ~4:21 AM UTC, November 16, 2026 (BBC) |
| Time to full cleanup | ~19 hours (clean by ~11:11 PM UTC the same day) |
| Confirmed crypto stolen | Roughly $6,600–$7,150 (estimates vary by researcher) |
| Ledger hardware wallets compromised | None confirmed — Ledger says device security was unaffected |
The gap between “178 major organizations hit” and “about $7,000 stolen” comes down to a few factors working together: the relatively short window before researchers and Optimizely caught and cleaned the code; the fact that most site visitors on any given day aren’t actively copying a crypto wallet address at that exact moment; and defenses like HSBC’s Content Security Policy, which is designed specifically to block unauthorized third-party scripts from executing on a page, partially limiting the payload’s effect on at least some of its pages. It’s a reminder that “number of sites compromised” and “actual financial damage” can be very different numbers, and that both matter for understanding the real severity of an incident.
What This Means If You Use Any of the Affected Sites
If you visited Ledger’s, HSBC’s, Zoom’s, CNN’s, the BBC’s, or another affected site between November 16 and 17, 2026, and copied a crypto wallet address during that window, it’s worth checking your transaction history against the address you intended to send to, using a block explorer for the relevant blockchain. If you see a transaction going to an unfamiliar address around that time, treat it as a likely loss and move any remaining funds in that wallet to a new one.
More broadly, this incident is a reminder that supply-chain risk isn’t limited to crypto exchanges and wallet apps — it can arrive through almost any third-party script a site embeds, from analytics tools to A/B testing platforms to chat widgets. That mirrors a pattern seen in other recent wallet-security stories: this site previously covered how a malicious Electrum server could trick users into signing away Bitcoin they thought was stuck, and separately how a hidden chip in counterfeit Ledger devices was used to steal seed phrases directly — different attack surfaces, but the same underlying lesson: verify everything related to money movement through a channel the attacker can’t control, whether that’s your hardware wallet’s own screen or a saved address book entry, rather than trusting what your screen displays by default.
This is not financial or security advice — if you handle cryptocurrency, do your own research into your specific wallet and browser setup, and treat any copied address as unverified until you’ve checked it in full.