Optimizely Flaw Served Malware to 178 Brands, 32 in Finance

Malicious JavaScript was served on 16 November to visitors of 178 organisations through Optimizely Web, the experimentation tool many large sites load on every page, security firm Report URI said in a report by Scott Helme. Its list includes Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock.

Banking and finance was the largest group, with 32 of the 178 organisations, or 18%, by our arithmetic. Optimizely said in a statement on its status page that “an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects”, and that it has fixed the flaw and removed the code.

Business Pill · Embedded Dependency

An evergreen Business Engineer explainer on embedded dependencies. It teaches the general idea only and does not discuss Optimizely or this attack.

The key insight: Report URI found malicious code in 188 of 1,611 Optimizely Web snippets it checked, belonging to 178 organisations, on 16 November; 32 of them, 18% by our arithmetic, were in banking and finance, and Optimizely says an attacker exploited a vulnerability in its Experimentation product.

How the Code Got In

Each Optimizely Web customer loads a JavaScript snippet from Optimizely’s CDN that includes an optional field, Project JavaScript, which runs on every page. Report URI says the attacker wrote a loader into that field across customer projects, and the rest of each snippet was untouched, so the file was still served from cdn.optimizely.com with Optimizely’s certificate.

Report URI says it fetched 1,611 distinct Optimizely snippets and found 188, belonging to 178 organisations, infected, about 11.7% of those it checked, by our arithmetic. It says “The real number is likely higher as we could only check snippets we could find in time”.

BleepingComputer said it independently confirmed, using urlscan.io scans, that the malicious script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN, Smartsheet and Salesforce, and that it analysed copies of the modified files.

Salesforce said it was investigating unauthorized Optimizely script changes and had disabled them as a precaution, Reuters reported. Reuters said it could not immediately ascertain whether the code was successfully used in each case, and that Zoom, HSBC, Equifax, CNN and IKEA did not immediately respond to its requests for comment.

An Optimizely spokesperson told Cointelegraph that the vulnerability was in its “Experimentation account signup flow”. “We have blocked access to the vulnerable path and deployed a fix”, the spokesperson said, adding that Optimizely ended active sessions, revoked tokens, reset access for affected user accounts and notified all affected customers.

Organisations whose Optimizely Web snippet carried the malicious code on 16 November 2026, by sector, per Repo
Organisations whose Optimizely Web snippet carried the malicious code on 16 November 2026, by sector, per Report URI, which found 188 infected snippets belonging to 178 organisations among 1,611 it checked. Banking and finance is 32 of 178, 18%, by our arithmetic; 49 more organisations sit in 11 smaller sectors.

What the Script Did

Report URI describes a multi-purpose kit. It swapped cryptocurrency wallet addresses for the attacker’s, skimmed payment cards typed into a site’s own form fields, and stole cookies and screenshots. Cards entered in hosted payment iframes, such as Stripe or Adyen, were out of its reach, it says.

On iPhones and iPads, the script delivered the Coruna and DarkSword iOS exploit kits, Report URI says. It says the kit’s own comments mark iOS 18.7.3 and later, and 26.3 and later, as patched, and it advises visitors to update.

The attacker’s wallets received about $7,040 within roughly nine hours on 16 November, as of 19:25 UTC, Report URI says; Cointelegraph, checking blockchain records, put it at about $7,100. Report URI says it cannot see how many cards or cookies reached the attacker’s server.

The 17-Hour Window

Report URI’s timeline puts the first Optimizely injection, in the BBC’s snippet, at 04:21 UTC on 16 November. The card skimmer was added at 13:43 UTC, and a mass clean-up ran from about 20:40 UTC. At 21:52 UTC, one of the 188 snippets, TalkTalk’s, was still infected.

From the first injection to that 21:52 UTC check is 17 hours and 31 minutes, by our arithmetic. Optimizely’s status page entry is timed 01:02 UTC on 17 November.

Who Was Exposed

After banking and finance, Report URI counts 23 technology and software companies, 20 retail and fashion brands, 12 streaming and entertainment services and 10 news and media sites. The finance group includes Paychex, several HSBC country sites, Equifax, SmartAsset and ABN AMRO; six more are listed under crypto and trading, among them Ledger, IG and OANDA.

