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

TL;DR

Security researcher Scott Helme of Report URI says malicious JavaScript was served through Optimizely Web to visitors of 178 organisations on Nov. 16, including sites run by major media, retail and financial brands. Optimizely says an attacker exploited a vulnerability in its Experimentation account signup flow, removed the injected code and notified affected customers. The code attempted to steal data and redirect crypto payments, but the number of people harmed and whether any iPhones were compromised remain unknown.

Malicious JavaScript was served to visitors of 178 organisations through the Optimizely Web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely says an unauthorized party exploited a vulnerability to add code to customer projects, creating a supply-chain incident that exposed visitors to attempted data theft and crypto-payment manipulation.

Before you orderOffer from Amazon

Get privacy and security gear delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

Report URI says it examined 1,611 Optimizely snippets and found the malicious code in 188. It counted 178 organisations among the affected sites and cautioned that the actual number could be higher. The figures describe infected snippets and organisations identified by the researcher; they do not establish how many visitors were exposed or harmed.

The code ran through a JavaScript file that customer sites intentionally loaded from Optimizely. According to Report URI, the attacker inserted code into customers’ Project JavaScript fields, while the rest of each snippet remained unchanged. The researcher said this was not a CDN cache-poisoning attack. Optimizely told BleepingComputer that the vulnerability was in the Experimentation account signup flow.

Report URI says the payload attempted to replace cryptocurrency wallet addresses on webpages and in clipboard activity, capture card numbers entered into site forms, and collect cookies and screenshots. It also observed delivery attempts involving the Coruna and DarkSword exploit kits targeting older iPhones and iPads. These describe the code’s reported functions and delivery; they do not confirm that every attempt succeeded or that a device was compromised.

Report URI first observed an Optimizely injection at 04:21 UTC on Nov. 16. The researcher says all infected Optimizely files had been cleaned by 23:11 UTC that day. Optimizely’s status-page notice, posted at 01:02 UTC on Nov. 17, said the vulnerability was fixed and injected code removed from affected projects. The company also told BleepingComputer it had ended active sessions, revoked tokens and reset access for affected accounts.

At a glance
reportWhen: The malicious code was observed on Nov.…
The developmentReport URI says malware reached visitors of 178 organisations through Optimizely Web after an attacker exploited a vulnerability in the platform.
Bar chart: 178 organisations served the malicious code through Optimizely on November 16, 2026, according to Report URI, by sector, largest 8 of 20 sectors. Highlighted: banking and finance 32, the largest group, including HSBC sites in several countries and Equifax. Technology and software 23, retail and fashion 20, streaming and entertainment 12, news and media 10, airlines and travel 9, healthcare and pharma 8, industrial and manufacturing 8. 56 more in 12 other sectors. 188 infected snippets among 1,611 checked; Report URI says the real number is likely higher
Who served the malicious code, by sector. Source: Report URI, "World's Largest Brands Infected With Malware Via Optimizely", November 16, 2026. Graphic: Thorsten Meyer AI.

Risks for Site Visitors and Businesses

The incident shows how a vulnerability at a third-party web provider can put visitors at risk even when the websites they visit have not themselves been breached. Because the script came from an address customer sites already trusted, their existing permission to load Optimizely did not, by itself, distinguish the malicious addition from ordinary platform code.

For people using affected sites, the reported goals included stealing payment details and altering crypto transfers. Visitors should be alert to suspicious transactions and account activity, particularly if they entered sensitive information during the exposure window. The available reporting does not identify confirmed victims, quantify stolen data, or show that every malicious function worked.

Report URI also checked security policies on affected organisations’ sites. It found that 24 of 159 blocked the code and that 68 had no policy at all. Those counts point to a potential gap in how sites restrict browser-executed scripts, but the source does not provide a broader industry comparison or establish that a policy would have prevented every part of this incident.

Products Worth Considering

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

As an affiliate, we earn on qualifying purchases.

