YuSMP Group logo
YuSMP Group Editorial Team Editorial team, YuSMP Group
Glass tubes carrying glowing code blocks into a row of night storefronts, with one tube near the source tinted red and leaking red particles into every window downstream

The short version

A flaw in Optimizely’s account signup let an attacker edit customer experiment snippets, and those snippets shipped malware to 178 brands’ visitors for most of a day. No site owner deployed anything. Teams that do web application development should treat marketing and testing tags as part of the release pipeline, with the same access rules, monitoring and blast-radius limits as their own code.

What happened to Optimizely’s customers?

On November 16, an attacker inserted extra code into 188 Optimizely Web Experimentation project snippets, and every site loading those snippets served the code to its visitors.

Optimizely Web Experimentation works through a JavaScript snippet that each customer embeds on its pages. The snippet is generated per project and served from Optimizely’s CDN, so when a project changes, every page that loads it picks up the change on the next visit.

Security researcher Scott Helme of Report URI spotted the change in his company’s crawl data, and BleepingComputer independently confirmed it from urlscan.io records after reviewing 1,611 Optimizely scripts.

The affected organisations named in the reports include:

  • Zoom, Salesforce, GitLab and Smartsheet in tech and SaaS
  • the BBC, CNN and Fox News in media
  • HSBC Insurance, Air France and KLM in finance and travel

What did the malicious script do?

The injected code loaded a second script, track.js, from the domain 1688360[.]cc. According to Report URI’s analysis, that script had four jobs:

  1. It watched pages for wallet addresses and replaced them with ones the attacker controlled.
  2. It looked for card numbers, expiry dates and security codes, validated numbers with a Luhn check and sent them out.
  3. It grabbed cookies, URLs and page screenshots.
  4. It loaded exploit kits known as Coruna and DarkSword for visitors on iOS devices.

Direct losses tracked so far are small: about $7,040 in cryptocurrency within roughly nine hours. Card data and cookies are harder to count, which is why Report URI advises treating payments made on affected sites on November 16 as potentially compromised.

How did the attackers get in?

Optimizely says the entry point was on its side. A spokesperson told Gizmodo that an unauthorized party “exploited a vulnerability in the Experimentation account signup flow” and added malicious JavaScript to some customer projects. The company says it blocked access to the vulnerable path, deployed a fix and notified all affected customers.

That detail matters for defenders. None of the 178 organisations changed their own code, and none of their deploy pipelines would have flagged anything. The trust boundary that failed sat inside a vendor console they did not run.

What it means for US & EU software teams

Experimentation, analytics and personalisation tags are designed to change without a release. That is their value to marketing teams, and it is exactly what made this attack possible.

Subresource Integrity, the usual way to pin a third-party file to a known hash, does not fit a snippet that is supposed to change whenever someone edits an experiment.

Which controls work around a changing tag?

The controls have to sit around the tag rather than on it:

  • Restrict outbound calls. A connect-src allowlist in your Content Security Policy limits where page scripts can send data, so a skimmer cannot quietly post to an unknown domain. Report URI recommends exactly this restriction after the attack.
  • Keep checkout clean. Payment and account pages rarely need A/B testing scripts. Removing them shrinks the blast radius of the next tag compromise.
  • Watch for script changes. In this case an outside researcher’s crawler found the change, not the affected companies. Monitoring that alerts when a third-party script’s content or outbound destinations change puts that signal in your own hands.
  • Own the vendor accounts. Use SSO, remove stale users and rotate API tokens for every tag platform, as you would for a CI system.

Does PCI DSS cover third-party scripts?

For merchants this is also a compliance question. PCI DSS v4.0 requirements 6.4.3 and 11.6.1, mandatory since March 31, 2025, require an inventory of authorized scripts on payment pages and a way to detect unauthorized changes to them. Teams building PCI DSS-compliant software should check whether their current controls would have caught a vendor-side edit like this one.

What should web teams do this week?

  1. Confirm exposure. If you use Optimizely Web Experimentation, check for Optimizely’s notice and review your project history for changes on November 16.
  2. Rotate exposed sessions. Report URI recommends rotating cookies that are readable by JavaScript, meaning those without the HttpOnly flag.
  3. Review account access. Audit users and API tokens on Optimizely and other tag platforms.
  4. Inventory your tags. List every third-party script per page template and remove the ones checkout and login do not need.
  5. Tighten CSP. Add or narrow connect-src and avoid 'unsafe-eval' where your stack allows it.

Frequently asked questions

What happened in the Optimizely supply chain attack?

On November 16, 2026, an attacker added malicious JavaScript to Optimizely Web Experimentation projects. Because sites load those project snippets from Optimizely’s CDN, the code ran for visitors of 178 organisations, including Zoom, the BBC, CNN, Salesforce and GitLab, according to Report URI and BleepingComputer.

How did the attackers get into Optimizely?

Optimizely told Gizmodo that an unauthorized party exploited a vulnerability in the Experimentation account signup flow and added malicious JavaScript to some customer projects. The company says it blocked the vulnerable path, deployed a fix and notified affected customers.

What did the malicious JavaScript do?

Researchers found a script loaded from the domain 1688360[.]cc that swapped cryptocurrency wallet addresses, captured payment card data with a Luhn check, collected cookies and screenshots, and loaded exploit kits aimed at iPhones and iPads. About $7,040 in cryptocurrency was stolen in roughly nine hours.

Would a Content Security Policy have stopped it?

Partly. The first-stage code arrived inside a script that sites already allowed, so CSP could not stop it from running. A script-src limited to specific hosts would block the second-stage track.js from the attacker’s domain, and a strict connect-src allowlist would block data being sent there, which is why Report URI recommends restricting both.

Do PCI DSS rules cover third-party scripts like this?

Yes. PCI DSS v4.0 requirement 6.4.3 asks merchants to inventory, authorize and check the integrity of every script on payment pages, and requirement 11.6.1 asks for a mechanism that detects unauthorized changes to those pages. Both have been mandatory since March 31, 2025.

Sources

Report URI (Scott Helme): World’s Largest Brands Infected With Malware Via Optimizely (primary research, November 16, 2026)
BleepingComputer: Optimizely supply chain attack infects major brands’ sites with malware (November 16, 2026)
Gizmodo: Sprawling Malware Attack Reportedly Affects Zoom and Other Major Brands, with Optimizely’s statement (November 16, 2026)