# Optimizely Supply Chain Attack | How One Signup Flaw Put Malware on 178 Major Websites

- Link: https://secithub.com/optimizely-supply-chain-attack/
- Published: 2026-11-19T09:09:14+02:00
- Author: SECITHUB

Reading Time:   5 min

The Optimizely supply chain attack turned the websites of 178 well-known organizations
into malware delivery points for a single day. On November 16, 2026, an attacker
abused a flaw in Optimizely’s Web Experimentation signup flow and slipped malicious
JavaScript into customer projects. Visitors to sites run by Zoom, the BBC, CNN, 
Salesforce, GitLab, IKEA, HSBC and Equifax loaded the code without clicking anything.

None of these companies lost control of their own servers. The code arrived through
a trusted marketing tool that their pages load on every visit. That is what makes
this incident so important. It shows how one vendor can quietly become an attack
path into hundreds of websites at once.

Table of Contents

 [Toggle](https://secithub.com/optimizely-supply-chain-attack/#)

 * [What Happened in the Optimizely Supply Chain Attack](https://secithub.com/optimizely-supply-chain-attack/#What_Happened_in_the_Optimizely_Supply_Chain_Attack)
    - [A Researcher Spots Bad Code on Big Brands](https://secithub.com/optimizely-supply-chain-attack/#A_Researcher_Spots_Bad_Code_on_Big_Brands)
    - [About 16 Hours of Exposure](https://secithub.com/optimizely-supply-chain-attack/#About_16_Hours_of_Exposure)
    - [Optimizely Confirms a Signup Flaw](https://secithub.com/optimizely-supply-chain-attack/#Optimizely_Confirms_a_Signup_Flaw)
    - [The Vendor's View of the Damage](https://secithub.com/optimizely-supply-chain-attack/#The_Vendors_View_of_the_Damage)
 * [How the Malicious Code Worked](https://secithub.com/optimizely-supply-chain-attack/#How_the_Malicious_Code_Worked)
    - [Hiding Inside "Project JavaScript"](https://secithub.com/optimizely-supply-chain-attack/#Hiding_Inside_%22Project_JavaScript%22)
    - [A Crypto Address Swapper](https://secithub.com/optimizely-supply-chain-attack/#A_Crypto_Address_Swapper)
    - [Card Skimming and Screenshots](https://secithub.com/optimizely-supply-chain-attack/#Card_Skimming_and_Screenshots)
    - [A Second Stage for iPhones](https://secithub.com/optimizely-supply-chain-attack/#A_Second_Stage_for_iPhones)
 * [How Much Did the Attackers Get?](https://secithub.com/optimizely-supply-chain-attack/#How_Much_Did_the_Attackers_Get)
 * [Why Third-Party Scripts Are Your Blind Spot](https://secithub.com/optimizely-supply-chain-attack/#Why_Third-Party_Scripts_Are_Your_Blind_Spot)
    - [Your Page, Someone Else's Code](https://secithub.com/optimizely-supply-chain-attack/#Your_Page_Someone_Elses_Code)
    - [Classic Defenses Struggle Here](https://secithub.com/optimizely-supply-chain-attack/#Classic_Defenses_Struggle_Here)
    - [The Same Story Across the Supply Chain](https://secithub.com/optimizely-supply-chain-attack/#The_Same_Story_Across_the_Supply_Chain)
 * [What to Do Now](https://secithub.com/optimizely-supply-chain-attack/#What_to_Do_Now)
    - [1. Audit Every Optimizely Project](https://secithub.com/optimizely-supply-chain-attack/#1_Audit_Every_Optimizely_Project)
    - [2. Search Your Logs and Telemetry](https://secithub.com/optimizely-supply-chain-attack/#2_Search_Your_Logs_and_Telemetry)
    - [3. Lock Down Third-Party Scripts](https://secithub.com/optimizely-supply-chain-attack/#3_Lock_Down_Third-Party_Scripts)
    - [4. Keep Checkout Pages Clean](https://secithub.com/optimizely-supply-chain-attack/#4_Keep_Checkout_Pages_Clean)
    - [5. Advice for Visitors](https://secithub.com/optimizely-supply-chain-attack/#5_Advice_for_Visitors)
 * [The Real Lesson](https://secithub.com/optimizely-supply-chain-attack/#The_Real_Lesson)
    - [Sources](https://secithub.com/optimizely-supply-chain-attack/#Sources)

## **What Happened in the Optimizely Supply Chain Attack**

### **A Researcher Spots Bad Code on Big Brands**

Scott Helme of Report URI raised the alarm. His team checked 1,611 Optimizely snippets
and found the injected code in 188 of them, tied to 178 organizations. Banking and
finance, technology and retail made up the largest groups.

### **About 16 Hours of Exposure**

According to Helme’s timeline, a BBC snippet began loading the attacker’s code at
04:21 UTC. The attacker kept improving the payload during the day and added a card
skimmer in the afternoon. Optimizely ran a mass cleanup in the evening, and Helme
reported every file clean by 23:11 UTC.

### **Optimizely Confirms a Signup Flaw**

Optimizely says an unauthorized party exploited a flaw in its Web Experimentation
account signup flow. The attacker used it to impersonate users on targeted accounts
and add JavaScript to their projects. The company says it closed the hole within
three hours of detection and removed the code from every affected project.

### **The Vendor’s View of the Damage**

Optimizely says fewer than 5% of its customers were affected and stresses that this
was not a credentials breach. It revoked sessions and tokens, reset access for affected
accounts and contacted customers directly. It has not published technical details
of the flaw itself.

    ```wp-block-verse
    The attacker never touched Zoom or the BBC. They only needed the tool both of them trusted.
    ```

## **How the Malicious Code Worked**

### **Hiding Inside “Project JavaScript”**

Every Optimizely Web customer loads a snippet from the Optimizely CDN. It holds 
the vendor’s code, the customer’s A/B tests and an optional custom field called 
Project JavaScript. The attacker wrote a small loader into that field. The CDN then
served it to visitors with Optimizely’s own trusted certificate.

### **A Crypto Address Swapper**

The main payload watched pages, forms and the clipboard for cryptocurrency wallet
addresses. When it found one near payment wording, it replaced it with an attacker
wallet. A visitor could copy a correct address and paste the attacker’s one without
noticing.

### **Card Skimming and Screenshots**

Later versions also checked form submissions and web requests for card numbers and
sent valid ones to the attacker. After a wallet swap, the script captured a screenshot
of the page and grabbed readable cookies. It could not read HttpOnly cookies or 
card fields inside a payment provider’s separate iframe.

### **A Second Stage for iPhones**

On iPhone and iPad visitors, the script loaded more code that delivered known iOS
exploit kits. Helme links them to the kits known as Coruna and DarkSword, which 
target older iOS versions. Public scans show the exploit pages reached devices. 
They do not prove that any phone was actually compromised.

## **How Much Did the Attackers Get?**

The on-chain numbers are small for an attack of this reach. Helme estimates that
attacker wallets received about $7,040, swept out within hours. Galaxy Digital puts
direct victim payments closer to $2,300. Some wallets were active before the attack,
so the exact figure is uncertain.

Card data and cookies leave no public trace, so the full cost is unknown. The risk
to iPhone users on old software is also hard to measure. The low crypto total should
not reassure anyone. The access was the real prize, and the next attacker may use
it more patiently.

Threat intelligence firm Hudson Rock adds a worrying detail. It says it traced the
same malicious code to three other web services: Kissmetrics, StorifyMe and minute-
ly. If confirmed, this was a campaign against web vendors, not a one-off.

    ```wp-block-verse
    A small payout today does not mean a small risk tomorrow.
    ```

## **Why Third-Party Scripts Are Your Blind Spot**

### **Your Page, Someone Else’s Code**

A typical corporate site loads tags for analytics, testing, chat, ads and consent.
Each one runs with the same power as your own code. Marketing teams often add them
without a security review, and nobody watches what they load next.

### **Classic Defenses Struggle Here**

Subresource Integrity hashes do not fit a snippet that changes every time a test
is published. Serving the snippet from your own domain did not help either, because
the content still came from the hijacked project. A Content Security Policy with
host allowlists for scripts and outbound connections could have blocked the download
and the data theft.

### **The Same Story Across the Supply Chain**

This week has shown the pattern again and again. The **_[Microsoft agent-framework PyPI compromise](https://secithub.com/microsoft-agent-framework-pypi-compromise/)_**
hit developers through a trusted package. The **_[Puppet CVE-2026-115731 flaw](https://secithub.com/puppet-cve-2026-115731/)_**
showed how one management server can reach a whole fleet. Attackers want the tool
that touches everyone.

## **What to Do Now**

### **1. Audit Every Optimizely Project**

Read the Project JavaScript field in each Optimizely Web project, including snippets
you serve from your own domain. Remove users and API tokens you do not recognize.
Ask Optimizely which of your projects changed on November 16.

### **2. Search Your Logs and Telemetry**

Block the published payload domains in DNS and proxy controls. Search logs back 
to early November 16 for requests to them. Check CSP reports and browser telemetry
for failed calls to unknown hosts.

### **3. Lock Down Third-Party Scripts**

Keep a live inventory of every script on your site and who owns it. Enforce a Content
Security Policy that limits where scripts load from and where data can go. Review
vendor admin access with the same care as your own admin accounts.

### **4. Keep Checkout Pages Clean**

Remove marketing and testing tags from payment pages wherever possible. Use payment
fields hosted by your provider inside a separate iframe. In this attack, that design
kept card fields out of the skimmer’s reach.

### **5. Advice for Visitors**

If you entered card details on an affected site on November 16, watch your statements
and consider a new card. Confirm that any crypto you sent reached the right wallet.
Update iPhones and iPads to the latest iOS.

## **The Real Lesson**

The Optimizely supply chain attack is a reminder that your attack surface includes
every vendor whose code runs on your pages. You can outsource a feature, but you
cannot outsource the risk that comes with it.

Most of the 178 organizations did nothing wrong in the usual sense. They used a 
popular tool exactly as intended. That is why third-party script governance needs
a place in every security program, next to patching and identity.

Want to see how the same trust problem plays out in software packages? Read our 
analysis of **_[how a 55-minute PyPI release stole cloud secrets](https://secithub.com/microsoft-agent-framework-pypi-compromise/)_**.

    ```wp-block-verse
    Know every script on your site before an attacker writes one for you.
    ```

![SECITHUB FAQ banner for the Optimizely supply chain attack](https://secithub.com/
wp-content/uploads/2025/12/SECITHUB-FAQ-1.jpg)

**What was the Optimizely supply chain attack?**

On November 16, 2026, an attacker exploited a flaw in Optimizely’s Web Experimentation
signup flow and added malicious JavaScript to customer projects. The code ran on
websites of 178 organizations for up to about 16 hours.

**Which websites were affected?**

Researchers named Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC and Equifax
among the 178 organizations. The companies’ own servers were not breached; the code
came through Optimizely.

**What did the malicious code do?**

It swapped cryptocurrency wallet addresses, skimmed card numbers from forms, captured
screenshots and readable cookies, and sent iPhone and iPad visitors to iOS exploit
kits.

**Has Optimizely fixed the problem?**

Optimizely says it closed the vulnerability within three hours of detection, removed
the injected code, revoked sessions and tokens, and contacted affected customers.
It says fewer than 5% of customers were affected.

**What should visitors do?**

If you entered card details on an affected site on November 16, monitor your statements
and consider replacing the card. Check any crypto transfers and update iPhones and
iPads to the latest iOS.

**How can companies prevent similar attacks?**

Inventory all third-party scripts, enforce a Content Security Policy that limits
script sources and outbound connections, review vendor account access and keep marketing
tags off payment pages.

### **Sources**

 * _[Report URI: The World’s Largest Brands Infected With Malware via Optimizely](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/)_
 * _[CMSWire: Optimizely Says Signup Flaw Let Attacker Plant Malicious Code in Customer Projects](https://www.cmswire.com/digital-experience/optimizely-works-through-web-experimentation-security-incident/)_
 * _[StepSecurity: OPTIMJACK technical analysis](https://www.stepsecurity.io/blog/optimjack-optimizely-hosted-scripts-crypto-clipper-card-skimmer)_
