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

🔍 Read the full analysis: The Malware That Hit 178 Websites: An AI User’s Guide To What To Check on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get the latest gadgets 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.

TL;DR

Report URI says malicious JavaScript was delivered to visitors of 178 organizations through Optimizely Web on Nov. 16, 2026. Optimizely says an unauthorized party exploited a vulnerability, and that it fixed the flaw, removed the injected code and notified affected customers. Researchers describe the code’s intended theft and exploit-kit behavior, but say its delivery does not establish that devices were compromised.

Malicious JavaScript was served to visitors of 178 organizations through Optimizely’s web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects, creating a supply-chain risk for site visitors even though the organizations’ own websites did not necessarily have to be hacked.

Report URI said it checked 1,611 Optimizely snippets and found the code in 188. It identified 178 organizations associated with the affected delivery and cautioned that the actual number could be higher. BleepingComputer separately reported that urlscan.io scans showed the script loading or attempting to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listed organization does not mean every page, service or customer of that organization was exposed.

Optimizely’s Nov. 17 status-page notice said an unauthorized party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects. The company told BleepingComputer the flaw was in the Experimentation account signup flow. It said it had fixed the vulnerability, removed the injected code, notified affected customers, ended active sessions, revoked tokens and reset access for affected accounts.

Report URI said the first injection it observed was at 04:21 UTC on Nov. 16, and that all infected Optimizely files had been cleaned by 23:11 UTC that day, a period of about 19 hours. The researcher described code intended to replace cryptocurrency wallet addresses, capture payment-card details entered into some site forms, collect cookies and screenshots, and send some iPhones and iPads toward the Coruna and DarkSword exploit kits. These are reported capabilities and delivery observations, not proof that every targeted action succeeded.

At a glance
reportWhen: Attack observed Nov. 16, 2026; Optimize…
The developmentReport URI identified malicious JavaScript served through Optimizely Web to visitors of 178 organizations on Nov. 16, and Optimizely confirmed an exploited vulnerability in its Experimentation service.

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

Why the Shared Script Matters

The incident shows how a third-party script can extend a supplier’s security failure to many unrelated websites. Optimizely customers used the platform to run experiments on their pages; visitors’ browsers loaded its JavaScript from an address those sites already trusted. That arrangement can make malicious code difficult for a visitor to distinguish from ordinary site functionality.

Report URI also examined security policies on affected organizations’ sites. It said 24 of 159 blocked the code, while 68 had no policy. Those figures describe the policies in the researcher’s assessment, not the number of organizations proven compromised. They do indicate that defenses against unexpected script behavior varied among the sites studied.

The potential consequences depend on what a visitor did, which device was used, and how the site handled information. Report URI said card numbers entered into a site’s own form fields could be in scope, while card details entered into hosted payment iframes such as Stripe or Adyen were outside the skimmer’s reach. That distinction matters: the available findings do not support treating every checkout or customer account as exposed.

Products Worth Considering

Bose Smart Dolby Atmos Soundbar with Alexa, A.I. Dialogue Mode, and Bluetooth, Black

Bose Smart Dolby Atmos Soundbar with Alexa, A.I. Dialogue Mode, and Bluetooth, Black

As an affiliate, we earn on qualifying purchases.

How Optimizely’s Snippet Was Changed

Optimizely Web customers load a small JavaScript snippet that carries their experiments. Report URI said customer projects can also contain an optional Project JavaScript field: custom code that runs across pages. According to the researcher, the attacker added code to that field in customer projects while leaving the rest of each snippet untouched. The affected files continued to be delivered by Optimizely.

Report URI said the incident was not a CDN cache-poisoning attack. Optimizely’s own websites also carried the code, according to the source report. The researcher’s account and Optimizely’s brief statement establish that customer projects were altered through the platform, but do not explain the technical path from a signup-flow vulnerability to write access across unrelated projects.

