0x052958d20529…052958cf
Ledger Malware Linked to 178 Organizations; $7,040 Traced
A compromised Optimizely script infected Ledger’s public website on November 16, exposing crypto addresses and card data. Researchers traced about $7,040, but visitor losses remain unknown.

Outputs
Ledger’s public website was infected with address-swapping and card-detail-stealing malware on November 16.
Scott Helme linked compromised scripts to Optimizely and 178 organizations, including Ledger, the BBC and Zoom.
Report URI traced about $7,040, while Alex Thorn estimated that victims sent about $2,300.
Report URI recorded cleanup of Ledger’s script at 20:41 UTC on November 16.
Polymarket announced $3.9 million in reimbursements and fully refunded 689 of 726 affected wallets by October 30.
Report URI traced about $7,040 in crypto to addresses linked to the November 16 malware attack on Ledger’s public website, part of a vendor incident involving compromised scripts tied to 178 organizations.
Security researcher Scott Helme traced the malicious code to Optimizely, a website testing provider. His team found compromised scripts tied to 178 organizations, including Ledger, the BBC and Zoom.
What did Ledger visitors face?
On November 16, Ledger’s public website served malware designed to replace a copied cryptocurrency address with an attacker-controlled destination and steal card details. The swap required a visitor to paste an address and approve the resulting payment before crypto would go to the attacker rather than the intended recipient.
The mechanism limits what the traced balance can prove about total exposure. Available reporting gives no quantified card theft and no complete count of visitors who lost crypto or submitted payment data. The practical loss boundary remains unknown.
Were wallets or devices affected?
Researchers have so far traced the malware only to Ledger’s public website. They have not established whether it also affected Ledger hardware wallets or the Ledger Wallet app.
Any claim of a broader device compromise would therefore outrun the available evidence.
Just over a month earlier, Ledger faced a separate attack involving physical devices. The company confirmed that some wallets sold through a reseller contained unauthorized hardware. At the time, AMBCrypto reported that the October theft had reached $91 million across more than 470 cryptocurrency addresses.
Nothing reported links the device incident to the November website compromise. The two events create different risks and should not be treated as one compromise.
When was the malicious code removed?
Report URI recorded the cleanup of Ledger’s script at 20:41 UTC on November 16. Early on November 17, Optimizely said:
“We've fixed the vulnerability and removed the injected code from affected projects.”
The statement addresses code removal, but not a full accounting of visitors exposed or crypto lost. It does not say whether payment data was taken, and it supplies no disclosure deadline for affected organizations. The cleanup timestamp establishes a remediation point, not the financial cost.
How much did visitors actually lose?
Report URI traced about $7,040 in crypto to addresses linked to the November 16 attack. Galaxy Digital’s Alex Thorn estimated that victims sent about $2,300 after examining where the money came from.
Thorn said:
“Most of the rest was the attacker’s own money. The attacker appears to have been very sloppy with their onchain hygiene”
The gap matters because blockchain tracing captured more than victim deposits. The number of Ledger visitors who lost funds remains unclear, and no final card-loss figure has been reported. The $7,040 amount is a traced balance, not a verified victim-loss total.
What did the Polymarket breach show?
A similar breach hit Polymarket a few weeks earlier, but its malicious code could act on behalf of traders who were already signed in. On October 29, it sold some traders’ positions and moved funds out of their wallets.
Polymarket paused international trading to stop further losses. It later announced $3.9 million in reimbursements, including about $1.2 million for losses during the pause. By October 30, the company said it had fully refunded 689 of the 726 affected wallets.
The Polymarket episode shows that code operating inside active sessions can monetize access without a visitor manually pasting a fraudulent address. It does not, however, establish how many Ledger visitors lost money or submitted card data. The comparison defines the shared-vendor risk without resolving Ledger’s exposure.
No enforcement deadline has been disclosed. The next material checkpoint should be a verified inventory of the 178 linked organizations, including script removal and any card-data exposure; until then, the $7,040 trace is not a loss ceiling.
via ambcrypto.com (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles