One Signup Flaw, Three Big Names, Zero Known Total: The Optimizely Address-Swap Mess
A signup flow bug at Optimizely let an attacker plant address-swapping code on pages run by HSBC, the BBC and Ledger. Nobody has published the stolen total, and investigators say AI had nothing to do with it. The boring layer just broke, and crypto is paying for it again.
How does a signup form end up draining crypto wallets?
That's the question I keep circling back to after learning that a flaw in Optimizely's signup flow let an attacker slip address-swapping code onto pages belonging to HSBC, the BBC, and Ledger. Not a zero-day. Not a poisoned open-source package. A signup form. The front door, left slightly ajar.
The question worth asking: if that's all it took to plant malicious script on a major bank, a national broadcaster, and the best-known hardware wallet maker in crypto, what exactly are we trusting when we plug a device into a laptop and call it self-custody?
The Raw Numbers, Such As they're
Here's what we know, and it's thinner than you'd like. Three marquee properties confirmed as affected. One attacker. Address-swapping code, which is the oldest trick in the crypto theft playbook: swap the recipient address sitting in a clipboard, let the victim paste, watch the funds leave.
Total stolen: unknown. Investigators haven't linked the attack to AI, which is worth flagging, because every incident this year seems to get blamed on a model somewhere. This one looks like plain, human, tedious exploitation.
Scope is where the story turns uncomfortable. Optimizely isn't a niche tool. It's an experimentation and personalization platform used by thousands of brands to run A/B tests and page variations. If a signup flow was the weak link, then the blast radius isn't three websites. It's every site where the same flow existed. And nobody has published that list.
Ledger matters most here, obviously. The company has sold millions of hardware wallets on a single promise: your keys, your coins, nobody else's. Its devices were never the breach point. Its website was. That distinction matters legally, and it matters psychologically, but it doesn't matter much to the user who pasted the wrong address and hit send.
Why Crypto Always Eats This First
Address swapping is boring malware. It's been around since at least 2017, living quietly in browser extensions and clipboard hijackers, and it works because crypto addresses are long, opaque strings that humans can't verify by eye. So we copy and paste. That's the entire attack surface. A user's trust in their own clipboard.
Traditional finance has friction that saves it. A bank transfer carries a name, an account number, a sort code, a confirmation screen, sometimes a phone call. Crypto carries a hex string and a send button. The friction got removed in the name of usability, and usability is where the thieves live.
But here's the part that should bother the proponents of self-custody more than the skeptics. Hardware wallets solved key management. They didn't solve the display problem. You still can't fully read what you're signing on most devices. You trust the screen, the screen is fed by software, and the software was served from a website that had a signup flaw. The hardware track record on key custody is excellent. The track record on everything upstream of the screen is thinner.
So the attack didn't break cryptography. It broke the layer everyone assumed was boring. Almost every major crypto loss traces back to that layer: a form, a plugin, a DNS record, a support desk.
What Security People Are Saying
According to researchers who track supply chain compromises, the pattern is familiar by now. Threat actors have stopped trying to break the exchange and started trying to break the vendor that serves the exchange. One compromised SaaS integration can touch hundreds of downstream customers, and each of those customers has its own auditors, its own compliance team, and its own false sense of coverage.
Security teams I've talked to over the years keep making the same point. Third-party scripts are the least audited code on any financial website. Marketing owns them. Engineering tolerates them. Legal doesn't know they exist. And they run with full page privileges.
Color me skeptical, but I don't think this incident changes that structure. Companies will patch, publish a post-mortem, and quietly re-sign the same vendor contract next quarter. The incentive to remove the widget is close to zero and the cost of leaving it's invisible until it isn't.
Ledger, for its part, has built a brand on the thesis that custody is the only thing that matters. This is a reputation test more than a technical one. Its customers are, by temperament, the people most paranoid about exactly this scenario.
What to Watch From Here
Three concrete things.
First, the site list. Until Optimizely publishes the full inventory, or an independent researcher reconstructs it from public script signatures, every company running the same flow is operating blind. Watch the disclosure timeline closely. Companies tend to publish these on a Friday afternoon for a reason.
Second, on-chain forensics. Address-swapping campaigns usually consolidate into a small cluster of wallets before moving through mixers or bridges. If analysts tag those clusters within the next few weeks, we'll get the first real estimate of the stolen total. That number is the story.
Third, insurance. Cyber policies typically cover data breach and business interruption. They're murkier on customer asset loss caused by a third-party widget. If claims get denied, watch how fast procurement teams start asking harder questions about their script inventory.
And one thing that isn't happening. There's no AI angle here, and that's the most interesting detail in the whole mess. We've spent two years being told machine learning would industrialize cybercrime. This attack was a signup form and a clipboard. The old methods still work because the old mistakes never got fixed.
The number nobody has published yet is the one that decides whether this was an embarrassment or a disaster.
Explore More
Key Terms Explained
An Ethereum Layer 2 that offers native yield on ETH and stablecoins deposited on the chain.
Following the laws and regulations that apply to financial activities, including crypto.
Who holds and controls your crypto assets.
A marketplace where cryptocurrencies are bought and sold.