0x06d083c006d0…06d083bd

ConfirmedSecurity625 vB176 sat/vB3 min decode

Optimizely Script Flaw Exposed 178 Sites to Wallet-Swapping Malware

Attackers used Optimizely's signup flaw to push wallet-swapping malware to 178 sites including HSBC and Ledger, netting about $7,040 in Bitcoin.

Optimizely’s web-testing flaw exposed 178 sites to crypto theft via malware
WitnessOptimizely’s web-testing flaw exposed 178 sites to crypto theft via malwarevickygharat / pixabay

Outputs

  1. A flaw in Optimizely's signup flow exposed 178 organizations' websites on November 16, 2026.

  2. The malware swapped wallet addresses across nine networks including Bitcoin, Ethereum and Solana.

  3. Linked wallets received roughly $7,040, mostly in Bitcoin, per Report URI.

  4. Helme's team found 188 infected scripts after examining 1,611 Optimizely files.

  5. At 21:52 UTC on November 16, one of the 188 scripts still contained malicious code.

Hackers exploited a flaw in Optimizely's Experimentation signup flow on November 16, 2026, pushing malicious JavaScript onto the websites of 178 organizations, including HSBC, Ledger, Salesforce and the BBC. The injected code swapped cryptocurrency wallet addresses across nine networks and skimmed payment-card data from visitors, according to research by security researcher Scott Helme.

Optimizely confirmed that an unauthorized party used its Experimentation account signup flow to place malicious JavaScript into customer projects. Because the entry point sat at the vendor level, attackers reached customer websites without breaching any individual server.

How many sites did the malware reach?

Helme and his team examined 1,611 Optimizely scripts and identified 188 infected files tied to 178 organizations. The list spans finance, technology and media: Zoom, GitLab, KLM, Air France, Bitly and UNICEF USA were all affected. Six of the identified entities operate in crypto or trading — Ledger, IG Group Holdings Plc, OANDA's Coinpass, Interactive Investor, TMS Brokers and Betashares — while 32 others were banks and financial companies.

Optimizely's software lets businesses test page layouts and wording, and visitors' browsers run its embedded code automatically when loading pages. That trust position made the injected scripts immediately executable on every affected domain.

What did the malicious code do?

The malware searched webpages for wallet addresses and replaced them with attacker-controlled destinations on Bitcoin, Ethereum, Solana, Tron and five other networks. It altered addresses both in form fields and in text copied to visitors' clipboards. A user who pasted a substituted address and authorized a transfer sent funds to the attacker — the method required no access to the victim's wallet and changed the destination before the transaction.

The script also captured payment-card numbers, expiration dates and security codes. Additional capabilities included harvesting browser cookies, webpage addresses and screenshots, plus delivering exploits against older iPhones and iPads. Helme attributed the secondary payloads to the Coruna and DarkSword exploit kits.

The injected JavaScript loaded a further malicious script called track.js. Some versions encoded its address; Helme found a variant with an embedded payload able to execute even if the remote script was blocked.

How did Optimizely respond?

The company said it blocked the vulnerable path, deployed a fix and removed the injected code. It also terminated active sessions, revoked tokens, reset access for affected accounts and blocked code delivery through Cloudflare, and notified all affected customers. Helme's checks showed the cleanup working: at 21:52 UTC on November 16, only one of the 188 compromised scripts still contained malicious code.

Salesforce said it was investigating the modifications and, as a precaution, verifying that Optimizely scripts were disabled across preview and production instances.

How much did the attackers take?

Wallets linked to the attack had received roughly $7,040, mostly in Bitcoin, by the evening of November 16, according to Report URI. Those receipts are not confirmed losses from this incident: Helme found some wallets had activity predating the attack.

Hudson Rock, which tracks infostealer malware, found similar code spreading through three other web services, with an earlier wave starting on November 13. Helme's earliest observed injection in the Optimizely incident occurred early on November 16.

The firms tracing the attack had not linked it to AI tools; Optimizely attributed the intrusion solely to its signup-process vulnerability. The incident lands amid heightened concern about automated vulnerability discovery — Google's threat intelligence team reported on November 16 that monthly vulnerability disclosures roughly doubled between January and July, and Anthropic recently limited access to Claude Mythos Preview over its ability to find software flaws. For the 178 affected organizations, the operational priority now is third-party script verification, since the same vendor pathway remains a standard feature of web experimentation tooling across the industry.

via en.cryptonomist.ch (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles