AI Users, Check These Things After Malware Hit 178 Major Websites
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: AI Users, Check These Things After Malware Hit 178 Major Websites on ThorstenMeyerAI.com

Age 18–24?Offer from Amazon

Prime made for students and young adults

  • Fast, free delivery for dorm and study essentials
  • Prime Video and Amazon Music included
  • Member-only deals
Try Prime for Young Adults Free trial for eligible 18–24 year olds
As an affiliate, we earn on qualifying purchases.

TL;DR

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 attacker exploited a vulnerability to add code to some customer projects and says it fixed the flaw and removed the code. The code’s attempted actions are documented, but there is no confirmation here that visitors’ devices or accounts were successfully compromised.

Malicious JavaScript was served to visitors of 178 organisations through Optimizely’s web experimentation platform on November 16, according to security researcher Scott Helme of Report URI. Optimizely confirmed that an unauthorised party exploited a vulnerability to add code to some customer projects; the incident matters because visitors encountered it through scripts the affected sites had deliberately loaded from a supplier.

Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188 snippets, associated with 178 organisations. It said the actual number could be higher. BleepingComputer separately reported confirming through urlscan.io scans that the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A name on the list does not establish that an organisation’s entire website or every page was affected.

The injected script was placed in an optional Optimizely feature called Project JavaScript, according to Report URI. The feature lets customers add code that runs on their pages. Report URI said the remainder of each affected snippet was unchanged, and that the script was still delivered from an Optimizely address already trusted by the customer site. It said this was not a content delivery network cache-poisoning attack.

Report URI’s analysis says the code attempted to replace cryptocurrency wallet addresses in page content and the clipboard, collect payment card details typed into a site’s own form fields, capture cookies and screenshots, and direct some iPhones and iPads to exploit kits called Coruna and DarkSword. It said cards entered in hosted payment iframes, such as those used by Stripe or Adyen, were outside the script’s reach. These are reported capabilities and attempted actions, not proof that each action succeeded or that every visitor was affected.

At a glance
reportWhen: Attack observed November 16, 2026; Opti…
The developmentReport URI found malicious JavaScript served through Optimizely to visitors of 178 organisations, and Optimizely confirmed an attacker exploited a vulnerability to inject code into 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

Risk From a Trusted Web Script

The incident shows how a compromise of a third-party web service can expose visitors across many unrelated organisations without attackers having to break into each organisation’s own systems. A small script used to run website experiments can execute in a visitor’s browser with access to the page it is loaded on. That can put information entered into the page at risk, depending on the code and the page’s design.

For users, the practical concern is not simply that a listed brand’s name appears in a report. Exposure depended on whether a visitor opened an affected page while the code was active, what they did there, and what device they used. Report URI’s account describes attempted collection and redirection; the supplied findings do not confirm successful theft of card data, cookies, cryptocurrency or device access. Hudson Rock specifically described its iPhone findings as delivery observations, not demonstrated iPhone compromises.

The event also raises questions for organisations about how they control scripts supplied by vendors. Report URI checked security policies on affected organisations’ sites and said 24 of 159 blocked the code, while 68 had no policy. Those figures describe its checks of the sites and policies it examined; they do not establish the outcome for every affected organisation.

KitchenAid Commercial Series 8-Quart Bowl-Lift Stand Mixer, White

KitchenAid Commercial Series 8-Quart Bowl-Lift Stand Mixer, White

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Roborock Q10 S5+ Robot Vacuum and Mop with Self-Emptying Station

Roborock Q10 S5+ Robot Vacuum and Mop with Self-Emptying Station

As an affiliate, we earn on qualifying purchases.

How the Optimizely Injection Worked

Optimizely Web allows companies to test versions of web pages. Customer sites load a small JavaScript snippet from the platform, which can carry experiment settings and customer-added code. Report URI says the attacker inserted code into the Project JavaScript field of customer projects, while the snippets continued to be served from a source the sites already trusted. That delivery path helps explain why visitors could receive the code through legitimate-looking pages.

Report URI observed the first injection at 04:21 UTC on November 16 and said all infected Optimizely files had been cleaned by 23:11 UTC, an interval of about 19 hours. Optimizely’s status-page entry, posted at 01:02 UTC on November 17, 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 and reset access for affected user accounts.

