On 16 November 2026, malicious JavaScript served by means of Optimizely’s Internet experimentation platform reached guests of 178 organisations, together with {hardware} pockets maker Ledger, in line with Report URI, the safety agency that discovered the contaminated code. The script swapped cryptocurrency pockets addresses for the attacker’s personal when folks copied them, and it additionally skimmed cost card particulars typed into web site varieties.
- The information: Report URI discovered malicious JavaScript being served to guests of 178 organisations by means of Optimizely’s experimentation platform on 16 November 2026.
- The important thing determine: 188 contaminated snippets belonging to 178 organisations, out of the 1,611 distinct Optimizely snippets Report URI fetched and checked.
- What occurs subsequent: Optimizely says it has blocked the weak path and deployed a repair, whereas researchers have nonetheless not established how the attacker obtained in.
Ledger’s Snippet Was Considered one of 188
Report URI’s listing reads like a listing of web sites folks already belief. Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock are among the many 178 organisations. For a crypto reader, Ledger is the one which issues, as a result of the malicious code did one thing particular to wallets.
The clipper script discovered legitimate pockets addresses for BTC, ETH and EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Money and Dogecoin and changed them with the attacker’s. It did that in web page textual content, type fields, hyperlinks and pictures, in the clipboard, and in outgoing requests. That’s the copy-and-paste step the place a {hardware} pockets is supposed to be the final line of defence: you copy an handle, you verify it on the system, you ship.
There is no such thing as a affirmation that any Ledger {hardware}, firmware or non-public keys had been compromised. The assault lived on the web site, not in the system, and a reader who checked the handle on their {hardware} display earlier than sending would have caught the swap. Report URI’s depend is certainly one of a number of: it discovered 188 snippets throughout 178 organisations, whereas different tallies put the confirmed web site depend barely decrease, as a result of the figures measure various things.
Why the Trusted Host Made It Worse
The attacker wrote their very own code into the Venture JavaScript discipline of buyer Optimizely initiatives and left the remainder of every snippet untouched, Report URI mentioned. The recordsdata had been nonetheless served from cdn.optimizely.com, with Optimizely’s certificates, from a bunch each affected web site already trusted. Optimizely’s personal www and login websites carried the code too, and Report URI mentioned this was not a CDN cache-poisoning assault.
Guests on iPhones and iPads confronted a second stage: the script loaded code linked to the Coruna and DarkSword iOS exploit kits, Report URI discovered. StepSecurity’s timeline reveals the payload was rebuilt 26 occasions in the course of the day, with the monitor.js file rising from 28,877 bytes at 16:02 UTC to 30,430 bytes at 18:11 UTC.
The Crypto Take Stayed Small
For all of the attain, the addresses tied to the malware collected little. StepSecurity put the funds obtained or held throughout the attacker’s BTC, LTC, ETH and TRX addresses at about $6,600 at 16 November costs, and famous that some addresses had exercise predating the assault. Alex Thorn, head of firmwide analysis at Galaxy Digital, estimated victims despatched solely about $2,300 in whole. The estimates disagree, and no single determine is settled.
Optimizely’s Response and What To Watch Subsequent
Optimizely has confirmed the incident. It mentioned an unauthorized get together added malicious JavaScript to some buyer initiatives and that it has blocked the weak path and deployed a repair, although its public discover doesn’t describe the signup-flow mechanism that has been reported however not confirmed.
StepSecurity mentioned it had “not established how the Optimizely-hosted files were modified”. That sentence issues most for anybody weighing the chance: with out understanding how the attacker reached the Venture JavaScript discipline, there is no such thing as a means to make certain the identical route is closed.
Equifax investigated and stopped utilizing Optimizely, saying it discovered no proof of compromise to its methods. Salesforce mentioned it was investigating unauthorized adjustments to Optimizely scripts on a few of its websites and disabling them as a precaution. It’s not but clear whether or not the code was efficiently used towards guests in each case.
For now, the open query is the entry route. Till Optimizely or the researchers title it, the helpful takeaway is narrower: an handle proven on a trusted web page is just not the identical as a verified one, and the system display remains to be the place the verify occurs.













