An Optimizely Flaw Put Crypto-Stealing Code on 178 Websites
Attackers used a flaw in Optimizely's website experimentation software to put crypto-stealing JavaScript on the sites of 178 organisations, the security firm Report URI reported on Monday. The code swapped cryptocurrency wallet addresses shown on a page for the attacker's own, skimmed card numbers out of payment forms, and sent cookies and screenshots to a server the attackers controlled. Optimizely confirmed the incident on Monday evening and said the injected code had been removed. The money taken is small. Four counts of it sit near $7,000, and no two agree.
What the code did once it loaded
Scott Helme of Report URI checked 1,611 Optimizely snippets and found the injected loader in 188 of them, and said the true number is probably higher. Neither CoinDesk nor The Record carries one. The payload sat in Project JavaScript, the field where an Optimizely customer adds its own code, and came off the company's content delivery network. A site using it was compromised without its servers being touched. The main component was a clipper, a program that substitutes one wallet address for another when a payment is set up, working on the page and on anything a visitor copied. Every account names bitcoin, ether, solana and tron among the targets. The chain count is not settled, running from five to eight across them. A card skimmer was bolted on at 13:43 UTC on 16 November, a time two accounts give. On iPhones and iPads the code delivered two iOS exploit kits, Coruna and DarkSword, aimed at older devices.
Four counts of the money, hours apart
Report URI put the haul at about $7,040 by Monday evening, mostly in bitcoin, the figure CoinDesk carried while noting Bloomberg could not verify it. StepSecurity valued the receipts at about $7,122 by 08:30 UTC on Tuesday, on one outlet's reading of its write-up. The Record said at least $7,000; CoinPaprika put estimates between $6,600 and $7,150. They do not reconcile. The hours behind them differ, so quoting one alone would misstate a total that moved while the code was live. One account has the bitcoin, ether and litecoin addresses emptied by 05:39 UTC on Tuesday. No second outlet carries that, and it stands unverified.
Optimizely's account of it
The company posted that it had identified and contained a security incident affecting some customers of its Web Experimentation product. A technical advisory on its status page confirmed that a vulnerability there let malicious JavaScript be injected into customers' websites.
"The vulnerable path is blocked, the injected code was removed, and customers have been contacted directly," the company said.
The statement does not say where the flaw was. CoinDesk attributes to the company an account locating it in Optimizely's account signup flow. One outlet states that flatly with no attribution, another says the company has given no mechanism, and The Record, which quoted the statement, does not mention signup. The accounts do not reconcile on who located it there, and Optimizely did not answer The Record's questions about Report URI's work. The cleanup ran past the notice, too. One account dates the incident post to 01:02 UTC on Tuesday and has the status page still reading monitoring at 07:30 UTC; another says the files appeared on 16 November and were cleared that day. Both cannot be right.
What nobody can measure
Every name on the list traces back to Report URI's findings, not the firms themselves. CoinDesk names HSBC, Salesforce, the BBC and the hardware wallet maker Ledger, with 32 more described as banks and financial companies. The Record gives the same count of 32 and names nobody. Optimizely, Ledger and HSBC did not immediately answer CoinDesk's requests for comment. Helme called the malware a multi-purpose kit, then said the part that matters most: there is no way to see how many cards were skimmed, how many cookies and screenshots were taken, or how many iOS devices were infected. Hudson Rock dated an earlier wave of similar code to 13 November. The pattern is not new here; Blockaid named 12 DeFi front ends serving a drainer through infrastructure none of them owned. The dollar figure will stay small. The count of exposed cards may not be knowable.
Read also: Phishing Emails Reached Trezor Users From Trezor's Own Domain