Text size
Security

The Optimizely Hack Explained: How 178 Big-Name Websites Ended Up Swapping Crypto Addresses

Malicious code slipped into a web-testing tool used by Ledger, the BBC and HSBC swapped copied crypto addresses. Here is what happened and how to protect yourself.

Not financial advice. This article is for general information and education only. It is not a recommendation to buy, sell or hold any asset. Crypto assets are volatile and you can lose money; do your own research.

Most crypto users have learned to be careful with strange links, fake apps and too-good-to-be-true giveaways. But what if the danger came from a website you already trust, like a major news outlet, a global bank or even a hardware wallet maker? That is roughly what happened on Monday, November 16, 2026, when hidden code was planted inside a popular website tool and then quietly delivered to visitors of 178 organisations around the world.

The code had one job that matters most to crypto holders: when you copied a wallet address, it could silently swap that address for one belonging to the attacker. Below we explain, in plain English, what happened, why it worked, how much was taken, and the simple habits that would have protected you.

What happened on November 16

Optimizely is a company that helps businesses test different versions of their web pages, for example to see whether a green or a blue button gets more clicks. To use it, a website adds a small piece of Optimizely code, called a "snippet," to its pages. Every time someone visits, their browser downloads that snippet from Optimizely's servers and runs it.

According to security researcher Scott Helme of the firm Report URI, who published a detailed investigation, an attacker added their own instructions to the custom-code section of many customers' Optimizely projects. That extra line told visitors' browsers to fetch a second file, called track.js, from a website the attacker controlled. Report URI checked 1,611 Optimizely snippets and found 188 of them, belonging to 178 organisations, carrying the malicious addition.

The list named in reports includes Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Peacock and Ledger, the hardware wallet company. CoinDesk reported that six of the affected organisations were crypto or trading firms, including Ledger, IG, OANDA's Coinpass, Interactive Investor, TMS Brokers and Betashares, and that 32 more were banks and other financial companies.

Optimizely confirmed the incident. In a statement shared with Cointelegraph, the company said an unauthorised party had abused a weakness in its Experimentation account signup flow. "We have blocked access to the vulnerable path and deployed a fix," it said, adding that it had removed the injected code, ended active sessions, revoked tokens and notified affected customers.

A "supply chain" attack, explained simply

Security experts call this a supply chain attack. Think of a bakery that buys its flour from a supplier. If someone tampers with the flour at the supplier's warehouse, every bakery using that flour is affected, even though nobody broke into the bakeries themselves.

Websites work the same way. A modern web page often pulls in code from many outside companies: analytics, chat widgets, advertising and testing tools. The site trusts each of those suppliers to send safe code. If one supplier is compromised, the bad code reaches every site that relies on it, and visitors see nothing unusual because the address bar still shows the real, trusted website.

That is why this incident matters beyond one company. As Helme put it in his write-up, "trusted JavaScript doesn't always remain trustworthy." Neither Ledger's nor HSBC's own servers needed to be breached for their visitors to be exposed.

What the malicious code actually did

Report URI and the security firm StepSecurity, which nicknamed the campaign "Optimjack," described a multi-purpose toolkit. The parts that matter most to everyday users were:

  • Crypto address swapping. The script looked for wallet addresses on Bitcoin, Ethereum and other EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin. When it found a valid one, it replaced it with an attacker address of the same type. It could do this in the text on the page, in form boxes, and in your clipboard when you copied something.
  • Card skimming. From about midday UTC, it also watched for credit card numbers typed into payment forms and tried to send them to the attacker.
  • Cookie and screenshot theft. It collected some page data, including certain cookies and a screenshot of the page.
  • iPhone and iPad attacks. On Apple mobile devices, it tried to load known exploit kits that target older iOS versions.

One detail is especially sneaky. Report URI noted that the swapper only used addresses that pass each network's built-in checksum test. A checksum is a small error-detecting code inside an address, a bit like the check digit on a credit card number. Because the fake address was perfectly valid, your wallet app would accept it without any warning. StepSecurity added that the code only swapped addresses when nearby words such as "wallet," "deposit" or "send" suggested a payment was about to happen.

Report URI also warned that with an infected page open in any browser tab, an address you copied from somewhere else could still be replaced before you pasted it.

