Optimizely Hack Targeted Crypto Payments on Sites Linked to 178 Organizations

The Optimizely hack exposed visitors to websites associated with HSBC, Ledger, Zoom and other major brands to malicious code on Monday, 16 November. The attack spread through a service companies use to test and personalize their web pages. The code was designed to redirect cryptocurrency payments, capture card details and target iPhones and iPads. Security researchers at Report URI traced the affected website scripts to 178 organizations. Reuters reported on the findings on 17 November.
Optimizely confirmed that someone exploited a vulnerability in its Web Experimentation service to add malicious code to customer projects. In an update at 6:32 a.m. IST on Tuesday, the company said it had fixed the vulnerability, removed the injected code and taken steps to secure affected accounts. The incident was listed as under monitoring when this report was prepared.
How one compromised service reached so many sites
Businesses use Optimizely Web Experimentation to compare page designs, test checkout changes and show different versions of a page to different visitors. To make those tests work, a website loads a small piece of code supplied by Optimizely. A visitor can be on a familiar company’s website while their browser also runs code supplied by that company’s vendors.
That arrangement gave the attacker a way to reach multiple websites through a shared service. Report URI researcher Scott Helme said his team checked 1,611 Optimizely scripts and found malicious code in 188 of them, associated with 178 organizations. Those figures describe what the researchers found in the scripts they examined. The number of individual visitors exposed is unknown, and 178 is a count of organizations, some of which had more than one affected script.
Report URI traced its earliest observed injection to a BBC script at 9:51 a.m. IST on Monday. Most of the affected scripts it was tracking had been cleaned up by early Tuesday morning in India, ahead of Optimizely’s public update. Those observations show when researchers saw the code appear and disappear. Each site’s exposure window may have differed.
How the attack tried to divert crypto payments
A wallet address tells the network where to send a payment. The malicious code could substitute an address controlled by the attacker for the intended recipient’s address on an affected page or when someone copied it. A visitor could then authorize a transfer in their own wallet while believing they were paying the original recipient. The wallet would process the address the user approved.

That is how a website incident can lead to a loss even when a hardware wallet functions as designed. Ledger’s appearance on the researchers’ list concerns a website script. The reporting reviewed for this article does not establish that Ledger hardware, wallet backups or private keys were compromised. Cointelegraph’s coverage also named Coinpass and several trading platforms among the organizations associated with affected scripts.
The loss figures are less certain than the list of affected scripts. Cointelegraph found roughly $7,100 in Monday receipts at addresses linked to the campaign and reported that some addresses had activity before the incident. It also cited a lower estimate of transfers from victims. A total received by an address can include the attacker’s own transfers, so the amount lost by visitors remains unconfirmed.
Card payments, iPhones and the companies named in the report
The researchers found code designed to capture payment card information entered into some affected pages. They also found that the campaign attempted to deliver malicious code to visitors using iPhones and iPads. Reuters said it could not independently establish where the attempts succeeded or the extent of the resulting compromises. Public reporting has yet to establish how many card details were collected or how many devices, if any, were compromised.
HSBC was among the organizations named in the research. A finding about code served to website visitors does not by itself establish access to the bank’s internal systems or customer accounts. Salesforce told Reuters it was investigating unauthorized changes to Optimizely scripts and had disabled the scripts as a precaution. Equifax told Reuters it stopped using the service and had found no evidence that its systems were compromised. The response from each organization matters because the scripts and pages in use varied across sites.
What visitors can check now
- If you sent crypto using an address from an affected page, compare the destination in your transaction history with an address verified independently with the recipient. Keep the transaction ID, amount and time. If the addresses differ, contact the recipient or exchange using its official support channel.
- If you entered card details or notice an unfamiliar charge, contact your card issuer through its official app or the number printed on your card. Your issuer can review the activity and advise on blocking or replacing the card. In India, suspected financial cyber fraud can also be reported through the National Cyber Crime Reporting Portal or by calling 1930.
- If you visited on an iPhone or iPad, check for available updates under Settings, General, Software Update. Apple publishes security release information for supported devices.
- If someone contacts you offering to recover crypto, go directly to your wallet provider’s official support site. Keep your recovery phrase and private keys to yourself.
Optimizely’s fix and what remains unknown
Optimizely says it removed the malicious code from affected projects and added protections against further unauthorized changes. Its notice did not give a total for affected visitors or confirmed losses. Further statements from the companies whose sites were named may clarify which pages were affected and whether customers need to take specific action.
For a related example of how a third-party provider can affect a familiar crypto service, see Trading Turtle’s reporting on the Coinbase India INR withdrawal disruption. That was a separate banking-partner outage. Follow Trading Turtle’s Market Insights for more coverage of crypto and market developments.



