Optimizely Web Hijacked to Serve Malware on 178 Brands' Sites: Injected Project JavaScript Swapped Crypto Wallets, Skimmed Cards and Sent iPhones to Coruna and DarkSword

Critical · 2026-11-17 · By H.A

Optimizely Web Hijacked to Serve Malware on 178 Brands' Sites: Injected Project JavaScript Swapped Crypto Wallets, Skimmed Cards and Sent iPhones to Coruna and DarkSword

An attacker abused a flaw in Optimizely Web Experimentation to plant a crypto clipper, card skimmer and iOS exploit router in 188 customer snippets, reaching visitors of Zoom, BBC, CNN, HSBC, Equifax and 173 other organisations on 16 November.

Overview

On 16 November 2026, malicious JavaScript was served to visitors of at least 178 organisations through Optimizely Web Experimentation, the A/B testing platform that many large brands load on every page. The attacker did not compromise the websites themselves. Instead, they wrote a loader into the Project JavaScript field of customer Optimizely projects. The rest of each snippet was left untouched, so the code still came from Optimizely's own CDN, with Optimizely's domain and certificate, and every site that trusted that script ran it.

Researchers who swept the platform during the attack checked 1,611 Optimizely snippets and found 188 infected snippets belonging to 178 organisations. Named victims include Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock, and Optimizely's own sites, including its login page. Banking and finance was the most affected sector (32 organisations), followed by technology and SaaS (23) and retail (20). The researchers say the real number is probably higher, because they could only check snippets they found in time.

The payload did three things: it swapped cryptocurrency wallet addresses, skimmed payment cards typed into on-page forms, and sent iPhone visitors to known iOS exploit kits. Optimizely says an unauthorised party "exploited a vulnerability in Experimentation" to add the code. The company says it has fixed the flaw and removed the injected code, but has not said publicly what the vulnerability was.

The Campaign

The injected loader came in three variants:

Sites that self-host or proxy their Optimizely snippet were affected too, because the content still came from the same compromised project configuration. Researchers ruled out CDN cache poisoning. They could not work out how one attacker got write access to many unrelated customer projects, and that points to a flaw in the platform itself rather than stolen credentials for each customer.

The track.js payload was rebuilt 26 times during the day. Each build added features and wallets, and none were removed. Its capabilities:

Google's threat intelligence team documented both kits earlier this year. DarkSword chains six vulnerabilities in JavaScriptCore, ANGLE, dyld and the XNU kernel, and all of them are fixed by iOS 26.3. Reef Sentinel covered the same two kits earlier this month in a separate campaign that bought expired analytics domains (DeadTag). The new element here is the delivery route: a trusted first-party tag on major brand websites.

Timeline

Tradecraft

Indicators of Compromise

Detection

grep -E '1688360\.cc|5vobauua3ojpklx\.icu|eil786npto9u5bq\.icu|l7bcsnwc7nzr3uo\.icu|webshell\.lol|linkforge\.cc' /var/log/squid/access.log

Recommended Actions

Analyst Assessment

This is one of the largest client-side supply-chain incidents seen so far: one platform flaw turned a tag trusted by banks, retailers and news sites into a delivery network for theft and iOS exploits. The direct crypto loss so far is small, but the card and session exposure is not yet measured, and the iOS chains raise the impact well beyond fraud for anyone on an unpatched device. Optimizely has not said what the vulnerability was, how long it was exploitable, or whether other products were exposed. Until it does, customers should treat their own audit logs as the authority. The low share of sites whose CSP blocked the payload is the lesson for everyone else: a vendor's script runs with your site's privileges, so restrict what it is allowed to load and where it is allowed to send data.

Sources

REEF SENTINEL