Report URI also described an earlier wave beginning Nov. 13, in which the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media. Those sites are separate from the 178-organization Optimizely list. Hudson Rock reported finding the same pattern and said how the code entered those services remained unresolved.

“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 Nov. 17

What Investigators Have Not Explained

Optimizely has not publicly described the code-level mechanics of the signup-flow vulnerability or how it allowed access to so many separate customer projects. The company’s statements say the flaw was fixed and the injected code removed, but do not specify how many projects or visitors were affected beyond the researchers’ findings.

Report URI’s count of 178 organizations is based on the snippets it identified; it said the real number may be higher. The count of 188 snippets is not the same as 188 organizations, and a named company may have only an individual subdomain implicated. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s whole website, product range, customer base or checkout system.

Researchers described what the JavaScript attempted to do, but the supplied findings do not establish how many people entered card details, copied wallet addresses, had information collected, or experienced a successful device compromise. Hudson Rock explicitly characterized its iPhone findings as delivery observations rather than demonstrated compromises. The duration and scope of the earlier activity involving three other providers also remain unclear.

Customer Checks and Security Follow-Up

Optimizely says it has fixed the vulnerability, removed injected code from affected projects and notified affected customers. Its reported steps to end active sessions, revoke tokens and reset account access address access control, but the company has not supplied a public technical account explaining how the incident began or how it will prevent a similar route from being used again.

Organizations using Optimizely should check the company’s notices and review their projects and site behavior for unauthorized changes, while following guidance from their security teams and service providers. Visitors who used an affected site during the reported window may wish to check for suspicious activity relevant to what they did there. Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later; it said those versions had been released months earlier by Apple.

Further reporting would need to clarify the vulnerability’s mechanics, the full set of affected projects and the extent of any actual data theft or device compromise. Until those details are available, the number of organizations identified should not be read as a count of confirmed victims.

Key Questions

What happened in the Optimizely incident?

Report URI says malicious JavaScript was delivered through Optimizely Web to visitors of 178 organizations on Nov. 16, 2026. Optimizely confirmed that an unauthorized party exploited a vulnerability to add code to some customer projects.

Were all pages or customers of the named organizations affected?

No such broad exposure is established. The researchers’ list can refer to particular snippets or subdomains, and Hudson Rock warned that an affected subdomain does not prove exposure across an organization’s full website, products or customer base.

Does the report prove that iPhones were compromised?

No. Hudson Rock characterized its findings as delivery observations, not demonstrated iPhone compromises. The report describes code that could send some Apple devices toward exploit kits, but does not establish successful compromise for every targeted device.

What should iPhone and iPad users do?

Report URI advised users to update to iOS 18.7.3 or later, or iOS 26.3 or later. Users should also follow relevant security guidance and monitor for suspicious activity, particularly if they entered payment details or interacted with wallet addresses on a potentially affected page during the incident window.

What remains unknown about the attack?

Optimizely has not publicly explained the signup-flow flaw’s technical mechanics or how it enabled changes across unrelated customer projects. The full number of affected projects, the number of people whose information was actually taken, and whether any devices were successfully compromised have not been established in the supplied reporting.

Source: ThorstenMeyerAI.com

You May Also Like

The City That Watches Itself: The Living Digital Twin, and the God’s-Eye View We’re Building

Cities are developing dynamic digital twins powered by advanced sensors and AI, creating real-time, interactive models that enhance planning but also pose surveillance risks.

Every Benchmark Launched 2023-2024 Has Fallen — The METR / SWE-Bench / CORE-Bench / MLE-Bench / PostTrainBench Sequence

Every major AI research benchmark launched between 2023-2024 has reached or is nearing saturation, signaling rapid progress in AI capabilities.

What Happened To TheNumbers.com

TheNumbers.com, a key source for box office and entertainment data, is currently inaccessible. Details on the outage and future plans remain unclear.

Forge or Self-Host? The Real Cost of Sovereign AI

Analyzing the financial and technical realities of building or buying sovereign AI in 2026, with insights into costs, capabilities, and strategic implications.