AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: AI User Checklist: Reviewing Accounts After Malware Hit 178 Websites on ThorstenMeyerAI.com

TL;DR

Report URI says malicious JavaScript was served on November 16 through Optimizely Web snippets on sites associated with 178 organisations. Optimizely says an unauthorized party exploited a vulnerability in its Experimentation signup flow, removed the injected code and notified affected customers. Researchers have not established that the code successfully compromised visitors‘ devices or accounts.

Malicious JavaScript reached visitors to sites associated with 178 organisations on November 16 through scripts served by Optimizely’s Web experimentation platform, according to security researcher Scott Helme of Report URI. Optimizely says an unauthorized party exploited a vulnerability in its Experimentation signup flow to add code to some customer projects; the company says it fixed the flaw, removed the code and notified affected customers.

Report URI says it found the code in 188 of 1,611 Optimizely snippets it checked and believes the actual number may be higher. The organisation count refers to sites where the malicious script was identified, not necessarily every page, service or customer system belonging to those organisations. BleepingComputer separately reported confirming that the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce.

The injected JavaScript was placed in an optional customer-project field called Project JavaScript, according to Report URI. The code was then delivered through Optimizely’s trusted snippet on affected sites. Report URI says the rest of each snippet was untouched and says this was not a content delivery network cache-poisoning attack. Optimizely told BleepingComputer that it ended active sessions, revoked tokens and reset access for affected user accounts.

Report URI says the code could try to replace cryptocurrency wallet addresses in page text, form fields and clipboard contents; capture payment-card details entered into a site’s own forms; and collect cookies and screenshots. It also describes attempts to direct older Apple devices to the Coruna and DarkSword exploit kits. The payload changed 26 times during the day, according to the researcher. These are reported capabilities and observations; they do not establish that every visitor was targeted successfully or that a device was compromised.

At a glance
reportWhen: Attack observed November 16, 2026; Opti…
The developmentSecurity researchers traced malicious JavaScript delivered to visitors of 178 organisations‘ websites to unauthorized changes made through Optimizely’s Experimentation platform.

Optimizely script attack · Nov 13 – Nov 17, 2026

How one trusted script carried malware to 178 websites

The sites were not hacked themselves. The code arrived inside a file they loaded on purpose.

The route (schematic)

Customer projects at Optimizelyvulnerability exploited, per OptimizelyCode written into Project JavaScript
served as usual from Optimizely
The trusted snippetsame address, rest of the file untouchedCarries the attacker’s loader
loaded on every page of
Company websites178 organisations found by Report URI
runs in visitors‘ browsers
Visitorswhat the code tried, per Report URI
Swap crypto addressesTake cookies and screenshotsSkim cards in a site’s own formsiPhone exploit kits
All Optimizely files clean by 23:11 UTC

Whether any iPhone was compromised has not been shown.

Timeline (UTC)

  1. Nov 13Earlier wave through three other providers‘ scriptsKissmetrics, StorifyMe, Minute Media
  2. Nov 16 04:21First Optimizely injection seen
  3. 08:28Address-swapping payload first seen on a site
  4. 13:43Card skimmer added
  5. 17:13iPhone exploit delivery widened
  6. 19:24Report URI sweep: 186 of 1,611 snippets infected
  7. 21:52Only 1 of 188 infected snippets left
  8. 23:11All infected Optimizely files cleaned
  9. Nov 17 01:02Optimizely confirms the incident on its status page
Why the sites let it in: the code came from the vendor’s own trusted address, so allowing Optimizely did not stop it.

Sources: Report URI (Scott Helme), Nov 16, 2026, timeline and update of Nov 17; Optimizely status page, Nov 17, 2026; Hudson Rock (Infostealers.com), Nov 16–17, 2026. The route is a schematic.

Graphic: Powered by Thorsten Meyer AI

How a Trusted Script Spread the Code

The incident shows how a compromise at a third-party provider can put visitors at risk even when the affected organisations’ own websites have not been hacked. Sites had deliberately loaded Optimizely’s scripts for experimentation, so malicious code inserted into customer projects could arrive through a source those sites already trusted. The exposure was distributed across many organisations, while visitors had little visible indication that a page’s script had changed.

Report URI also checked security policies on affected organisations’ sites. It found that 24 of 159 organisations blocked the code, while 68 had no policy at all. Those figures describe the checks reported by the researcher, not a complete measurement of security across all 178 organisations. They nevertheless point to a practical issue: browser security policies can limit what injected scripts are able to do, but protection varied among the sites examined.

For users, the findings support reviewing recent account activity and payment statements, especially if they visited an affected site or entered sensitive details during the exposure period. The reported presence of malicious code alone does not mean an individual’s information was stolen. Businesses, meanwhile, may need to check their own projects, scripts and access controls rather than assume that cleaning a supplier’s files resolves every downstream concern.

Vitamix Nano Personal Blender with SmoothiePilot Technology, Black

Vitamix Nano Personal Blender with SmoothiePilot Technology, Black

KitchenAid Artisan 5-Quart Tilt-Head Stand Mixer with Flex Edge Beater

KitchenAid Artisan 5-Quart Tilt-Head Stand Mixer with Flex Edge Beater

As an affiliate, we earn on qualifying purchases.

The November 16 Exposure Window

Report URI says its first observed Optimizely injection was at 04:21 UTC on November 16. By 23:11 UTC that day, it says all infected Optimizely files it tracked had been cleaned, a window of about 19 hours. Optimizely’s November 17 status-page notice, posted at 01:02 UTC, said the company had fixed the vulnerability and removed injected code from affected projects.

Report URI’s published list covers organisations across several sectors. Banking and finance accounted for 32 entries, followed by technology and software with 23 and retail with 20. The list includes sites associated with Zoom, the BBC, CNN, HSBC, Salesforce, IKEA, Equifax, GitLab, Ledger, Peacock, Air France-KLM and UNICEF USA. A listing may refer to one subdomain, such as a particular tool, rather than a company’s entire website or checkout system.

Report URI also says the same actor’s injector appeared from November 13 in scripts associated with Kissmetrics, StorifyMe and Minute Media, on sites outside the 178-organisation list. Hudson Rock reported finding the same pattern and said how the code entered those services remained unresolved. The reports describe related observations, but do not establish the full scope or connection among all affected providers.

„An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.“

— Optimizely, in its status-page update on November 17

What Researchers Cannot Yet Confirm

The available information does not explain the technical steps that allowed the attacker to write to unrelated customer projects. Optimizely has described the flaw as being in the Experimentation account signup flow, but Hudson Rock says the company’s disclosure does not explain the bug’s code-level mechanics. It is also unclear whether Report URI’s sample represents the full number of affected snippets or organisations.

Researchers have described what the script attempted to do, but the source material does not establish how many visitors saw each function, whether specific card or account data was taken, or whether any visitors’ devices were successfully exploited. Hudson Rock explicitly characterizes its iPhone findings as delivery observations rather than demonstrated compromises. Affected-site listings also do not show that an organisation’s whole site, customer base or payment system was exposed.

Customer Reviews and Security Follow-Up

Optimizely says it has fixed the vulnerability, removed injected code, ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers. The company’s statements, as reported here, do not provide a detailed account of how the attacker crossed between projects or whether further technical findings will be published. The next confirmed developments would be additional disclosure from Optimizely or affected organisations about their investigations and any user notifications.

Report URI advises iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. Users who visited a listed site during the reported window can review bank and card activity and watch for unfamiliar account sessions, while treating any concern as a reason to contact the relevant provider. Organisations can check whether their own domains and Optimizely projects appear in the researcher’s findings, review access and session changes, and assess whether their browser security policies blocked the script. None of those checks alone establishes that data was stolen or that an account was compromised.

Key Questions

What happened to the 178 organisations‘ websites?

Report URI says visitors to sites associated with 178 organisations received malicious JavaScript through Optimizely Web snippets on November 16. Optimizely says an unauthorized party exploited a vulnerability to add code to some customer projects.

Does being on the list mean a company’s whole website was affected?

No. A listing can refer to a particular subdomain or tool. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s entire website, customer base or checkout system.

Was information definitely stolen from visitors?

The reports describe code that attempted to collect or alter information, but the available findings do not establish how many people were affected or confirm successful theft of particular visitors’ data.

What should visitors do now?

People who visited a listed site during the reported period can review payment-card and bank activity and check accounts for unfamiliar sessions or activity. Report URI advises Apple-device users to install iOS 18.7.3 or later, or iOS 26.3 or later.

Has Optimizely removed the malicious code?

Optimizely said it fixed the vulnerability and removed injected code from affected projects. Report URI said the infected Optimizely files it tracked had been cleaned by 23:11 UTC on November 16.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Incident postmortem builder for managed service providers

A new incident postmortem builder is being tested for small managed service providers to improve post-incident communication and efficiency.

Prepare For A Faster Cyberattack Landscape With These Steps

U.S. agencies and Microsoft describe AI-assisted attacks, while OpenAI forecasts more AI-found vulnerabilities. Here are the confirmed risks and defenses.

Active Exploitation Of CVE-2026-8037 Signals Need For Enhanced Cyber Operations

Cybersecurity experts confirm active exploitation of CVE-2026-8037, prompting urgent need for enhanced monitoring and response strategies for small and mid-sized organizations.

What’s Behind The OpenSSH SSHole Bug Affecting Some Linux Servers?

CVE-2026-123158 can bypass SSH password checks on certain musl-based Linux setups. See the conditions, response and steps for administrators.