Optimizely Flaw Let Attacker Slip Crypto-Stealing and Card-Skimming Code onto 178 Trusted Websites
An attacker exploited a flaw in Optimizely's website testing platform to plant malicious code that reached visitors of 178 organisations, according to security researchers. Affected sites included Zoom, the BBC, CNN, Salesforce, GitLab, IKEA and Optimizely itself. Scott Helme of Report URI said his team found the code in 188 of the 1611 Optimizely snippets it checked, and warned the real number is likely higher because it could only check snippets it found in time.
Optimizely confirmed the incident in a November 17 notice, saying an unauthorised party exploited a vulnerability in its Experimentation product and added malicious JavaScript to some customer projects. The company says it has fixed the flaw, removed the injected code and taken steps to secure affected user accounts. The code was added to the Project JavaScript field, a custom-code area that runs on every page, while the rest of each snippet was left untouched. Because the files were still served from Optimizely's trusted content delivery network with its certificate, they looked legitimate.
The injected script swapped cryptocurrency wallet addresses for the attacker's own. Report URI said those wallets had received about $7,040 by 19:25 UTC on November 16 before being emptied the next day. The code also acted as a card skimmer, capturing card details typed into websites' own forms, though cards entered in hosted payment iframes were out of reach. It also stole some cookies and page screenshots.
On iPhones and iPads, the JavaScript delivered two iOS exploit kits, which Report URI identified as Coruna and DarkSword. Report URI advised visitors to update to iOS 18.7.3 or later, or iOS 26.3 or later. The first injection was seen at 04:21 UTC on November 16, and all infected files had been cleaned by 23:11 UTC. The attacker has not been named, but Report URI linked the same actor to an earlier wave of injections through other third-party scripts.
Why it matters
Any business that loads a third-party testing or marketing script on its pages is exposed, because the tampered code arrived from a trusted CDN with a valid certificate, so the usual assumption that a reputable vendor's domain means safe content failed. The skimmer could not reach hosted payment iframes, which shows that where card entry happens decides whether a script compromise becomes a card breach. It also forces a decision about who can edit custom-code fields and whether you can detect changes to vendor scripts you did not write.
What to do
- Review Project JavaScript in your Optimizely projects for code you did not add.
- Check your Optimizely accounts for unauthorised access and secure any affected user accounts.
- Move card entry into hosted payment iframes rather than your own forms.
- Update iPhones and iPads to iOS 18.7.3 or later, or iOS 26.3 or later.