Optimizely, a platform many businesses use to run A/B tests and personalise their websites, confirmed that attackers exploited a flaw in its experimentation account signup flow to inject a malicious script into customer projects on 16 November. That script, loaded automatically on every page using Optimizely's standard JavaScript snippet, was found live on at least 178 organisations' websites, including CNN, Fox News, the BBC, Salesforce, Zoom, GitLab, KLM, and American Eagle. Researcher Scott Helme identified 188 separate infected Optimizely files feeding the campaign.
The injected code did more than one thing at once. It watched for cryptocurrency wallet addresses copied to a visitor's clipboard and silently swapped them for an attacker-controlled address, attempted to skim payment card details entered on checkout pages, tried to serve iOS exploit kits to mobile visitors, and collected cookies, URLs, and screenshots from infected sessions. Researchers have so far traced roughly $7,000 in stolen cryptocurrency to the attackers' wallets, though the true scale of card and data theft is still being assessed. Optimizely has since blocked the vulnerable signup path and shipped a fix; it has not published a full list of which customer projects were affected.
What this means for your business
The unsettling part of this incident isn't Optimizely specifically — it's that none of the 178 affected organisations had to make a mistake of their own. Their own code was never touched. A single compromised script from a trusted vendor was enough to turn hundreds of unrelated websites into malware distributors overnight, entirely outside those businesses' control. If your website runs A/B testing, personalisation, analytics, live chat, or any other third-party embedded script, this is the exact failure mode to think about.
Three things worth doing this week. First, ask your developer or agency whether your site uses Optimizely, and if so, confirm the injected script is gone and the fix is in effect — a look at the page source or browser network tab for anything unexpected loading from an unfamiliar domain is a quick first check. Second, if you take online payments, review for unusual chargebacks or card complaints tied to visits around 16 November, and flag it to your payment processor if anything looks off. Third, and more broadly: ask for a plain list of every third-party script your site loads. Each one is effectively a vendor with write access to what your visitors' browsers run — fewer of them, and keeping the ones you keep audited, is what limits the damage the next time a vendor, not you, gets breached.