Data Analytic Investments
RIPPLE book coverRIPPLE — the book·numbered first edition·$29Buy now
Crypto Academy

Crypto clipper malware: how address swapping works, and what the Optimizely incident of 16 November 2026 showed

A third-party script swapped crypto addresses on the websites of 178 organisations. How clipper malware works, why the fake address is still a valid one, and what to check before you send.

D
Data Analytic Investments
••6 min read
Crypto clipper malware: how address swapping works, and what the Optimizely incident of 16 November 2026 showed

On 16 November 2026, JavaScript running on the websites of major brands, including CNN, the BBC, Fox News, Zoom and Salesforce according to BleepingComputer, quietly replaced cryptocurrency addresses with addresses controlled by an attacker (BleepingComputer, 16 November 2026). The code did not come from those companies' own systems. It came through scripts from Optimizely, a web experimentation and A/B testing service that these sites load.

The incident is a useful moment to explain one basic idea: what clipper malware (address-swapping malware) is, how it works, and what a user can check before sending a transfer.

Data sheet
EventMalicious code in Optimizely Web customer scripts
Date16 November 2026, first injection seen at 04:21 UTC
Infected script files188 (out of 1,611 examined)
Organisations affected178
Chains covered by the codeBTC, ETH and EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Cash, Dogecoin
Received by attacker addressesabout $7,040 (up to 19:25 UTC, 16 November)
Clean-up1 of 188 files still infected at 21:52 UTC
Provider status"Monitoring", 17 November 2026, 01:02 UTC

Sources: Report URI, 16 November 2026, Optimizely Status, 17 November 2026

What is clipper malware?

Clipper malware is a program or script that looks for crypto addresses and, wherever it finds one, replaces it with another. You copy or see one address, but what you paste is already the attacker's.

According to Report URI's analysis, the 16 November code went well beyond the clipboard. It swapped addresses in page text, form fields, links, images, outgoing network requests and the iOS share sheet (Report URI). A SecurityOnline summary says the swap was triggered when an address appeared near payment words such as "wallet", "deposit" or "send" (SecurityOnline, 17 November 2026).

The code did more than that. It tried to capture payment card details, sent cookies and screenshots to attacker servers, and loaded further exploit code on iPhones and iPads (BleepingComputer). This article covers only the address swapping.

Why did it happen on trusted websites?

Modern websites load a lot of outside code: analytics, advertising, A/B testing. If malicious code gets into one of those providers, it runs on every customer site that loads the script. This is called a supply-chain attack.

Optimizely said an unauthorised party exploited a vulnerability in its account signup flow to add malicious JavaScript to some customer projects (BleepingComputer). The company says it has fixed the vulnerability, removed the injected code and secured affected accounts (Optimizely Status).

The point for users: a well-known, legitimate website is not a guarantee that every address shown on it is correct.

Why a checksum does not help

Many crypto address formats include a checksum. It protects against typos: change one character and the wallet flags the address as invalid.

Report URI found that the 16 November code validated address checksums and swapped in valid attacker addresses (Report URI). The attacker's address is formally correct, so the wallet shows no error. There is nothing for it to object to: you would be sending to a real, valid address.

A checksum tells you whether an address is valid. It does not tell you whose it is.

What to check before you send

These are general security practices, not instructions tied to any particular provider.

  1. Read the address on the wallet's own screen, not in the pasted text. With a hardware wallet, the address on the device display is the one that counts, because code running in the browser cannot change it.
  2. Compare the whole address, not just the first and last few characters. A handful of matching characters does not make two addresses the same.
  3. Confirm through a second channel. When paying someone, check the address with them by a route other than the same page or message.
  4. Use the wallet's address book for regular recipients. An address you have already checked and saved does not need to be copied from a website each time.
  5. Send a small test amount before a larger one. If the recipient confirms the test arrived, the address is right.
  6. Keep devices updated. BleepingComputer advised iPhone and iPad users to install the latest system updates (BleepingComputer).

Anyone who copied a crypto address from an affected site on 16 November was advised by BleepingComputer to check the destination addresses of that day's transfers (BleepingComputer).

Clipper or address poisoning?

The two are often confused. Clipper malware swaps the address on your device or in the page you loaded. Address poisoning works differently: the attacker sends tiny transfers from an address that looks similar to a real one, hoping you will later copy it from your transaction history. The defence is the same in both cases: check the full address against a trusted source.

What the incident does not show

  1. The amount is not the total loss. The roughly $7,040 is what reached the attacker addresses. BleepingComputer notes some of those addresses were active before the attack, so it is unclear how much came from this campaign.
  2. Nobody has published visitor numbers. It is not known how many people loaded the infected pages.
  3. These are first-day figures. They come from researchers and press reports and may be revised. Reports already differ on the number of organisations.
  4. It was not a blockchain failure. Bitcoin, Ethereum and the other chains worked as described; the problem was in code loaded into websites.
  5. The practices above reduce risk; they do not remove it. On an infected device, care alone does not cover everything.

Summary

  • On 16 November 2026, code delivered through Optimizely scripts swapped crypto addresses on the websites of 178 organisations.
  • Clipper malware swaps in valid addresses that pass checksum checks, so the wallet shows no error.
  • The single most useful step: read the full address on the wallet's or hardware wallet's own display.

Related reading: Blog archive.

Sources

Data Analytic Investments is not affiliated with the companies or sites referenced; names are used for identification only.

Educational content, not investment advice.

Explore Topics

#clipper malware#address swapping#crypto address#supply-chain attack#Optimizely#security#wallet#clipboard
D

Written by

Data Analytic Investments

Content creator and writer sharing insights and stories.

Share · Megosztás:XFacebookLinkedInWhatsAppTelegramE-mail