Optimizely said in a November 18, 2026, update that a supply-chain attack affected fewer than 5% of its customers. The attack used its Web Experimentation service to deliver malicious JavaScript through customer websites on November 16.
Researchers traced altered scripts to 178 organizations
Report URI said it found malicious code in 188 of the 1,611 Optimizely snippets it examined. Those files belonged to 178 organizations, with its published list including the BBC, Zoom, CTV News and Starbucks Canada. The tally identifies organizations associated with altered scripts, not confirmed cases of data theft at every organization.
A signup flaw let the attacker edit customer code
In its November 17 incident report, Optimizely said the attacker exploited its account signup flow to impersonate customer administrators and edit a field called Project JavaScript. Customer passwords were neither stolen nor used, according to the company.
Project JavaScript contains custom code that runs on pages loading the Optimizely snippet. Report URI found that the rest of each snippet remained untouched.
Palo Alto Networks’ Unit 42 noted that the altered files arrived from the vendor’s legitimate content delivery network under its own security certificate. This delivery mechanism did not require a separate breach of each customer’s web servers.
Payment theft tools and iOS exploit attempts
The payload could replace cryptocurrency wallet addresses with attacker-controlled destinations and attempt to capture card numbers, expiry dates and security codes from accessible payment forms, according to Sri Lanka CERT’s November 18 advisory. The advisory cautioned that these capabilities did not establish that every visitor was infected or that every affected organization experienced data theft.
Report URI found that payment details entered inside hosted payment iframes, such as those provided by Stripe or Adyen, were outside the script’s reach. Its analysis also identified code for sending browser-readable cookies and screenshots when a wallet-address swap occurred near payment-related wording.
Netskope Threat Labs documented attempts to deliver the Coruna and DarkSword exploit kits to iPhones and iPads. However, most requests to exploit-related domains in its telemetry came from Windows and macOS browsers, where those iOS exploits could not run.
Report URI said it could not count the cards skimmed, cookies or screenshots stolen, or iOS devices infected. Optimizely’s initial report likewise said it could observe code loading, but not whether it succeeded or what data was taken.
Service repairs leave customer-specific investigations
Optimizely’s preliminary timeline says the signup flaw was fixed at 16:10 UTC on November 16 and injected code was removed from all affected projects by 22:24 UTC that day. The company engaged Mandiant for the continuing forensic investigation.
Separately, Netskope recorded requests to the main payload domain as late as 11:38 UTC on November 17, attributing them to pages still cached in browsers. A request to a malicious domain does not, by itself, establish that the payload downloaded successfully or infected a device.
Optimizely has asked Web Experimentation customers to identify affected payment pages, review transaction activity and browser-security reports, and obtain customer-specific timelines through their customer success managers. Its November 18 update said no malicious code remained in its systems and other Optimizely products were unaffected.
Unit 42 recommends auditing project changes and removing non-essential marketing and experimentation tags from authentication and checkout pages. It also recommends isolating payment collection in cross-origin iframes, separating sensitive inputs from third-party code running on the main page.

Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us







