AI Tools And The Optimizely Malware Incident: What Users Should Review
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: AI Tools And The Optimizely Malware Incident: What Users Should Review on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

  • 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

Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation account signup flow and inserted malicious JavaScript into some customer projects. Report URI says the code reached visitors of 178 organisations on November 16 and was removed by 23:11 UTC; the exact route to write access, the number of affected visitors and whether devices or data were compromised remain unclear.

Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation platform and added malicious JavaScript to some customer projects. Security researcher Scott Helme of Report URI says the code was served to visitors of sites associated with 178 organisations on November 16, making this a supply-chain incident involving a script those sites had intentionally loaded.

Report URI says it checked 1,611 Optimizely snippets and found the malicious code in 188. The researcher identified the affected snippets with 178 organisations; the tally is not a count of every affected page, user or company system. Report URI says the true number may be higher. BleepingComputer separately reported that urlscan.io scans showed the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce.

The injected JavaScript was placed in an optional Optimizely field called Project JavaScript, according to Report URI. Customer sites load their own Optimizely snippets, which can include this custom code. Report URI says the attacker changed that field while leaving the rest of each snippet untouched; the script continued to arrive from an address the affected sites already trusted. The researcher said the incident was not a CDN cache-poisoning attack.

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

Report URI’s analysis says the code attempted several actions, including replacing cryptocurrency wallet addresses in page content or clipboard use, capturing payment-card details entered into sites’ own form fields, and collecting cookies and screenshots. It also attempted to direct some iPhones and iPads to the Coruna and DarkSword exploit kits. Hudson Rock cautioned that its iPhone findings describe delivery observations, not demonstrated device compromises. Report URI said card details entered in hosted payment iframes such as Stripe or Adyen were outside the code’s reach.

At a glance
updateWhen: Incident observed November 16, 2026; Op…
The developmentOptimizely confirmed an attacker exploited a vulnerability to add malicious JavaScript to customer projects, with Report URI identifying the code on sites associated with 178 organisations.

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 change at a third-party provider can expose visitors to malicious code even when the organisations whose sites they visit have not themselves been hacked. Optimizely’s script was already trusted by customer websites, so the injected code could be delivered through an expected page component. This makes the event relevant to both website operators reviewing vendor access and users who visited affected pages during the incident window.

The potential impact depends on the page, device and user activity. Report URI describes attempted wallet-address substitution, form-field card skimming and collection of cookies or screenshots; these are findings about the code’s behaviour, not proof that a particular visitor lost funds or had an account accessed. Hudson Rock’s warning likewise distinguishes exploit delivery from a confirmed iPhone compromise. The available material does not establish how many people encountered the code or suffered harm.

For organisations, the incident also puts attention on safeguards that can limit third-party scripts. Report URI says it checked security policies at affected organisations and found that 24 of 159 blocked the code, while 68 had no policy. These figures describe the organisations it checked, not every affected site. The findings suggest that controls such as restrictive content security policies may affect whether an injected script can run, but they do not establish what any one organisation’s other protections did during this event.

De'Longhi Stilosa Compact Manual Espresso Machine with Manual Milk Frother

De'Longhi Stilosa Compact Manual Espresso Machine with Manual Milk Frother

Breville Barista Pro Espresso Machine with Grinder, Brushed Stainless Steel

Breville Barista Pro Espresso Machine with Grinder, Brushed Stainless Steel

As an affiliate, we earn on qualifying purchases.

How Optimizely Code Reached Sites

Optimizely Web is used to test different versions of web pages. A customer site loads a small JavaScript snippet from the platform; the snippet can carry experiments and customer-written code in the Project JavaScript field. Because that code runs on pages that include the snippet, an attacker able to alter customer projects could affect visitors without separately compromising each listed organisation’s infrastructure.

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 the 178-organisation Optimizely list. Hudson Rock found a similar pattern but said how the code entered those services remained unresolved. This earlier activity is separate from Optimizely’s confirmed account of a vulnerability in its own Experimentation signup flow.

Report URI published affected names by sector: banking and finance led with 32 organisations, followed by technology and software with 23 and retail with 20. A name on the list does not mean an entire company website or service was affected. Hudson Rock specifically cautioned that an affected subdomain does not establish exposure across an organisation’s full website, products, customer base or checkout system.

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