Report URI says the same actor’s injector had appeared from November 13 in scripts associated with Kissmetrics, StorifyMe and Minute Media, on sites outside its list of 178. The available material does not establish how the code entered those services or whether those incidents shared the same access route as the Optimizely compromise.

“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

Scope and Successful Data Theft

The available reports do not establish how many visitors received the code, whether anyone’s card details, cookies or wallet addresses were successfully stolen, or whether any device was compromised. Report URI says the payload changed during the day, but the provided material does not quantify which visitors received each version or how many people encountered affected pages.

Optimizely has not publicly explained, in the cited statements, the code-level mechanics of the signup-flow vulnerability or how it enabled changes to multiple customers’ projects. The total number of affected sites may also be higher than the 178 organisations identified by Report URI. An affected subdomain is not evidence that an organisation’s other sites, products, checkout pages or customers were exposed.

The reports also do not resolve how the related injector appeared in scripts from three other providers beginning November 13, or whether those cases were connected through the same technical weakness or actor access. These limits matter when interpreting lists of affected brands: a listed organisation is not, by itself, proof of broad exposure or confirmed harm.

Customer Checks and Further Findings

Optimizely says it has fixed the vulnerability, removed injected code from affected projects, notified affected customers, ended active sessions, revoked tokens and reset access for affected accounts. The cited material does not give a date for a fuller technical account or describe any continuing investigation milestones. Further detail from Optimizely or independent researchers could clarify how the flaw was used and how many visitors were exposed.

Report URI advises iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. For people who visited a potentially affected page during the reported window, the available reporting supports caution rather than assuming a compromise: watch for unusual account activity and contact a bank or service provider if there is evidence of unauthorised transactions or access. Organisations named in the report can check the specific subdomains and pages listed, review their own incident notices and ask their web-service providers what was affected.

Further reporting will need to distinguish code delivery from confirmed impact. The key open questions are whether investigators can document successful theft or device compromise, whether the affected customer-project count changes, and how Optimizely’s vulnerability allowed the attacker to write code to those projects.

Key Questions

What happened to the 178 organisations?

Report URI says malicious JavaScript was served to visitors of 178 organisations through Optimizely on November 16, 2026. Optimizely confirmed an attacker exploited a vulnerability to add code to some customer projects. The list does not mean every page or service belonging to those organisations was affected.

Does the report prove that visitors’ data was stolen?

No. Report URI described code that attempted to collect certain information and redirect some devices to exploit kits. The source material does not confirm successful theft of card details, cookies or cryptocurrency, or successful iPhone compromises.

What should iPhone and iPad users do?

Report URI advises updating to iOS 18.7.3 or later, or iOS 26.3 or later. The reporting describes exploit-kit delivery attempts but does not establish that every device exposed to the script was compromised.

Was every page of a listed company affected?

No such conclusion follows from the list. Some entries were individual subdomains or tools. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organisation’s entire website, products, customer base or checkout system.

What has Optimizely said it did?

Optimizely said it fixed the vulnerability, removed injected code from affected projects and notified affected customers. It also told BleepingComputer it ended active sessions, revoked tokens and reset access for affected user accounts. The cited statements do not explain the vulnerability’s code-level mechanics.

Source: ThorstenMeyerAI.com

You May Also Like

AI’s Achilles’ Heel: Cross-Domain Cyber Threats

Experts warn that multi-domain cyber attacks threaten global security by creating cascading effects, ambiguity, and political instability, challenging defenses.

The Chainalysis Breach From First Update To Password Hashes And Live Tokens

Chainalysis said password hashes and live tokens for all users were exposed, revising its initial account of an October intrusion.

Can 72-Hour Drills Help Put A16z’s AI Defense Plan Into Practice?

Andreessen Horowitz’s proposed AI-era cyber plan calls for 72-hour manual-operation drills and measurable security targets across five sectors.

The Frameworks Can’t See the Thing That Matters: A Year of AI-Enabled Cyber Threats

A new report reveals AI’s role in making cyber attackers more dangerous and challenges traditional threat assessment methods. Key insights from a year of malicious activity analysis.