How much was stolen, and how fast it was cleaned up

The good news is that the direct crypto losses appear to have been fairly small, at least so far. Report URI said the attacker's wallets had received about $7,040 by 19:25 UTC on November 16, with the take spread across several coins. StepSecurity's on-chain check found roughly 0.085 BTC, about 17 LTC and about 0.075 ETH had landed in the attacker's addresses, plus some USDT and TRX on TRON. Its review found nothing received at the TON, Solana, Bitcoin Cash or Dogecoin addresses. CoinDesk noted that the full amount stolen, including any card fraud, is still not known.

The clean-up was also quick once the problem was spotted. Report URI's timeline shows a mass removal between roughly 20:40 and 21:10 UTC, with Ledger's snippet cleaned at 20:41 UTC. By 21:52 UTC, only one of the 188 infected snippets still contained the code.

Why "clipper" malware keeps working

Address-swapping malware, often called a "clipper," is an old trick. It survives because of a very human habit: crypto addresses are long strings of random-looking characters, so almost nobody types them by hand or checks every character. We copy, paste and press send.

Clippers exploit that moment of trust. They don't need your seed phrase, your password or your private key. They simply change where your money goes, and because blockchain transactions are generally final, a payment sent to the wrong address usually cannot be reversed. We covered a related lesson about address mistakes in our piece on CoinDCX and retired deposit addresses.

How to protect yourself: a simple checklist

You don't need to be a security expert to beat a clipper. A few habits go a long way:

  1. Check the address after you paste it. Compare the first five and last five characters, and a few in the middle, with the address you intended to use. Attackers often pick addresses that look similar at a glance, so don't stop at the first two or three.
  2. Trust your hardware wallet's screen, not your computer screen. If you use a hardware wallet, the address shown on the device itself is the one that counts. StepSecurity specifically advised checking the address on the wallet or hardware-wallet screen rather than against what you copied. Our wallets guide explains how hardware wallets work.
  3. Use saved contacts or address books for regular payments. Many wallets and exchanges let you save trusted withdrawal addresses. Some also offer allowlists, where withdrawals can only go to pre-approved addresses.
  4. Send a small test payment first when moving a large amount to a new address, then confirm it arrived before sending the rest.
  5. Close other tabs before sending crypto. Since an infected tab could tamper with your clipboard, a clean browser window adds a layer of safety.
  6. Update your iPhone or iPad. Report URI said iOS 18.7.3 or later, or iOS 26.3 or later, are patched against the exploit kits used here.
  7. Watch your card statements if you paid for anything by card on an affected website on November 16, and contact your bank about anything you don't recognise.

For more everyday habits, see our security guide.

If you think you were affected

If you sent crypto on November 16 after copying an address from a website, open your wallet's transaction history and compare the destination address with the one you meant to use. If they don't match, the transfer may have been redirected. Sadly, there is usually no "undo" button on a blockchain, but you should still report it to the platform you used and to local police or your national fraud-reporting agency, since stolen funds sometimes reach exchanges that can freeze them. Report URI said some of the stolen stablecoins on Ethereum were sent to an exchange deposit address.

Be wary of anyone who contacts you offering to "recover" lost crypto for a fee. Recovery scams often follow big hacks, and they target exactly the people who were just hurt.

The bottom line

The Optimizely incident showed that a trusted website can deliver harmful code without being hacked itself, because one of its outside suppliers was compromised. The direct crypto losses reported so far were modest, about $7,040 according to Report URI, but the reach was enormous. The best defence is simple: never trust a pasted address blindly, confirm it on your hardware wallet's screen, and keep your devices updated. This article is for education only and is not financial advice.

Sources: Report URI (Scott Helme), Nov. 16, 2026; CoinDesk, Nov. 17, 2026; Cointelegraph, Nov. 17, 2026; StepSecurity, Nov. 2026; BleepingComputer, Nov. 2026; Decrypt, Nov. 17, 2026

#security#optimizely#supply chain attack#clipper malware#ledger#address swap#bitcoin#litecoin#dogecoin#ios

Spotted an error? Tell us and we will correct it. See also our disclaimer and beginner guides in Learn.

Related articles

← All articles