AI And The 178-Site Malware Incident: What Should You Check?
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: AI And The 178-Site Malware Incident: What Should You Check? 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 delivered through Optimizely snippets on sites associated with 178 organizations on Nov. 16, 2026. Optimizely says it fixed a vulnerability and removed the injected code; the script attempted several forms of theft, but the available reporting does not establish that every listed site or visitor was compromised.

Malicious JavaScript was served to visitors of sites associated with 178 organizations through Optimizely’s 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 some customer projects; the incident matters because visitors could receive the code through a third-party script their chosen website had loaded.

Report URI says it found the code in 188 of 1,611 Optimizely snippets it checked and warned that the actual number may be higher. That count refers to snippets, not necessarily 188 separate organizations. The script was delivered from Optimizely through customer snippets, while the malicious code was written into the projects’ optional Project JavaScript field, according to Report URI. The researcher said the rest of each snippet was untouched and ruled out a content-delivery-network cache-poisoning attack.

Optimizely’s status page said it had fixed the vulnerability and removed the injected code from affected projects. The company told BleepingComputer the flaw was in the Experimentation account signup flow, and said it had notified affected customers. It also said it ended active sessions, revoked tokens and reset access for affected accounts. Report URI recorded the first injection it observed at 04:21 UTC on Nov. 16 and said infected files had been cleaned by 23:11 UTC that day—about 19 hours later.

Report URI’s analysis says the script attempted to replace cryptocurrency wallet addresses in page content and clipboard activity, collect payment-card details entered into a site’s own form fields, and capture cookies and screenshots. It also attempted to direct some iPhones and iPads to the Coruna and DarkSword exploit kits. Report URI said cards entered into hosted payment frames, such as those used by Stripe or Adyen, were outside the script’s reach. Hudson Rock said its iPhone findings were delivery observations, not evidence of demonstrated device compromise.

At a glance
updateWhen: The incident was observed Nov. 16, 2026…
The developmentReport URI identified malicious JavaScript served through Optimizely’s web experimentation platform, and Optimizely confirmed an unauthorized party exploited a vulnerability to add code 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

What Visitors and Site Operators Should Check

The incident shows how a compromise of a third-party web service can expose visitors without attackers first breaking into each customer website. A trusted script can run in a page visitors already use, making the difference between legitimate and malicious code difficult for users to see. The reported payload sought data in specific situations; its presence does not establish that every listed visitor had information stolen.

Visitors who used an affected site during the reported window should be alert to unusual wallet transactions and consider whether they entered card details directly into a site’s own form. They should review relevant account and payment activity and contact their bank or card issuer if they see unauthorized charges. Report URI advises iPhone users to install iOS 18.7.3 or later, or iOS 26.3 or later. The source says both versions had been released months earlier, but does not establish that installing them would reverse any prior exposure.

For organizations, the incident puts attention on third-party scripts, account access and web security policies. Report URI found that only 24 of 159 organizations it checked blocked the code with their site security policies, while 68 had no policy. Those figures describe the researcher’s checks, not a measure of confirmed customer data theft. A policy that limits which scripts can run may reduce exposure, but the report does not claim it would prevent every attack of this kind.

Products Worth Considering

As an affiliate, we earn on qualifying purchases.

How the Optimizely Snippets Were Altered

Optimizely Web lets customers run experiments on their websites by loading a small JavaScript snippet from the platform. A project can include Project JavaScript, an optional field for customer-written code that runs on pages using that project. Report URI says the attacker placed the malicious code in that field across customer projects, so affected sites continued loading a file from an address they already trusted.

Report URI published a list of 178 organizations, including sites associated with Zoom, the BBC, CNN, HSBC, Salesforce and IKEA. It counted 32 organizations in banking and finance, 23 in technology and software, and 20 in retail. BleepingComputer separately said urlscan.io scans confirmed that the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listing may refer to a particular subdomain; it does not establish that every page, product, checkout system or customer of an organization was exposed.

Report URI also described an earlier wave beginning Nov. 13, when the same actor’s injector appeared in scripts from Kissmetrics, StorifyMe and Minute Media. Hudson Rock reported a similar pattern but said how the code entered those services remained unresolved. The available material does not connect that earlier activity to confirmed compromise of the same customers.

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

