The Optimizely attack on 16 November loaded malicious JavaScript onto 188 website scripts belonging to 178 organizations, according to security researcher Scott Helme of Report URI. Zoom, the BBC, CNN, HSBC and hardware wallet maker Ledger were among them. Its code swapped crypto wallet addresses on eight blockchains and skimmed card numbers, and it also served exploit kits to older iPhones. By 19:25 UTC that day, the attacker’s wallets had received about $7,040.
Optimizely said on its status page at 01:02 UTC on 17 November that an unauthorized party “exploited a vulnerability in Experimentation” to add the code to some customer projects. Ledger said private keys on its devices remain protected, so the crypto risk from the Optimizely attack sits with anyone who sent funds from an affected page during the window.
Optimizely’s only public notice on the Optimizely attack still shows Monitoring and gives no count of affected projects, against Report URI’s tally of 188 infected snippets. Source: OptimizelyThe Optimizely Attack Ran for About 17 Hours Through a Signup Flaw
Optimizely Web customers load a snippet from Optimizely’s servers, and each snippet carries an optional Project JavaScript field that runs on every page. The attacker wrote a loader into that field across unrelated customer accounts. Helme saw the first injection on the BBC’s snippet at 04:21 UTC, and by 21:52 UTC only TalkTalk’s snippet still carried the code.
“Optimizely’s CDN served exactly what it was given; this was not a CDN cache-poisoning attack,” Helme wrote. Optimizely spokesperson Victoria Johnson told Gizmodo the flaw sat “in the Experimentation account signup flow.” The status notice says Optimizely has fixed the vulnerability, removed the injected code and taken “steps to secure affected user accounts.” It does not say how a signup flaw gave the attacker write access to other customers’ projects.
Ledger, IG, OANDA and HSBC Were on Report URI’s List of 178
To size the Optimizely attack, Helme scanned 1,611 snippets and found 188 infected, and he wrote that the real count is likely higher. The six crypto and trading names are Ledger, IG, OANDA (listed with Coinpass), interactive investor, TMS Brokers and Betashares. Banking and finance led with 32 organizations. HSBC sites in 11 markets were hit, along with Equifax and ABN AMRO.
Banks, insurers and crypto or trading firms made up 44 of the 178 organizations in the Optimizely attack, about a quarter of the list. Source: Report URI · Chart: FinanceFeedsThe same actor hit other sites through Kissmetrics, StorifyMe and Minute Media scripts from 13 to 16 November, Helme wrote, and those sites are not on his list. HSBC’s content security policy blocked the externally loaded script and the data theft, but an inline copy of the payload still ran.
The Address Swapper Covered Eight Chains and Took About $7,040
The code looked for valid addresses on Bitcoin, Ethereum-compatible chains, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin. It replaced them in page text, forms, the clipboard and outgoing requests. StepSecurity, which also analyzed the code, found it swapped an address only when nearby text carried a payment word such as “wallet,” “deposit” or “send.”
Bitcoin’s 0.0853 BTC, received across five transactions by 19:57 UTC, had not been spent as of 12:50 UTC on 17 November, according to mempool.space. All 17.02 LTC sent to the Litecoin address also stayed put. Helme found the TRON wallet active since March 2026, so the actor behind the Optimizely attack predates this campaign.
Bitcoin accounted for $5,380 of the roughly $7,040 the Optimizely attack had collected by 19:25 UTC, about 76%, with four other chains sharing the rest. Source: Report URI · Chart: FinanceFeedsThe total compares with $8.734 billion stolen across 322 crypto incidents in 2026 through 30 October, per DefiLlama.
Ledger Says Device Keys Stayed Protected in the Optimizely Attack
Ledger’s security team, Ledger Donjon, said on X that “the malicious code is no longer being served through our website,” per U.Today. “This incident does not affect the security architecture of Ledger devices,” it added. “Your private keys remain protected by your Ledger device.” Report URI logged Ledger’s snippet clean of the Optimizely attack code at 20:41 UTC.
A clipper does not touch keys, so it beats a hardware wallet only when the user approves a transfer to the wrong address. “Check the address on your wallet or hardware-wallet screen against the one you meant to use,” StepSecurity advised. That screen is a core feature of devices such as the Ledger Flex. Ledger CTO Charles Guillemet warned of the same address-swapping technique in a September 2025 npm attack, and a December 2023 breach of its Connect Kit library cost users about $600,000, which Ledger pledged to make whole, The Daily Hodl reported.
Investor Takeaway
The Optimizely attack left hardware wallet keys untouched, so crypto losses are limited to transfers approved from affected pages on 16 November, which Report URI put at about $7,040 by 19:25 UTC.
Card Skimming and iPhone Exploit Kits Hit Visitors Beyond Crypto
A card skimmer joined the Optimizely attack payload at 13:43 UTC, capturing card numbers, expiry dates and security codes from forms. Payment fields hosted by Stripe and Adyen were out of its reach, and Helme wrote that he cannot see how many cards reached the attacker’s server. Stolen UK card details already sell for a median £9 on dark web markets, per NordVPN data.
The script also loaded the Coruna exploit kit for iOS 13 to 17 and DarkSword for iOS 18. Hudson Rock “has not independently reproduced those stages or demonstrated compromise of a real victim’s iPhone,” it wrote, per Help Net Security. Report URI found 68 affected hosts ran no content security policy, and only 24 blocked the payload outright.
Coinbase and Gnosis Pay Kept Funds Safe Weeks Before the Optimizely Attack
Coinbase confirmed on 27 October that customer contact details were exposed through its analytics vendor Amplitude, and said wallets and funds were unaffected. Gnosis Pay disclosed a 3 November intrusion into its legacy card system and said: “customer funds were unaffected.”
Binance’s $6.3 billion loss on 29 October did reach custody, and Binance traced it to a compromised DevOps engineer’s laptop. The Optimizely attack code ran in visitors’ browsers, so its losses fell on people sending funds from affected pages.
Investor Takeaway
The Optimizely attack follows the Amplitude leak at Coinbase and the Gnosis Pay card-system breach, and all three exposed customer data or transfers while leaving crypto custody intact.