Pull to refresh
Logo
Optimizely signup flaw let attackers inject skimmers into major brand sites

Optimizely signup flaw let attackers inject skimmers into major brand sites

Force in Play

A flaw in Optimizely's account signup flow let an outsider write JavaScript into customer projects, exposing visitors to CNN, the BBC, Zoom and Salesforce to card skimming and crypto theft

Overview

Updated 8 hours ago

On 16 November 2026, visitors to CNN, the BBC, Zoom and Salesforce loaded a JavaScript file that came from Optimizely, the experimentation vendor those sites embed. For roughly 16 hours, that file also copied card numbers out of payment forms and swapped cryptocurrency wallet addresses as people pasted them.

The route in was not a stolen password or a poisoned content delivery network. A flaw in Optimizely's account signup flow let outsiders act as administrators on customer projects, where a field meant for experiments accepts arbitrary code. Optimizely closed the flaw at 16:10 UTC and had removed the injected code by 22:24 UTC.

Why it matters

Hundreds of brands outsourced a piece of their page to one vendor. The flaw showed a signup form, not the CDN, was the weak link.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

178
Organizations with infected Optimizely files
Scott Helme's count after reviewing 1,611 scripts used across the platform.
188
Infected JavaScript files
Those files were spread across the 178 organizations.
~16
Hours most sites served the loader
From the first injection to the evening cleanup on 16 November.
$7,000
Crypto stolen in the campaign
Mostly bitcoin, with the rest split across litecoin, USDT and ether, per Helme.
0
Customer passwords exposed, per Optimizely
The attacker acted as administrators without using anyone's credentials.

Voices

Curated perspectives — historical figures and your fellow readers.

Sign up to generate historical perspectives on this story.

People Involved

Organizations Involved

Timeline

9 events Latest: Yesterday
Tap a bar to jump to that date
  1. Attacker command-and-control goes offline

    Latest Attack

    Netskope records the infrastructure dropping off after the cleanup.

  2. Optimizely publishes its incident report

    Statement

    The report rules out a credentials breach and says the injected script targeted payment and crypto data only.

  3. Attacker accounts created through the signup flow

    Attack

    Optimizely links the registrations to commercial VPN addresses, including ExpressVPN.

  4. First malicious code written into customer projects

    Attack

    Optimizely dates the first injected Project JavaScript to this time; Helme saw a BBC snippet loading attacker code earlier that morning.

  5. Optimizely detects the activity

    Detection

    The company begins incident response on the same day the injections started.

  6. Signup flaw closed

    Remediation

    The vulnerable path is blocked and a fix deployed.

  7. Injected code removed from every affected project

    Remediation

    Optimizely also ends sessions, revokes tokens and resets access for affected accounts.

  8. Last infected file cleaned, per Helme

    Remediation

    One snippet, reported to be TalkTalk's, was still infected at 21:52 UTC.

  9. Same infrastructure used against other sites

    Background

    Researchers at Netskope trace an earlier skimming attempt using webshell[.]lol and other third-party scripts, including Kissmetrics and StorifyMe.

Scenarios

1

Mandiant names the actor behind the Optimizely injections

Possible Resolves by May 31, 2027

Discussed by: Optimizely's incident report and StepSecurity, both of which note attribution is pending while tying the infrastructure to earlier skimming campaigns

The report says the actor controls pay-cloud[.]online and has run two command-and-control frameworks from it since at least September 2026, and that the same infrastructure hosted skimmers used against other victims. A final forensic report could attach a name or a malware family to that infrastructure. If it does not, the campaign stays an unattributed string of domains.

2

A privacy regulator opens a formal inquiry into Optimizely

Possible Resolves by May 31, 2027

Discussed by: Dark Reading's coverage, which notes Optimizely did not explain how a signup flaw crossed customer boundaries

The injected code ran in visitors' browsers across the European Union and the United Kingdom, which puts the incident inside the scope of the UK Information Commissioner's Office and EU data protection authorities. A regulator could open a formal inquiry into whether Optimizely's access controls were adequate. No regulator has announced one.

3

Affected brands file breach notifications covering payment card data

Possible Resolves by Feb 28, 2027

Discussed by: StepSecurity's analysis of the skimmer's card-capture code, which logged card numbers passing Luhn checks and sent them to a remote endpoint

The script watched form submissions for card numbers with valid brand prefixes, expiry dates and security codes, then beaconed them to a server-side handler. Optimizely says cards entered in hosted payment iframes were out of reach, so the exposure is limited to sites that collected card details in their own forms. Whether any of those sites notify regulators and customers is the test of how much card data left.

4

A customer sues Optimizely over the injection

Uncertain Resolves by Nov 30, 2027

Discussed by: No plaintiff has filed; the question follows from Optimizely's statement that it has confirmed affected customers individually

Optimizely told each customer whether it was affected, which establishes a list of potential plaintiffs. A lawsuit would turn on whether the signup flaw counted as a failure of the access controls Optimizely promised, and on whether the customer or the vendor bore responsibility for the Project JavaScript field. Filing deadlines for contract claims typically run for years, so a suit could arrive long after the technical story goes quiet.

Historical Context

3 moments from history that rhyme with this story — and how they unfolded.

August-September 2018

British Airways payment-page skimming (2018)

Attackers altered a script on British Airways' booking and payment pages so that card details went to a lookalike domain instead of the airline. The airline said about 380,000 card payments were affected. The breach was traced to code modified at the edge of the site, not to a database intrusion.

Then

The airline notified customers and its share price fell; the UK privacy regulator later fined it £20 million.

Now

The case established that a company can be held liable for card data taken by code running in a visitor's browser, and pushed payment teams to adopt content security policy and script monitoring.

Why this matters now

Same mechanism as Optimizely: a script a site trusts runs with the site's authority in the visitor's browser, and the merchant absorbs the consequence.

February-June 2018

Ticketmaster chat-widget breach (2018)

A support chat widget supplied by a third-party vendor ran on Ticketmaster's payment pages. Attackers compromised the vendor and used the widget to lift payment details from customers in the UK and elsewhere.

Then

Ticketmaster told affected customers and pulled the widget; the UK regulator fined the company £1.25 million in 2020.

Now

The case made the point that payment-card rules scoped to a checkout page do not protect you when a vendor's JavaScript has the same access as your own.

Why this matters now

Optimizely is the same structural problem at larger scale: one vendor script, embedded by many merchants, with no boundary between the vendor's code and the merchant's forms.

June 2024

Polyfill.io supply-chain injection (2024)

A widely used JavaScript library hosted on a content delivery network changed hands. The new operator began serving code that redirected visitors of sites still loading it. Cloudflare and other providers urged sites to switch to a mirror and warned that roughly 100,000 sites used the service.

Then

Providers stood up replacement mirrors and published blocklists; sites that had pinned the original domain had to remove it.

Now

It became the standard example of a hosted script as an unmonitored dependency, and pushed more sites toward subresource integrity and vendor allowlists.

Why this matters now

Optimizely differs in one important way: the CDN served exactly what it was given. The failure was in the control plane that decides what gets written into a customer's script.

Sources

(9)