— Optimizely, in a status-page update posted Nov. 17 at 01:02 UTC

What the Investigation Has Not Established

Optimizely has not publicly explained the code-level mechanics of the signup-flow vulnerability or how it enabled access to unrelated customer projects. Report URI says it could not determine how the attacker obtained write access at that scale, and Hudson Rock likewise said the disclosure did not explain the bug’s mechanics. The source material gives no confirmed attacker identity or account of the attacker’s motive.

The 178-organization list does not prove that every page or visitor was affected. Nor does the presence of the script prove that wallet funds, payment data, cookies or screenshots were successfully stolen. The reports describe what the code attempted to do and, for the iPhone stage, Hudson Rock explicitly distinguishes delivery observations from successful compromise. The number of affected users, any confirmed data theft and the total scope of affected projects remain unclear.

Report URI says the code was rebuilt 26 times during the day, but that raw count does not establish how many visitors encountered each version or how many were affected. The source material does not provide a verified count of exposed visitors or a confirmed number of resulting financial losses.

What Customers Should Do Now

Organizations using Optimizely should review the company’s incident notices, confirm that affected projects and accounts have been addressed, and check their own logs and customer communications for relevant exposure. They should review third-party scripts and access controls, and consider whether their site security policies restrict unapproved scripts. The incident reports do not specify a universal customer remediation checklist, so businesses should follow Optimizely’s guidance and their own security-response procedures.

Visitors who used a listed site during the reported period can review card statements and cryptocurrency activity, and take account-specific steps if they entered sensitive information into a page. Users should apply the iOS updates cited by Report URI if they have not already done so. These steps address potential risk; they do not confirm that a particular visitor was affected.

The next key developments are any fuller technical account from Optimizely, further findings about the earlier activity involving other providers, and confirmation of whether investigators identified data theft or compromised devices. Until those details are public, the reported delivery window and attempted behaviors should not be treated as proof of individual compromise.

Key Questions

What happened in the Optimizely malware incident?

Report URI says malicious JavaScript was served through Optimizely snippets on sites associated with 178 organizations on Nov. 16, 2026. Optimizely confirmed an unauthorized party exploited a vulnerability to add code to some customer projects.

Were all 178 organizations’ websites and customers affected?

No such conclusion is established by the reports. A listed organization may be represented by a specific subdomain, and the listing does not show that every page, service or visitor was exposed.

What did the malicious script attempt to do?

Report URI says it attempted to replace cryptocurrency wallet addresses, collect card details entered into sites’ own forms, capture cookies and screenshots, and direct some Apple devices to exploit kits. Attempted behavior is not proof that data was successfully stolen or a device compromised.

What should visitors check?

Review card and cryptocurrency activity if you used an affected site during the reported period, and contact your bank or card issuer about suspicious charges. Report URI advises iPhone users to update to iOS 18.7.3 or later, or iOS 26.3 or later. These actions do not establish that an individual was exposed.

Has Optimizely fixed the issue?

Optimizely says it fixed the vulnerability, removed injected code from affected projects, notified affected customers, ended active sessions, revoked tokens and reset access for affected accounts. The company has not publicly explained the vulnerability’s code-level mechanics in the source material.

Source: ThorstenMeyerAI.com

You May Also Like

AI Security Update: What To Do About This Week’s Emerging Issues

A review of six security developments reported Oct. 29, from Fortinet firewall threats to Android banking malware and exposed AI credentials.

How A Routine Cybersecurity Scan Caught A Security Camera Admin Token

A routine cybersecurity scan uncovered a security camera transmitting a GitHub admin token, highlighting emerging device vulnerabilities.

Message Your Other Claude Code Sessions

OpenAI introduces a new feature allowing users to message their other Claude Code sessions for improved workflow and continuity.

Maersk Says Data Theft Involved A Legacy System And $5 Million Demand

Maersk says data was extracted from a local legacy system, but it sees no operational impact. A reported $5 million ransom demand remains unconfirmed.