How Optimizely’s Script Was Altered

Optimizely Web lets organisations run experiments on their webpages using a small JavaScript snippet. A customer’s snippet can include Project JavaScript, a field for custom code that runs on pages loading the snippet. Report URI says the attacker wrote malicious code into that field in customer projects, so sites continued to load a file from the platform’s normal, trusted address.

The incident was not limited to a single moment or provider. Report URI’s timeline records an earlier wave through scripts associated with Kissmetrics, StorifyMe and Minute Media on Nov. 13. Its reporting places the first Optimizely injection it saw on Nov. 16, with later observations that day of address replacement, a card skimmer and expanded iPhone exploit delivery. The earlier activity is part of the reported timeline; the supplied information does not establish who was responsible for either wave or whether they were connected.

Optimizely’s status notice confirmed that an unauthorized party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects. The company said it had fixed the vulnerability and notified affected customers. The company’s statements establish its response, while the technical mechanism that enabled access to multiple unrelated projects has not been publicly detailed in the supplied reporting.

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

— Optimizely, in a status-page notice posted Nov. 17

Victim Counts and Access Path Remain Unknown

The supplied reporting does not say how many visitors received the malicious code, how many entered payment details, or whether any crypto payments were redirected. It also provides no confirmed count of stolen credentials, affected accounts or financial losses. Report URI’s 178 organisations and 188 infected snippets are detection counts, not measures of individual victims.

It remains unclear how the signup-flow vulnerability gave an attacker the ability to write to projects belonging to many unrelated customers. Report URI said it did not know how the attacker gained that access, and Hudson Rock said Optimizely’s disclosure did not explain the flaw’s code-level mechanics. The sources also do not establish who carried out the attack or whether the Nov. 13 activity was related.

For Apple devices, Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock cautioned that its findings showed exploit delivery, not demonstrated compromise. The material does not confirm that an iPhone or iPad was successfully infected through this campaign.

Customer Notifications and Security Reviews

Optimizely says it has fixed the vulnerability, removed injected code from affected projects and notified affected customers. It also said active sessions were ended, tokens revoked and access reset for affected accounts. The supplied sources do not set out a further public investigation deadline or say when a more detailed technical report will be released.

Organisations using Optimizely should review notifications from the company, check their projects and access records, and assess whether the relevant pages or visitors require follow-up. Visitors concerned about exposure can review recent card and crypto activity and install current software updates. Those steps are precautionary; they do not indicate that any particular visitor or device was compromised.

Further clarity depends on details not yet provided in the cited accounts: the exact signup-flow flaw, how access spread across customer projects, and whether investigations identify successful theft or device compromise. Until those findings are available, the confirmed scope is the code observed by Report URI and the response Optimizely has described.

Key Questions

What happened to the 178 organisations?

Report URI says visitors to 178 organisations received malicious JavaScript through Optimizely Web on Nov. 16. The code was added to customer projects through a vulnerability in Optimizely’s Experimentation service, according to the company.

Were the organisations’ own websites hacked?

The reported delivery path was a trusted Optimizely script loaded by the sites, not a direct compromise of each organisation’s website. Report URI says malicious code was inserted into Optimizely customer projects.

What did the malware attempt to do?

Report URI says it attempted to alter crypto wallet addresses, capture card numbers entered into site forms, collect cookies and screenshots, and deliver exploit kits to older Apple devices. The reporting does not confirm that each attempt succeeded.

Have iPhones been confirmed compromised?

No confirmed iPhone compromise is described in the supplied sources. Hudson Rock characterized its findings as observations of exploit delivery, not demonstrated device compromises. Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later.

What should businesses and visitors do now?

Optimizely says it fixed the flaw, removed the injected code and notified affected customers. Businesses should review vendor notices and relevant access records; visitors can check payment and crypto activity and keep devices updated. These are precautionary steps, not proof that a particular account or device was affected.

Source: Thorsten Meyer AI

You May Also Like