178 Sites, One Hijacked Script, and the Clipboard Problem Crypto Still Won't Fix
A supply chain attack quietly planted address-swapping and card-skimming malware on 178 major websites through a third-party script. The crypto angle is the headline. The card-skimming is the actual business. And the clipboard is a design failure nobody wants to fix.
I spent a solid twenty minutes last week staring at a recipient address before I hit send. Not because I didn't trust the person on the other end. Because I didn't trust the clipboard.
Turns out that paranoia was well calibrated.
Researchers flagged a campaign this week that planted malware on 178 major websites. The entry point wasn't a compromised server farm or a browser zero-day. It was a script. A third-party script delivered through Optimizely, the experimentation and personalization vendor that a huge slice of the commercial web quietly leans on to run A/B tests.
Once the attackers had a foothold in that delivery chain, they pushed a payload with two jobs. One watched the clipboard and swapped crypto wallet addresses for ones they controlled. The other skimmed payment card details straight out of checkout forms.
This is what onboarding actually looks like. Except nobody signed up for it.
Two Thefts, One Payload
Let's get into the mechanics, because the mechanics are where this gets interesting.
Clipboard hijackers, often called clippers, are old malware with a new target. They sit in memory, monitor what you copy, and when they detect something shaped like a wallet address, they swap it. The sloppy versions do a blunt find and replace. The good ones match the first four and last four characters, because the malware authors know exactly what a nervous user checks before sending.
That's the detail that should bother you. The attacker isn't just stealing. They're modeling your behavior.
Then there's the card side, which is the part that gets underreported. Loading a script from a trusted domain means it slides past a lot of defenses that would catch injected code. No weird redirect. No sketchy checkout page. Your browser thinks it's talking to the tool it's been talking to for years. Formjacking has been the go-to for this class of attack since the Magecart era, and it still works because the underlying weakness never changed. Every site that pastes a vendor snippet into its CMS is accepting a stranger's code into its payment flow.
178 sites sounds small next to the thousands Magecart touched. Size of count isn't size of damage. Blast radius here's a function of traffic, not quantity. A couple hundred high-traffic destinations means millions of sessions exposed before anyone notices.
And the discovery timeline is always the ugly part. Supply chain attacks don't get detected at minute one. They get detected after someone notices money that left without permission.
Who Actually Eats This
Pull the camera back for a second.
The natural read is that this is a crypto story. Address swapping, wallets, on-chain losses. But the crypto half is the smaller ledger. Card fraud has chargebacks, fraud teams, and liability rules that shift losses to issuers and processors. Crypto transfers are final. There's no dispute window on a signed transaction.
So here's what I think the scoreboard looks like.
Winners: hardware wallet makers, security vendors doing address verification, and, and this is the uncomfortable one, custodial exchanges. Because you can't clipboard-swap a transfer that happens inside an account. Every time self-custody gets punished by a dumb UX problem, the case for handing your keys to a company quietly gets stronger.
Losers: anyone defending the current address format, small merchants running checkout on old CMS setups, and Optimizely's sales team for at least two quarters. Supply chain vendors absorb reputational damage even when the compromise isn't their fault. That's the price of being in the path.
Who wins in the long run? Whoever treats this as a product problem instead of a user education problem. Because telling people to double check 42 characters isn't a security control. It's a prayer.
What I'd Actually Do
Here's my honest take, and it's a hot one. The crypto industry has had the tools to kill address clipping for years and keeps shipping the same broken interaction.
Address books with contact verification. Name services that resolve to a readable string. Checksum validation at paste. Hardware wallets that display the full address on a secure screen while the host machine stays untrusted. All of it exists. Almost none of it's the default path in the wallets people actually use every day.
So why does this keep working? Because the primary interaction in crypto is still copy, paste, hope.
That's a design failure, not a user failure. And the industry has decided it's cheaper to blame users than rebuild the flow.
If you're trading or holding right now, a few concrete things. Use an address book. Verify the first and last six characters on the hardware screen, not on your laptop. Send a small test amount first, even if it feels stupid, especially if it feels stupid. And don't paste card details into any checkout without asking why a site is loading scripts from four different domains.
For the builders reading this, the meta shifted. Wallet UX is security now. A beautiful mobile app that asks users to eyeball hex strings is a liability with a gradient and a custom font.
One more thing worth saying, because it usually doesn't get said. The people who fix this won't get a single headline. Address verification tooling doesn't pump a token or get a mention on a timeline. It just quietly stops thefts nobody will ever hear about.
The builders never left. Most of them are working on stuff you'll only notice when it doesn't break.
Floor price is a distraction. Watch the utility. That applies to wallets too.
Explore More
Key Terms Explained
An Ethereum Layer 2 that offers native yield on ETH and stablecoins deposited on the chain.
Who holds and controls your crypto assets.
The lowest price at which an NFT in a collection is listed for sale.
A physical device that stores cryptocurrency private keys offline.