
A supply-chain attack on software company Optimizely turned some of the world's most trusted websites into malware traps on Monday, November 16, 2026, infecting the sites of 178 organisations — including CNN, BBC, Fox News, Zoom and Salesforce — with code designed to steal cryptocurrency and payment-card details. The Optimizely supply-chain hack was uncovered by security researcher Scott Helme, and it reached visitors through a script the sites themselves trusted.
The attack worked because of trust, not because the victims' own systems failed. None of the affected organisations' servers was breached. Instead, attackers slipped malicious JavaScript into Optimizely's experimentation platform, and the poisoned code rode along with a script millions of sites load every day.
Helme and his team at Report URI spotted the campaign on Monday and traced it to Optimizely's platform. The earliest observed injection came in the early morning of November 16, although it is not clear how long the vulnerability had been present, or how many visitors were exposed before it was found.
The attackers kept updating their payload all day. The track.js file, about 30 KB in size, was rebuilt 26 times — a sign the operators were actively adapting it to stay ahead of security tools. The injected code fetched a second-stage script from 1688360.cc/track.js, sometimes directly and sometimes hidden with Base64 encoding. One variation carried an embedded copy that could run even if the remote script was blocked.
Once loaded, the payload watched webpages for cryptocurrency wallet addresses and replaced them with attacker-controlled addresses, so transfers went to the criminals. It also searched for credit-card numbers, expiry dates and security codes, and collected browser cookies, webpage addresses and screenshots. The wallets embedded in track.js had received about $7,040 by 19:25 UTC, though some were active before the attack, so the true theft is unclear.
Optimizely is a digital experience and experimentation platform that companies use to test and personalise their websites. Its JavaScript files are loaded into customers' webpages to deliver that functionality — running experiments and measuring what works. That is why a single flaw spread so far: one vendor's code sits inside hundreds of customer sites.
The criminals did not need to break into CNN, the BBC or Zoom. They only needed one weak link in a shared supplier, and the trusted script did the rest. The code arrived through cdn.optimizely.com, a host the sites deliberately trusted, so browsers and security tools treated it as legitimate. Read our earlier report on hackers hijacking GitHub accounts to spread a credential stealer.
Three things made this attack unusually dangerous: scale, speed and breadth. A single flaw reached 178 household-name organisations. The payload was rebuilt 26 times in one day, showing operators who were watching defences and adapting. And a single 30 KB file combined crypto theft, card skimming, cookie theft and iOS exploits. The Coruna and DarkSword kits target different versions of iOS, so anyone on an older iPhone or iPad who visited an affected site on Monday should update to the latest iOS or iPadOS. There is also an irony in the victim list: Ledger, a maker of cryptocurrency hardware wallets, was among the affected sites.
Optimizely confirmed the incident to BleepingComputer on Monday. "Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in the Experimentation account signup flow," the company said. "We have blocked access to the vulnerable path and deployed a fix. We have removed the injected code from affected projects. We have also ended active sessions, revoked tokens, and reset access for affected user accounts."
The company added that it had blocked the code from being delivered through Cloudflare and that it has notified all affected customers. Salesforce confirmed it is investigating and said it is confirming Optimizely scripts are disabled across preview and production. Helme's tracking showed the cleanup working: by 21:52 UTC only one of the 188 infected files still contained malicious code.
The modern web runs on trust. A typical news page loads dozens of third-party scripts — analytics, advertising, testing tools, chat widgets — and each one is a door into the visitor's browser. When one vendor is compromised, hundreds of sites inherit the breach overnight, and visitors have no way to tell a trusted script from a poisoned one. The $7,040 seen in the attackers' wallets is almost certainly a floor, not a total, and card numbers stolen on Monday may surface as fraud weeks from now. Read our report on the bank outage that locked out Chase, Bank of America and Wells Fargo customers.
Optimizely says it is continuing to investigate and will publish updates at status.optimizely.com. Expect hard questions about how a flaw in a signup flow went unnoticed, and about how customers audit the third-party code on their pages. For visitors, the advice is practical: check any cryptocurrency transfers made on November 16, watch card statements for unauthorised transactions, and update iPhones and iPads. Read our report on the FBI warning about the ARTEX hacking tool.
Attackers exploited a flaw in Optimizely's Experimentation account signup flow on November 16, 2026, injecting malicious JavaScript into customer projects. Visitors to 178 organisations' websites were then served malware from cdn.optimizely.com.
CNN, BBC, Fox News, Zoom, Salesforce, GitLab, HSBC, Equifax, Ledger, IKEA, Air France-KLM and Peacock, as well as American Eagle, Change.org, Bitly and UNICEF USA. None of the organisations' own servers was breached.
The code ran in the browser: it could swap wallet addresses, skim card details, steal cookies and screenshots, and route iPhones and iPads to exploit kits. Check crypto transfers from that day, monitor card statements and update iOS or iPadOS.
Wallets in the malicious script had received about $7,040 by 19:25 UTC on November 16, but some were active before the attack, so the exact amount stolen is unclear.
Optimizely fixed the flaw and removed the code. By 21:52 UTC on November 16 only one infected snippet — TalkTalk's — still carried it. The company says it is continuing to investigate.