The 178-Website Malware Incident: Questions AI Users Should Ask
KIDieser Beitrag wurde mit Unterstützung künstlicher Intelligenz (KI) erstellt.

🔍 Read the full analysis: The 178-Website Malware Incident: Questions AI Users Should Ask on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

  • 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 to visitors of 178 organisations on November 16 through Optimizely’s web experimentation platform. Optimizely confirmed an unauthorized party exploited a vulnerability and said it removed the code, but the flaw’s mechanics and the full extent of exposure remain unclear.

Malicious JavaScript was served to visitors of 178 organisations on November 16 through the Optimizely web experimentation platform, 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, turning a trusted third-party script into a possible route for theft and device exploits.

Report URI says it found the malicious code in 188 of 1,611 Optimizely snippets it checked and warned that the total could be higher. It recorded the first affected Optimizely file at 04:21 UTC on November 16; by 23:11 UTC, it said the infected files had been cleaned. That is a roughly 19-hour period in which the code was observed, not proof that every visitor or every page of an affected organisation was exposed.

The payload attempted several actions, according to Report URI: replacing cryptocurrency wallet addresses on pages and in the clipboard, capturing payment-card details entered into a site’s own form fields, collecting cookies and screenshots, and directing some iPhones and iPads toward the Coruna and DarkSword exploit kits. Report URI said the card collection code could not reach card details entered in hosted payment frames such as Stripe or Adyen. Hudson Rock, which examined the iPhone-related activity, cautioned that its findings were delivery observations, not demonstrated device compromises.

Optimizely said it had fixed the vulnerability, removed injected code from affected projects, notified affected customers, ended active sessions, revoked tokens and reset access for affected accounts. BleepingComputer reported that the company identified the flaw as being in the Experimentation account signup flow. Report URI says the attacker inserted code into customer projects’ optional “Project JavaScript” field; the rest of the snippets remained unchanged and continued to load from Optimizely’s trusted address.

At a glance
reportWhen: The reported incident occurred November…
The developmentReport URI documented malicious JavaScript delivered through Optimizely to visitors of 178 organisations, and Optimizely confirmed a vulnerability was exploited.

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

Risks From a Trusted Web Script

The incident shows how a compromise of a service provider can expose visitors across many separate organisations without each organisation’s own website being hacked. Sites intentionally load Optimizely’s snippet to run page experiments; the injected code could then execute in the visitors’ browsers under the conditions available on those pages. That makes the incident relevant not only to the named companies but also to people who visited affected pages during the exposure window.

Report URI’s review also points to uneven site-level protections: it said 24 of 159 organisations it assessed blocked the code through their security policies, while 68 had no policy. Those figures describe the organisations Report URI checked, not all 178, and do not by themselves establish whether an individual visitor was harmed. The researchers have not reported a confirmed count of stolen cards, compromised wallets, or infected devices.

Products Worth Considering

Logitech MX Master 4 Ergonomic Wireless Mouse with Haptics - Graphite

Logitech MX Master 4 Ergonomic Wireless Mouse with Haptics – Graphite

As an affiliate, we earn on qualifying purchases.

How the Optimizely Snippet Was Altered

Optimizely Web provides a JavaScript snippet that customer websites use to run experiments. A project can include custom JavaScript that runs on pages where the snippet is installed. Report URI says the attacker wrote malicious code into that project field, while the surrounding snippet stayed intact. Its analysis ruled out CDN cache poisoning as the explanation.

Report URI’s published list names organisations across several sectors, including Zoom, the BBC, CNN, HSBC sites, Salesforce, IKEA, GitLab, Ledger and UNICEF USA. Its sector count lists banking and finance as the largest group, with 32 organisations, followed by technology and software with 23 and retail with 20. BleepingComputer said it independently confirmed script loading or attempted loading on a number of sites, including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listing may refer to one subdomain or tool; it does not establish that an organisation’s entire website, checkout system or customer base was affected.

Report URI also described an earlier wave beginning November 13, involving scripts associated with Kissmetrics, StorifyMe and Minute Media. Those sites are separate from the 178-organisation Optimizely list. Hudson Rock 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 and Attack Mechanics Remain Open

Neither Optimizely’s statements nor the researchers’ findings explain how the signup-flow vulnerability enabled access to so many unrelated customer projects. Report URI says it does not know how the attacker gained write access at that scale; Hudson Rock says the company’s disclosure does not spell out the bug’s code-level mechanics.

The confirmed scope of downstream harm is also unknown. The available material does not establish how many people saw the code, whether any attempted wallet or card theft succeeded, or whether any iPhone or iPad was compromised. The list of affected organisations is not a measure of the number of affected pages or users, and a named organisation may have had only a specific subdomain exposed. The connection between the Optimizely incident and the earlier activity involving three other providers has not been established.

Customer Reviews and Security Updates

Optimizely says it has removed the code and taken account-access steps, while Report URI says affected files had been cleaned by 23:11 UTC on November 16. The next steps for customers include reviewing Optimizely project code and account access, checking relevant browser and security logs, and following any direct notices from the company. Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later; those versions had been released months earlier, according to the source material.

Further clarity depends on Optimizely explaining how the vulnerability worked and what customer projects and accounts were affected. Customers and users should distinguish that incident response from evidence of actual data theft or device compromise, which has not been established in the reporting available here.

Key Questions

What happened in the 178-website incident?

Report URI says malicious JavaScript was delivered to visitors of 178 organisations through Optimizely’s web experimentation platform on November 16, 2026. Optimizely confirmed an unauthorized party exploited a vulnerability to add code to some customer projects.

What was the malicious code designed to do?

Report URI says the code attempted to replace cryptocurrency wallet addresses, collect card details typed into some sites’ own forms, capture cookies and screenshots, and direct some Apple devices to exploit kits. These reported capabilities do not establish that each action succeeded.

Were all pages or customers of the named organisations affected?

No such broad exposure is established. The list can include an individual subdomain or service, and researchers cautioned that a listed subdomain does not prove exposure across an organisation’s whole website, products or customer base.

Is there evidence that users’ devices or payment details were stolen?

The source material does not provide a confirmed count of stolen payment details, compromised wallets or infected devices. Hudson Rock specifically described its iPhone findings as evidence of delivery, not demonstrated compromise.

What should visitors do now?

Report URI advised iPhone and iPad users to install iOS 18.7.3 or later, or iOS 26.3 or later. Visitors concerned about a particular account or payment should follow guidance from the relevant organisation; the reporting does not identify a confirmed list of affected individuals.

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

The Two-Day PHP2Shell Chain Behind Palo Alto Server Compromises

Dream reports that an attacker chained PHP2Shell and a Linux kernel flaw to gain root access on 24 PAN-OS firewalls and a network server.

How 10 Best Mesh Wi-Fi Systems Can Help Cover Your Home In 2027

A 10-system comparison weighs Wi-Fi generation, backhaul, kit size and setup, while noting why coverage claims are not guarantees.

11 Hubs To Help Bring AI To Your Connected Home In 2027

A buyer’s guide to 11 smart-home hubs, comparing protocols, local control, camera features and setup demands. Check device compatibility before buying.

The 90-Day Window Closed. Nobody Sent a Notice.

The 90-day window for responsible vulnerability disclosure has effectively ended without any notice from vendors or researchers, raising concerns about security practices.