Optimizely supply chain attack loads malware on major websites

Tampered Optimizely scripts served code to sites such as CNN, Zoom and GitLab that stole crypto and card data and delivered iOS exploit kits.

SecurityPublished
What happened
Attackers modified Optimizely-hosted JavaScript so that customer websites loaded a malicious script on 16 November.
What’s new
Researcher Scott Helme counted 188 infected files across 178 organisations, and BleepingComputer saw the code load on sites including CNN, BBC and Salesforce.
Why it matters
Visitors to trusted brand sites were exposed to crypto theft, payment card skimming and iPhone exploits through a third-party script.

A suspected supply chain attack on Optimizely, a platform companies use to run experiments and personalise their websites, caused malicious JavaScript to load on many well-known sites on 16 November, BleepingComputer reports. Optimizely's scripts are served from its content delivery network into customers' pages, so altered files reached site visitors directly.

Security researcher Scott Helme first flagged the attack. After examining 1,611 Optimizely scripts, his team found 188 infected files belonging to 178 organisations; he says attackers inserted code into Optimizely customer projects. Using urlscan.io scans, BleepingComputer confirmed the malicious script loaded, or tried to, on sites including Zoom, CNN, BBC, GitLab, KLM, Smartsheet and Salesforce. Fox News, Air France, HSBC Insurance and UNICEF USA are also on the list of affected sites.

The injected code pulled in a second script, track.js, from the domain 1688360[.]cc. According to BleepingComputer's analysis and Helme's, track.js swaps cryptocurrency wallet addresses on a page for the attackers' own, captures card numbers, expiry dates and security codes, and can collect cookies, URLs and screenshots. It also loads exploits aimed at iPhones and iPads, which Helme identified as the Coruna and DarkSword exploit kits.

Helme found the attackers' wallets took in roughly $7,000 on 16 November. He reported that by 21:52 UTC that day, cleanup had left only one of the 188 files still compromised.

How the attackers gained access remains unclear, including whether Optimizely's own infrastructure was breached or stolen credentials were used. BleepingComputer says it has asked Optimizely for comment.