Malware Hit 178 Websites Via Optimizely: An AI Security Review
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Malware Hit 178 Websites Via Optimizely: An AI Security Review on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on tech for your team

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

Report URI says malicious JavaScript was served to visitors of 178 organizations on November 16 through their Optimizely Web experimentation snippets. Optimizely says an unauthorized party exploited a vulnerability in its Experimentation signup flow, added code to customer projects and that the flaw has been fixed. The scope of exposure and how the vulnerability enabled access to multiple customer projects remain unclear.

Malicious JavaScript was delivered to visitors of websites belonging to 178 organizations through the Optimizely Web experimentation platform on November 16, according to security researcher Scott Helme of Report URI. Optimizely said an unauthorized party exploited a vulnerability to add code to some customer projects; the script attempted several forms of data theft and device targeting, though the available reporting does not establish that every attempt succeeded.

Report URI says it examined 1,611 Optimizely snippets and found the malicious code in 188 of them. The difference between those counts reflects that a snippet can be associated with a project or site; Report URI’s published list names 178 organizations. The researcher said the true number may be higher, but did not provide a confirmed total. 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.

The payload sought to replace cryptocurrency wallet addresses in page content and clipboard activity, collect payment-card details entered into a site’s own forms, and capture cookies and screenshots, according to Report URI’s analysis. It also redirected some iPhones and iPads toward the Coruna and DarkSword exploit kits. Hudson Rock, which examined the iPhone component, cautioned that its findings were delivery observations, not evidence of confirmed iPhone compromises. Report URI said the code changed repeatedly during the day and that its behavior depended on the device and visitor activity.

Report URI observed the first Optimizely injection at 04:21 UTC on November 16 and said all infected Optimizely files it tracked had been cleaned by 23:11 UTC, roughly 19 hours later. Optimizely’s November 17 status update said it had fixed the vulnerability and removed injected code from affected projects. The company also told BleepingComputer it had ended active sessions, revoked tokens, reset access for affected accounts and notified customers it considered affected.

At a glance
reportWhen: Activity observed November 16, 2026; Op…
The developmentReport URI documented malicious JavaScript delivered through Optimizely to visitors of 178 organizations, while Optimizely confirmed unauthorized access to some customer projects.

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 Reached Visitors

The incident illustrates the reach of a third-party web script: organizations can load code from a vendor without an attacker directly breaking into each organization’s own website. Here, Report URI says the injected code was placed in the Project JavaScript field of customer projects, then delivered through snippets the sites already trusted. That meant a single supplier-side compromise could expose visitors across unrelated organizations.

The potential consequences vary by what a visitor did and what form of payment or device was involved. Report URI said card details in hosted payment frames such as Stripe or Adyen were outside the script’s reach, while numbers entered into a site’s own fields could be observed. That distinction matters: a listed organization does not establish that its full checkout, every page, or all customers were exposed. Hudson Rock specifically warned that an affected subdomain does not prove exposure across an organization’s entire site or customer base.

Report URI also assessed security policies on affected organizations’ sites: 24 of 159 blocked the code, while 68 had no policy, according to its report. Those figures describe the sample it checked, not all 178 organizations. They suggest that browser-side restrictions may limit some malicious scripts, but the incident’s main entry point was code served through a supplier already trusted by the affected pages.

Products Worth Considering

Kindle Paperwhite Signature Edition 32GB (2024 Model) - Metallic Black

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black

As an affiliate, we earn on qualifying purchases.

How Optimizely Projects Were Altered

Optimizely Web experimentation works by having a customer site load a small JavaScript snippet. The snippet carries a project’s experiments and can include an optional Project JavaScript field for customer-written code that runs on pages where the snippet is loaded. Report URI said the attacker changed that field while leaving the rest of each snippet untouched. It also said the incident was not a CDN cache-poisoning attack.

Optimizely’s status-page entry, posted at 01:02 UTC on November 17, said an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. The company told BleepingComputer the flaw was in the Experimentation account signup flow. The source reporting does not detail how that signup-flow vulnerability led to write access across unrelated projects.

Report URI listed organizations across sectors, including 32 banking and finance organizations, 23 in technology and software, and 20 in retail. Its list includes major brands and individual subdomains. Report URI also described an earlier wave beginning November 13 involving scripts from Kissmetrics, StorifyMe and Minute Media. Hudson Rock found a similar pattern and said how the code entered those services remains 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

Exposure Scope Still Needs Answers

It is not clear how the signup-flow vulnerability gave an attacker the ability to edit multiple unrelated customer projects, how many visitors encountered the payload, or whether any data was successfully stolen. The code’s reported capabilities and attempted actions do not, by themselves, establish successful theft or device compromise. Optimizely has not publicly explained the flaw’s code-level mechanics in the material cited by the source report.

The count is also subject to limits: Report URI found the code in 188 of 1,611 snippets and published 178 organization names, while saying the real number may be higher. A listed organization may represent only one subdomain or tool, not its whole website. Hudson Rock’s analysis does not confirm successful iPhone exploitation, and the method behind the earlier activity involving three other services remains unresolved.

Customer Reviews and Technical Disclosure

Optimizely says the vulnerability has been fixed, injected code removed from affected projects, and customers it identified as affected notified. Organizations using Optimizely should review their project code and access records, confirm their snippets are clean, and follow vendor guidance on account access and session resets. Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later; those versions were already available, according to the source material.

Further clarity depends on Optimizely’s account of how the signup-flow flaw enabled project changes and on customers’ investigations into whether visitors or data were affected. The reporting available as of November 17 does not provide a confirmed victim count, evidence of successful data theft, or a public technical explanation of the vulnerability. The earlier activity involving Kissmetrics, StorifyMe and Minute Media also remains under investigation, according to Hudson Rock.

Key Questions

What happened in the Optimizely incident?

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

Does a listed organization’s whole website appear to have been affected?

No such conclusion can be drawn from the published list. Some entries were individual subdomains or tools. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s full website, products, customer base or checkout.

Was data theft or an iPhone compromise confirmed?

The script attempted to collect information and direct some Apple devices toward exploit kits, according to the researchers. The source material does not confirm successful data theft or iPhone compromise; Hudson Rock described its iPhone findings as delivery observations, not demonstrated compromises.

What should affected organizations and users do?

Optimizely said it fixed the flaw, removed injected code and notified affected customers. Organizations can review their project code and access records and follow the company’s guidance. Report URI advised Apple mobile-device users to install iOS 18.7.3 or later, or iOS 26.3 or later.

Source: ThorstenMeyerAI.com

You May Also Like

Threat Modeling and Risk Assessment for Cloud Applications

Considering threat modeling and risk assessment for cloud applications reveals critical insights that can help you strengthen your security defenses effectively.

Identity and Access Management: Least Privilege or Bust

Managing access effectively hinges on least privilege principles, but understanding how to implement them is crucial—discover the key strategies to strengthen your security.

Billions Leaving Binance: A Minute-by-Minute Guide To The Hack

Binance says an attack affected about $6.3 billion across its wallets. The exchange says user funds are safe; the total remains preliminary.

Implementing Zero Trust Architecture for Cloud Systems

Just as security evolves, implementing Zero Trust Architecture for cloud systems requires continuous adaptation to stay ahead of threats.