0x69a887ad69a8…69a887aa

ConfirmedSecurity661 vB103 sat/vB3 min decode

Optimizely-linked malware reached 178 organizations, including Ledger

Malware tied to Optimizely reached 178 organizations, including Ledger. About $2,300 in victim payments sat within a $7,040 on-chain trail, while hardware-wallet and app exposure remains unclear.

Here’s how Ledger’s website was hit by the Optimizely malware attack
WitnessHere’s how Ledger’s website was hit by the Optimizely malware attackiAmMrRob / pixabay

Outputs

  1. November 16: Ledger’s public site served malware; Scott Helme’s team linked the compromised scripts to 178 organizations.

  2. The separate October device theft reached $91 million across more than 470 cryptocurrency addresses, AMBCrypto reported.

  3. About $7,040 flowed to attack-linked addresses, while Galaxy Digital’s Alex Thorn estimated about $2,300 came from victims.

  4. Optimizely removed the injected code early November 17 after Ledger’s script was cleaned at 20:41 UTC on November 16.

  5. By October 30, Polymarket had fully refunded 689 of 726 affected wallets under a $3.9 million reimbursement program.

By Nathan Brooks

Malware linked by security researcher Scott Helme to website-testing provider Optimizely reached 178 organizations, including Ledger, the BBC and Zoom, after Ledger’s public website was compromised on November 16.

Helme traced the malicious code to compromised scripts associated with Optimizely. The payload could replace a cryptocurrency address that a visitor copied with one controlled by the attacker, then steal card details. A visitor who pasted the substituted address and approved the payment could send crypto to the attacker instead.

Researchers have traced the malware to Ledger’s public website. They have not established whether it also affected Ledger hardware wallets or the Ledger Wallet app. The evidence therefore stops at the website layer and leaves both questions unresolved.

Just over a month earlier, Ledger confirmed that some wallets sold through a reseller contained unauthorized hardware. AMBCrypto reported that the October theft had reached $91 million across more than 470 cryptocurrency addresses. No link between that physical-device incident and the November website compromise has been established.

What does this change for Ledger users?

The practical change is narrow but consequential: the familiar Ledger domain could present a substituted cryptocurrency destination. Users needed to check the destination independently before approving a payment, while the card-detail collection feature created a second risk beyond crypto transfers.

The compromise also does not settle the status of Ledger’s devices or app. Users should not treat the website incident as proof that hardware wallets or the Ledger Wallet app were compromised, nor should they treat it as proof that those products were unaffected.

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 confirmed code removal but did not quantify the remaining investigation or victim impact.

Report URI traced about $7,040 in crypto to addresses linked to the November 16 attack. When Galaxy Digital’s Alex Thorn examined where the funds originated, he estimated that victims sent about $2,300. He said: “Most of the rest was the attacker’s own money. The attacker appears to have been very sloppy with their onchain hygiene.”

That distinction matters because value reaching attacker-linked addresses does not equal aggregate losses. Thorn’s analysis attributes most of the $7,040 to the attacker’s own activity, while the number of Ledger visitors who lost funds remains unknown. Neither figure establishes how many visitors transferred money or the complete loss total.

A similar breach hit Polymarket a few weeks earlier, but the operating mechanics differed. The 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. The company later announced $3.9 million in reimbursements, including about $1.2 million for losses during the pause. By October 30, it said it had fully refunded 689 of the 726 affected wallets.

For Polymarket, the response combined trading restrictions with a disclosed reimbursement program and wallet-level refund count. Ledger’s site has yielded a cleanup time and a limited on-chain estimate, while Optimizely supplied the code-removal statement; no public victim total has emerged.

The comparison makes the difference concrete: one platform could pause activity and report refunds, while Ledger cannot yet quantify visitor losses.

That scale changes the incident from a Ledger-only website problem into a provider-linked containment issue. For practitioners, identifying every affected project is a more useful control than a general assurance that the injected code has been removed.

The next practical checkpoint is a follow-up disclosure from Optimizely, Ledger or other identified organizations that resolves whether exposure remained confined to public websites and whether the Ledger Wallet app or hardware wallets were affected. Until that evidence arrives, copied payment addresses require independent verification.

via cryptonews.net (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,512 articles