An attacker exploited a vulnerability in Optimizely Web Experimentation, a service websites use to run experiments such as A/B tests, and added malicious JavaScript to some customer projects. Optimizely disclosed the incident on its official status page on November 17 (JST). Report URI, a security company that sells website script-monitoring services, detected the injected code with its own scanning and published its own research report. By its count, sites belonging to 178 organizations received code that swapped visitors' cryptocurrency destination addresses and stole payment card details.

Optimizely Says It Fixed the Flaw and Removed the Injected Code

Optimizely posted an update on its official status page under "Web Experimentation Security Incident" at 10:02 a.m. JST on November 17 (01:02 UTC). The company says "an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects." The affected component is the delivery of the snippet that sites load (Snippet Delivery).

In response, Optimizely says it fixed the vulnerability and removed the injected code from affected projects. It also says it took steps to secure affected user accounts and put additional protections in place to prevent unauthorized code from being delivered. Optimizely itself has not yet described the vulnerability or given a number of affected customers. The figures below come from Report URI's own investigation, not from Optimizely.

Report URI's Scan: Malicious Code in 188 of 1,611 Snippets

Report URI published its findings on November 16 on the company's own blog, in a research report written by its founder, Scott Helme. It is the company's first-hand account of its own investigation, not a news article. The company examined 1,611 Optimizely Web snippets, gathered largely from its own crawl data, and found malicious code in 188 of them. Because some organizations use more than one snippet, those 188 snippets belonged to 178 organizations. Report URI says the real number is likely higher.

Organizations it named include Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. Optimizely's own sites were also on the list.

In Report URI's analysis, the attacker altered the "Project JavaScript" section that each customer configures for its project, leaving the rest of the snippet untouched. The injected code loads an additional script from an external domain. Report URI says Optimizely's CDN simply served what it was given, and that this was not a cache-poisoning attack. The first injection Report URI observed was at 1:21 p.m. JST on November 16 (04:21 UTC).

Crypto, Payment Cards and iPhones Were Targeted

Report URI's researchers analyzed the loaded script themselves and list the following capabilities in their report:

  • Crypto address swapping: replaces BTC, ETH, TRON, Solana and other addresses in page text, forms, the clipboard and outgoing requests with the attacker's own
  • Card skimming: sends card numbers, expiration dates and security codes entered in forms to an external server. This capability was added partway through. Embedded payment frames from providers such as Stripe and Adyen were out of reach
  • Sending cookies and screenshots of the page
  • iOS attacks: on iPhone and iPad, loads exploit kits that Report URI identifies as Coruna and DarkSword, depending on the iOS version

Report URI also traced the attacker's wallets listed in the script and says that, as of 19:25 UTC on November 16, they had received about $7,040 in total. It says it cannot see how much card or cookie data was sent.

Most of the Malicious Code Was Removed Before Optimizely's Notice

Report URI's repeated scans found that as of 6:52 a.m. JST on November 17 (21:52 UTC on November 16), only 1 of the 188 infected snippets still contained the malicious code. In other words, cleanup on most sites was largely done by early morning on November 17 in Japan, a few hours before Optimizely posted its status update at 10:02 a.m. JST.

Report URI advises site owners to check every project's Project JavaScript and experiment code for unfamiliar scripts, review users and API tokens, and rotate credentials. It urges visitors who used an affected site on November 16 (UTC) to update their iPhone or iPad to iOS 18.7.3 or later, or iOS 26.3 or later, and to check their crypto transfer history and card statements.

Our Take: The Attack Came From a Place Site Owners Never Touched

Many websites load third-party scripts for analytics, experiments and advertising. In this case, site owners changed none of their own code, yet settings on the service they use were rewritten and malicious code reached their visitors. In our view, this is a clear example of how fragile a setup that depends on external scripts can be.

What stands out is that no one has yet explained how the attacker was able to write to so many unrelated customer projects. Report URI also says it does not know how that access was obtained. Restricting allowed destinations with a Content Security Policy (CSP) is one way to limit this kind of damage. Whether a detailed explanation of the root cause emerges is the next thing to watch.

Summary

According to Optimizely's status page, an attacker exploited a vulnerability in Optimizely Web Experimentation and added malicious JavaScript to some customer projects, and the company has fixed the flaw and removed the code. Report URI's own research found that sites of 178 organizations were affected, with code that swapped crypto addresses, skimmed payment cards and attacked iOS devices. Anyone who used an affected site on November 16 should update iOS and check their transfer history and card statements.