Security Hub

Ledger Among 178 Brands Hit by Crypto-Stealing Website Malware

Published: Nov 17, 2026•By Aleksandar Dukic

Key Analysis

Ledger, Zoom, BBC and HSBC were among 178 brands hit through Optimizely scripts. The malware swapped crypto addresses and stole payment data from visitors.

Ledger Among 178 Brands Hit by Crypto-Stealing Website Malware

Listen To This Article

Ledger Among 178 Brands Hit by Crypto-Stealing Website Malware

4m 40s audio

AI narration. Useful for scanning on the move. Names and tickers may be mispronounced.

Ledger, Zoom, the BBC and HSBC were among 178 organisations whose websites served malicious JavaScript through Optimizely on November 16, according to researcher Scott Helme at Report URI. The code replaced cryptocurrency addresses and collected payment data. The reported compromise involved website scripts; the findings provide no evidence that Ledger hardware wallets were breached.

For crypto users, the immediate concern is the payment destination presented before approval. An address can look ordinary, pass a wallet's format checks and still belong to the wrong recipient.

Trusted website scripts carried the attack

Report URI traced the injection to the Project JavaScript field in customers' Optimizely projects. Browsers received the altered snippets through a domain the affected websites already trusted. The researchers had not determined how the attacker obtained access to those projects.

The payload could replace addresses in page content and the clipboard. It also skimmed card details entered into ordinary website forms, although hosted payment iframes were outside that component's reach. Report URI recorded Ledger's snippet being cleaned at 20:41 UTC on November 16.

Recognising a website's name is no guarantee that its payment instructions are trustworthy. A familiar site and checkout can still depend on code supplied elsewhere.

This changes the question a wallet holder needs to ask. Checking whether an address is valid only establishes that the wallet can use it. Verifying ownership requires a separate check with the intended recipient. A technically valid transfer can complete exactly as approved while paying the attacker.

A hardware confirmation needs an independent reference

Ledger's standing transaction guidance tells users to assume their computer could be compromised. It recommends checking the recipient address, amount and fees on the hardware wallet, and checking addresses again after copying and pasting.

The company also recommends obtaining a recipient address through a secondary communication channel and sending a small amount first. Before transferring a larger balance, the sender should confirm that the intended recipient received that test payment.

Those steps answer different questions. Comparing the device display with the intended destination checks the transaction awaiting approval. Confirming receipt checks that the destination actually reaches the person or account being paid. A successful broadcast alone is insufficient for that second check.

There is a trap in comparing two displays that both inherited the same substituted address. Agreement between them would only confirm consistency. The reference needs to come from the intended recipient through a route the sender has reason to trust.

Receiving funds deserves similar care. Ledger advises displaying a receiving address on the hardware device because addresses shown by wallet software can be manipulated on a compromised computer.

For people using self-custody options, this draws attention to the full payment process. Keeping control of signing still requires establishing who will receive the transfer. Approving a payment means approving both its destination and the amount to spend.

Clipboard checks can reveal trouble without clearing a device

MetaMask's security documentation describes clipboard malware that watches for cryptocurrency addresses and substitutes an attacker's destination. It recommends testing copied addresses in the device's default text editor.

A user can first copy and paste ordinary text, then copy a wallet address and compare the pasted result with the original. A mismatch is a reason to stop transferring funds and investigate the device using guidance from its manufacturer or operating-system provider.

MetaMask cautions that this test can miss malware designed to activate only in particular applications. Passing the test therefore shows only that the specific paste operation produced the expected result.

Its guidance also recommends keeping the operating system and anti-malware software current, while continuing to check addresses before confirming transactions. These are general precautions, rather than a forensic test for this particular website incident.

For someone reviewing a recent payment, the useful comparison is between the destination recorded in the transaction and the address the intended recipient independently confirms. Repeating the original copy-and-paste process would leave the same point of failure in place.

The response should depend on what that comparison reveals. An altered address calls for investigating the transfer and the device used to prepare it. A matching address should still be checked with the recipient before another payment follows.

Overview

Report URI identified a website supply-chain attack affecting 178 organisations, including Ledger. Its findings put browser-delivered payment instructions at the centre of the incident. Ledger's published guidance calls for checking transaction details on the device and confirming receipt of a small test transfer before sending more.

DisclaimerThis article is provided for informational purposes only and does not constitute financial advice. All fee, limit, and reward data is based on issuer-published documentation as of the date of verification.

Have a question or update?

Discuss this analysis with the community on X.

Discuss on X

Comments

Comments are moderated and may take a moment to appear.