Visitors to CNN, the BBC, Zoom and Salesforce on Monday, November 16, may have been served code their browsers should never have run. The Optimizely supply chain attack abused a trusted A/B testing tool to inject malicious JavaScript into sites run by 178 organizations, and the payload reached their visitors within a single day.
Optimizely Web Experimentation runs on roughly 190,000 live websites, according to BuiltWith. Customers load it through a JavaScript snippet from Optimizely's own content delivery network, so one tampered file can reach the visitors of every customer that loads it. This is a classic supply chain attack, where criminals compromise one trusted vendor to reach all of its customers at once.
Scott Helme of Report URI flagged the code on Monday. Optimizely confirmed the incident on Tuesday, November 17, and appointed Mandiant, a Google subsidiary, to investigate.
How the Optimizely supply chain attack got in
Optimizely says an unauthorized party exploited a flaw in the account signup flow of its Experimentation product. The attacker then used that access to add malicious code to some customer projects on November 16. The company has not publicly named the attacker.
The malicious code sat in the optional Project JavaScript field. That customer-editable area runs on every page of a site, so one edit spreads quickly. Because Optimizely's own CDN served the tampered files, no customer's servers had to be breached.
Optimizely's interim timeline puts the first malicious code at 02:51 and its detection at 08:34 on November 16. The source does not state a time zone, so those times should be read exactly as Optimizely reported them.
The campaign may have started earlier. Netskope reported that the broader malware effort may have begun as early as September, targeting sites through other third-party software providers before the Optimizely attack. The sources reviewed do not establish whether those September events connect to the November 16 campaign.
Which brands and sites were hit
Reporting names Air France-KLM, BBC, CNN, Equifax, GitLab, HSBC, IKEA, Peacock, Salesforce and Zoom among the affected brands. BleepingComputer reported infections on CNN, Fox News, BBC and Salesforce sites, and Malwarebytes listed Zoom among the sites serving the code. Newsweek published a full list of the 178 organizations.
Salesforce said it was investigating unauthorized changes to Optimizely scripts on some of its sites. The company disabled the third-party scripts as a precaution.
Two headline numbers are easy to mix up. Report URI examined 1,611 Optimizely scripts and found malicious code in 188 of them, as Shattered.io reported. The 178 figure counts organizations, while the 188 figure counts script snippets, so the two should not be treated as interchangeable.
What the malware did to payments and crypto
The injected code swapped cryptocurrency wallet addresses for the attacker's own. Report URI said about $7,040 reached the attacker's wallets before they were emptied the next day. The sum is modest, but it shows the code redirected real transactions instead of only collecting data.
The code also carried card-skimming and data-theft functions. Nobody has established how many consumers had payment card data stolen, and Optimizely has not published a figure.
Helme estimated the malicious code may have been served during roughly 34 million page visits, with a range of 6 million to 150 million, according to Newsweek. The range is an estimate, not a measured count, and it is wide enough to make sizing your own exposure difficult.
Defenses varied widely. Only 24 affected sites had content security policies that fully blocked the payload. A content security policy is a browser rule that limits which scripts can run on a page, so a strict one can stop a tampered script even when a vendor's file is compromised.
Helme's team tested the defenses of affected sites, and his conclusion was blunt. "The important lesson here is that trusted JavaScript doesn't always remain trustworthy," he wrote in his blog post, as KrebsOnSecurity quoted it. In an interview with Krebs, he added: "Organizations are running all this code, but they don't know what it's doing."
Which iPhones and iPads need an update now
The malware did not stop at web payments. On iPhones and iPads, it delivered two iOS exploit kits, which Report URI named Coruna and DarkSword. Report URI advised visitors to move to iOS 18.7.3 or later, or to iOS 26.3 or later.
To check your version, open Settings, tap General, then Software Update, and install the newest release offered for your device. Reporting does not break down which models stay exposed on older builds, so the version number is the test to rely on.
What to do if you visited an affected site
If you browsed one of the affected sites on November 16, work through these steps:
- Review card and bank statements for November 16 charges you do not recognize, and contact your card issuer if anything looks wrong.
- If you hold cryptocurrency, check wallet and exchange activity from that day for transfers you did not authorize.
- Update iPhones and iPads to iOS 18.7.3 or later, or iOS 26.3 or later.
Business owners should go further. Review the Project JavaScript field and any experiment custom code in every Optimizely project in the dashboard, rather than only the file your site serves. Site owners should tighten content security policies and monitor third-party scripts, which remain the main defense against this type of attack.
What remains unknown and what to watch next
Optimizely says it fixed the vulnerability, removed the injected code, secured affected accounts and added protections. "We've fixed the vulnerability and removed the injected code from affected projects," the company said in a statement. Report URI later confirmed the infected files had been cleaned, and the attacker's main payload domain has since been suspended.
Several questions remain open. Mandiant's investigation is ongoing, and Optimizely says a final root-cause analysis will follow it. The company has not said how many customer projects were affected beyond the 178 organizations.
Researchers also traced a wider pattern. Hudson Rock, working with a researcher, reported poisoned scripts served through Optimizely, Kissmetrics, StorifyMe and minute-ly, with archived activity recorded on November 13. That finding rests on one research firm and has not been independently confirmed in the reporting reviewed here.
Third-party exposure keeps producing these headlines. USA 24 recently reported how JPMorgan, Visa and Mastercard customer data leaked through vendors, showing how a breach at one supplier can reach many companies at once.
The next milestones are Mandiant's findings and Optimizely's root-cause analysis. Those should show whether the signup flaw was the only entry point and how many projects were touched. Watch for brands publishing their own checks, and for Helme's team to refine the visit estimate once the cleanup is verified.