Being on the list means a site served the script to visitors, not that the organisation’s own systems were breached. Report URI says “A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached”.

Of the affected organisations whose content security policy it could evaluate, Report URI says 24, or 15%, blocked the payload, while 68 had no policy at all. HSBC’s policy blocked the external script and the data theft, it says, but an inline copy still ran.

How It Compares

The incident landed the same day Google’s Threat Intelligence Group published its report on AI-driven exploitation (our piece). None of the sources on the Optimizely attack say AI was used in it.

It also came the same day as a Chase outage that the bank attributed to a software bug, with no evidence of a cyber link (our piece), and days after a Microsoft 365 outage (our explainer). Those were service failures; this was code served to visitors.

The Structural Read

As we read Report URI’s account, the code came from a host every affected site already trusted, so allowing cdn.optimizely.com in a security policy did not help; the 24 organisations it says blocked the payload had a restrictive script policy.

As we read the timeline, the attack ran 17 hours and 31 minutes from the first injection to the 21:52 UTC check, by our arithmetic, and the card skimmer was added only at 13:43 UTC.

As we read the list, finance and trading names carry the most exposure: 32 banking and finance organisations plus six in crypto and trading, where wallet addresses and card fields sit on the page.

Report URI, in its report

“A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached”

Three Implications

FOR SITE OWNERS Report URI advises Optimizely Web customers to check every project’s Project JavaScript, rotate credentials and treat cards entered in their own forms on 16 November as potentially exposed.

FOR SECURITY TEAMS Report URI says 68 of the affected organisations it checked had no content security policy at all, and 24 blocked the payload.

FOR VISITORS Report URI advises updating iPhones and iPads to iOS 18.7.3 or later, or 26.3 or later, and checking any crypto transfer made on an affected site.

The Business Engineer Lens

This story maps onto the Business Engineer framework AI and the Great SaaS Bifurcation.

The analysis says: “It’s a structural bifurcation driven by two converging forces: the democratization of development through AI-assisted coding and the intensification of enterprise integration dependencies.”

As we read it, this attack ran through one such integration dependency: an experimentation tool loaded on every page of 178 organisations’ sites. The analysis does not discuss this attack.

What Is Not Established

How the attacker reached so many unrelated customer projects is not fully explained: Optimizely has named a vulnerability in its signup flow, and Report URI says it does not know whether a compromised system, a credential or something else was involved. No source has said who the attacker is, how many cards were taken, or whether any named organisation’s customers lost money.

This Week In The AI Supercycle

AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source

This week’s issue: the Nvidia leadership change, read as the AI build-out losing its central banker: who now finances the GPU landlords, backstops the data centres and sponsors open models, and why two labs are becoming the bank.

Read the full issue →

Business Engineer Framework

AI and the Great SaaS Bifurcation

A Business Engineer analysis of how software splits as AI changes how it is built and how deeply it is wired into the enterprise.

Read the Map of AI →

The Bottom Line

Report URI found malicious code in 188 Optimizely Web snippets belonging to 178 organisations on 16 November, 32 of them in banking and finance; Optimizely says an attacker exploited a vulnerability in its Experimentation product, that it has fixed it and removed the code, and that affected customers were notified.

95,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.

A note on sourcing. The counts, list of organisations, timeline, payload description and wallet figures come from Report URI’s report of 16 November 2026 by Scott Helme, which we read in full; BleepingComputer’s independent urlscan checks and file analysis are from its article of the same day. Optimizely’s words are from its status page entry of 17 November 2026 and its spokesperson’s statements to Cointelegraph and Gizmodo.

The post that drew our attention was by HormuzLetter on X. Shares, the 17-hour window and sector totals are our arithmetic. Being named in Report URI’s list means a site served the script, not that the organisation was breached.

Sources: Report URI: World’s Largest Brands Infected With Malware Via Optimizely (16 Nov 2026) · Optimizely status page: Web Experimentation Security Incident (17 Nov 2026) · BleepingComputer (16 Nov 2026) · Cointelegraph (16 Nov 2026) · HormuzLetter on X (17 Nov 2026)

Scroll to Top
FourWeekMBA