What the Investigation Has Not Established

Optimizely has not publicly explained the technical mechanics of the signup-flow vulnerability or how it gave the attacker write access to multiple customer projects. Hudson Rock says the company’s disclosure does not detail the bug at code level. The available statements also do not establish who carried out the activity or whether the earlier injections involving three other providers were connected through the same access method.

The number of people who saw the code, the number who interacted with it and any resulting theft or device compromise have not been established in the source material. Report URI’s count covers snippets it checked, and its estimate that the actual number may be higher is not a confirmed total. Nor does a listing for a particular organisation establish that all its pages, services or customers were exposed.

Report URI advised iPhone users to update to iOS 18.7.3 or later, or iOS 26.3 or later, and said those versions had been released months earlier by Apple. The source material does not show how many visitors were running vulnerable software or whether any exploit attempt succeeded. Hudson Rock’s account expressly stops short of claiming confirmed iPhone infections.

Follow-Up for Sites and Visitors

Optimizely says it has fixed the vulnerability, removed injected code, ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers. Businesses using the platform should review Optimizely’s notices and their own project configuration, confirm whether their snippets were among those identified, and check site and security logs for activity during the reported November 16 window. They can also review third-party script permissions and content security policies as part of their incident response.

Visitors who used an affected site during the period should apply Apple’s recommended software updates if they use an iPhone or iPad. Those who entered payment details into a site’s own form or copied a wallet address while an affected page was open may wish to check relevant account or transaction activity and contact their provider if they see suspicious activity. These steps are precautionary; the source material does not confirm that a particular visitor’s information was taken.

Further clarity depends on Optimizely and investigators providing more detail about the flaw, access to customer projects and any verified impact. Organisations should also distinguish a listed affected subdomain from confirmed exposure of an entire service. The scope of visitor exposure, any successful compromises and the relationship to the earlier provider incidents remain open questions.

Key Questions

What happened in the Optimizely incident?

Optimizely said an unauthorized party exploited a vulnerability in its Experimentation signup flow to add malicious JavaScript to some customer projects. Report URI found the code in 188 snippets associated with 178 organisations and says it was served to visitors on November 16, 2026.

Does a listed organisation’s entire website mean it was affected?

No. The reported list includes specific sites and subdomains. Hudson Rock cautioned that exposure of an affected subdomain does not establish exposure across an organisation’s whole website, products, customer base or checkout system.

What did the malicious code attempt to do?

Report URI says it attempted to replace cryptocurrency wallet addresses, capture card details entered into a site’s own forms, collect cookies and screenshots, and direct some Apple devices to exploit kits. These reported behaviours do not prove that a visitor’s data was stolen or a device compromised.

What should visitors do now?

Apply the iOS updates cited by Report URI if you use an iPhone or iPad. If you entered card details in a site’s own form or copied a wallet address while visiting an affected page during the incident, check for suspicious activity and contact the relevant provider if needed. These are precautionary steps; confirmed individual losses have not been reported in the supplied material.

What remains unknown?

Optimizely has not publicly explained how the signup-flow flaw enabled changes to multiple customer projects. The available reporting also does not establish the number of exposed visitors, whether any data was successfully taken, or whether an iPhone or iPad was successfully compromised.

Source: ThorstenMeyerAI.com

You May Also Like

PeerTube Is A Free, Decentralized And Federated Video Platform

PeerTube is now available as a free, decentralized, and federated video platform, offering an alternative to centralized services like YouTube.

AnySpeechRecognizer And AnyDecisionModel Put Open Models On Apple

AnySpeechRecognizer and AnyDecisionModel give Swift developers shared APIs for speech and structured decisions using models that can run on device.

Meta Reuses Old RAM In New Servers With Custom Bridge Chip

Meta integrates recycled RAM modules into new servers using a custom-designed bridge chip to improve efficiency and reduce costs.

Notion Reports AI Transcript Exposure After Fireworks Breach

Notion says attackers accessed AI chat transcripts in a Fireworks dataset and revoked exposed API keys. Fewer than 1% of workspaces are affected.