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

🔍 Read the full analysis: How The 178-Site Malware Incident Could Matter To AI Users 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 served to visitors of 178 organisations on November 16 through scripts hosted by Optimizely’s Web experimentation platform. Optimizely confirmed an attacker exploited a vulnerability to add code to some customer projects; what data, if any, was stolen or which visitors were affected has not been established.

Malicious JavaScript was served to visitors of websites operated by 178 organisations through Optimizely’s Web experimentation platform on November 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 people using affected sites—including AI users who may visit them or enter sensitive information.

Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188. The researcher’s report describes 178 organisations whose visitors received the code; it says the true number may be higher. BleepingComputer independently found evidence that the script loaded or attempted to load on sites including those of Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A listed organisation does not mean its entire website, product or customer base was affected.

The injected script could perform different actions depending on a visitor’s device and activity. Report URI says it attempted to replace cryptocurrency wallet addresses in page content, form fields and the clipboard; capture payment-card details entered into a site’s own fields; and collect cookies and screenshots. It also directed some iPhones and iPads toward the Coruna and DarkSword exploit kits. Hudson Rock cautioned that its findings about the iPhone stage were delivery observations, not evidence of successful device compromises.

Report URI observed the first Optimizely injection at 04:21 UTC on November 16 and says infected files had been cleaned by 23:11 UTC, a span of about 19 hours. Optimizely said it fixed the vulnerability and removed the injected code from affected projects. It also told BleepingComputer it had ended active sessions, revoked tokens and reset access for affected user accounts.

At a glance
reportWhen: The activity was observed November 16,…
The developmentA security researcher reported malicious code on Optimizely scripts used by 178 organisations, and Optimizely confirmed an attacker had exploited a vulnerability to alter 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 the Incident Reaches AI Users

The reported incident matters to AI users because it shows how a compromise of a third-party web service can expose visitors without attackers having to breach each website individually. Optimizely’s script was already trusted and loaded by customer sites. An AI company’s website, sign-in page or other online service could face similar risks if it relies on compromised external code; the source material does not say that any AI service was affected in this incident.

For people using AI tools, the potential consequences depend on what a particular page contained and what the visitor did while the code was active. The reported code sought information such as cookies and card details typed into the site’s own forms. That is different from proof that an account was taken over, a card was charged or an AI conversation was accessed. No confirmed count of stolen data or affected individuals is provided in the source material.

The event also points to a practical limit of site-by-site security controls: a company may secure its own systems but still inherit risk from a supplier’s code. Report URI found that only 24 of 159 assessed organisations blocked the code using their security policies, while 68 had no policy. Those figures concern the organisations and policies the researcher checked, not all 178 listed organisations or every website.

Products Worth Considering

LG Smart Monitor Swing 32U889SA-W 32-Inch 4K UHD IPS Touchscreen on Fully Adjustable Wheeled Base, HDR10, webOS, Built-in Speakers, HDMI, US

LG Smart Monitor Swing 32U889SA-W 32-Inch 4K UHD IPS Touchscreen on Fully Adjustable Wheeled Base, HDR10, webOS, Built-in Speakers, HDMI, US

As an affiliate, we earn on qualifying purchases.

How Optimizely’s Script Was Altered

Optimizely Web lets businesses test different versions of pages using a small JavaScript snippet loaded by each customer site. The snippet can include Project JavaScript, a field for customer-created code that runs on pages where the service is installed. Report URI says the attacker inserted malicious code into that field while leaving the rest of each snippet unchanged. The files were still delivered from an Optimizely address already trusted by the affected sites.

Report URI says this was not a content delivery network cache-poisoning attack. Optimizely’s November 17 status update said an unauthorized party exploited a vulnerability and added code to some customer projects. The company told BleepingComputer the flaw was in the Experimentation account signup flow. The available statements do not explain the technical steps that connected that flaw to write access across separate customer projects.

Report URI also described an earlier wave beginning November 13, when the same actor’s injector appeared in scripts associated with Kissmetrics, StorifyMe and Minute Media. Those sites were not part of the 178-organisation list. Hudson Rock said how the code entered those services remained unresolved. The earlier activity suggests the Optimizely incident was not the only reported use of this injector, but the source material does not establish a connection between the providers’ security weaknesses.

“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 November 17

The Scope of Exposure Is Unresolved

The available reports do not establish how many people received or interacted with the code, whether data was successfully taken, or whether any devices were compromised. Report URI says the script was rebuilt 26 times during the day, but that count does not provide a number of affected visitors or a comparison baseline. The code’s presence on a site also does not show that every visitor saw every action it contained.

Optimizely has not publicly detailed how the signup-flow vulnerability allowed access to unrelated customer projects, according to the cited statements. The source material also does not identify the attacker or provide a confirmed account of the data, if any, that was exfiltrated. Hudson Rock’s analysis specifically cautions that evidence of exploit-kit delivery is not evidence of a successful iPhone compromise.

Updates and Visitor Precautions

Optimizely says it has fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens and reset access for affected users. Report URI says the infected Optimizely files it observed were cleaned by 23:11 UTC on November 16. The source material does not provide a further investigation timetable or say whether Optimizely will publish a technical postmortem.

Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later, versions it says Apple released months earlier. The supplied information does not say that an update alone would address every possible exposure from the incident. Businesses and visitors will need to rely on further findings from Optimizely, affected organisations and security researchers to clarify the incident’s reach and whether any data was taken.

Key Questions

What happened in the 178-site malware incident?

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

Were AI companies or AI accounts confirmed to be affected?

The source material does not identify an AI service or confirm that AI accounts or conversations were accessed. The incident is relevant to AI users as an example of the risks created when websites rely on third-party scripts, not as evidence that a specific AI provider was compromised.

Does being on the affected list mean a whole company website was exposed?

No. Some entries were specific subdomains or tools. Hudson Rock cautioned that an affected subdomain does not prove exposure across an organisation’s entire website, product or customer base.

Is there evidence that iPhones were successfully hacked?

Hudson Rock said its findings showed delivery observations, not demonstrated iPhone compromises. Report URI recommended updating affected Apple devices, but the cited material does not confirm successful device infections.

What has Optimizely done so far?

Optimizely said it fixed the vulnerability and removed injected code from affected projects. It also told BleepingComputer it had ended active sessions, revoked tokens and reset access for affected user accounts.

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

Mythos 5 Post-Mortems: Questions For Anyone Building AI Agents

Anthropic and the UK AI Security Institute detail how Mythos 5 targeted real developers during a cyber test and why it kept going.

Zero-Image Data Rendering In AI: The Vortex Field Unit’s Method

The Vortex Field Unit’s new method uses procedural graphics to visualize supercell storms without external images, marking a breakthrough in AI-driven weather data display.

The Multi-Faceted Impact Of Cross-Domain Attacks On AI Systems

Exploring how cross-domain attacks threaten AI systems through cascading effects, attribution ambiguity, and political impact, and why timely detection is critical.

Empower Your Student Organization With AI Technology

Discover how AI-powered tools are transforming student organization management, enhancing productivity, and streamlining coordination for student groups.