Coineighbour

Lightning, payment channels, crypto settlement, wallet payment features and real usage

Optimizely Script Attack Replaced Crypto Payment Addresses on Affected Websites

An attack on Optimizely’s Web Experimentation product put crypto payments at risk by changing the destination address a visitor saw or copied. As reported on November 17, 2026, affected websites included hardware-wallet maker Ledger, but the malicious code was delivered through Optimizely’s servers—not through a reported breach of those websites’ own systems.

Optimizely said an unauthorized party exploited a vulnerability to add JavaScript to some customer projects. The company said it blocked the vulnerable path, removed the code, secured affected accounts and contacted customers. Spokesperson Victoria Johnson told Gizmodo the vulnerability was in the Experimentation account signup flow. Optimizely had not explained how the attacker gained access to other customers’ projects.

According to security firm Report URI, the script replaced valid wallet addresses displayed on pages across networks including Bitcoin, Ethereum, Tron, Solana and TON. It also changed addresses copied to a visitor’s clipboard. A sender who pasted an address while an affected page was open could therefore have sent funds to the attacker instead of the intended recipient. The report concerns wallet-address substitution; it does not describe a Lightning payment or channel failure.

Report URI founder Scott Helme said researchers found the code in 188 of 1,611 Optimizely scripts examined, associated with 178 organizations. The affected sites included the BBC, CNN, Zoom, Salesforce, GitLab, IKEA and HSBC, alongside Ledger, IG and OANDA. Report URI said the attacker’s wallets received about $7,150 in crypto, mostly Bitcoin, Litecoin and USDT, and were emptied early on November 17. The firm linked one Tron cash-out address to earlier operations in March and on November 3.

The script also skimmed card details entered into some websites’ own payment forms, but not details entered into hosted fields such as Stripe’s. On iPhones and iPads, it attempted to load exploit kits targeting older iOS versions. Report URI said it could not determine how many card numbers were stolen or devices compromised.

Report URI first saw the injected code early on November 16 UTC and said it was gone from all scripts it could find by late that evening. Helme advised people who visited affected sites on November 16 to check any crypto transfers they made, update their iPhones and iPads, and monitor card statements. He advised website operators to review custom code in their Optimizely projects and rotate credentials.