A Simple Guide To Checking AI Accounts After The Optimizely Malware Incident
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: A Simple Guide To Checking AI Accounts After The Optimizely Malware Incident on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get smart everyday buys delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Report URI says malicious JavaScript was served to visitors of 178 organisations through Optimizely Web on November 16, 2026; Optimizely confirmed an attacker exploited a vulnerability to add code to some customer projects. The payload attempted several kinds of data theft, but the sources do not establish that every listed organisation or visitor was compromised. People and businesses should review account activity, update eligible iPhones and iPads, and follow notices from affected organisations.

Malicious JavaScript was delivered to visitors of websites using Optimizely’s experimentation platform on November 16, after an attacker exploited a vulnerability to add code to some customer projects, according to Optimizely and security researcher Scott Helme of Report URI. The incident affected snippets associated with 178 organisations in Report URI’s findings, but a listed organisation does not necessarily mean its entire website or customer base was exposed.

Report URI says it checked 1,611 Optimizely snippets and found malicious code in 188; it identified 178 organisations affected. The researcher says the actual total may be higher. BleepingComputer independently found that the script loaded or attempted to load on sites including Zoom, the BBC, CNN, GitLab, KLM and Salesforce. These counts describe observed snippets and organisations, not confirmed victims or successful theft.

Optimizely’s status page said an unauthorized party exploited a vulnerability in its Experimentation product and added code to some customer projects. The company told BleepingComputer that the weakness was in the account signup flow, and said it had notified affected customers. Optimizely also said it fixed the vulnerability, removed injected code, ended active sessions, revoked tokens and reset access for affected accounts.

Report URI observed the first injection at 04:21 UTC on November 16 and said the infected files had been cleaned by 23:11 UTC, roughly 19 hours later. The malicious code was added to an optional custom JavaScript field in customer projects, according to Report URI; the rest of the Optimizely snippet was unchanged. That meant affected sites continued loading it from a supplier address they already trusted.

At a glance
reportWhen: Incident observed November 16, 2026; Op…
The developmentA vulnerability in Optimizely Experimentation was exploited to inject malicious JavaScript into some customer projects, exposing visitors to harmful code on November 16.

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 Should Check Now

The incident matters because a third-party script can run in the browser on a site that visitors trust, without the site itself being hacked. Depending on the page and visitor activity, the code reportedly tried to replace cryptocurrency wallet addresses, capture payment-card details entered into a site’s own forms, collect cookies and screenshots, and direct some Apple devices toward exploit kits.

Report URI said card details entered into hosted payment frames, such as Stripe or Adyen, were outside the code’s reach; it said card numbers typed into a site’s own form fields were not. This distinction is useful, but does not establish whether any particular visitor’s information was captured. If you visited a site later confirmed to be affected, check for unusual account activity, review payment and wallet transactions, and contact the relevant provider if you find something you did not authorize. Change credentials if an affected organisation advises it or if you have other reason to believe an account was accessed. Avoid following unsolicited links claiming to offer incident support.

For Apple users, Report URI advised updating to iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock cautioned that its iPhone findings were “delivery observations, not demonstrated iPhone compromises.” The evidence supplied does not show that simply visiting an affected page caused every device to be compromised.

Products Worth Considering

Dell XPS 13 13.4-Inch Touchscreen Laptop, Intel Core 5 320, 16GB RAM, 512GB SSD

Dell XPS 13 13.4-Inch Touchscreen Laptop, Intel Core 5 320, 16GB RAM, 512GB SSD

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 Abused

Optimizely Web lets organisations test different versions of web pages. Its customers install a small JavaScript snippet that can load experiments and optional customer-written code called Project JavaScript. Report URI says the attacker wrote code into that field on customer projects, while Optimizely continued to deliver the snippets from its usual address. The researcher said the incident was not a CDN cache-poisoning attack.

Report URI said the payload was rebuilt 26 times during the day and that visitors received the same script, with its actions varying according to device and activity on the page. The published account also described an earlier wave beginning November 13 involving scripts associated with Kissmetrics, StorifyMe and Minute Media. Hudson Rock reported a similar pattern, but said how the code entered those services remains unresolved.

Report URI’s published list spans different sectors, including banking and finance, technology and software, and retail. It counted 32 organisations in banking and finance, 23 in technology and software, and 20 in retail. A name on the list may refer to only one subdomain or service, rather than a company’s main site, checkout system or full customer base.

“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

What the Public Record Does Not Show

The public statements do not explain the signup-flow vulnerability’s code-level mechanics or how it enabled changes across many unrelated projects. Optimizely has said it fixed the flaw and took steps to secure affected accounts, but the source material does not detail how many customers were notified or provide a full account of the attacker’s access.

It is also unclear whether anyone’s data was successfully stolen, whether any payment details or credentials were used, or how many individual visitors encountered the payload. Report URI’s snippet and organisation counts are observations, and it says its total may be incomplete. An organisation’s appearance on the list does not establish that every page, service or customer was exposed. Hudson Rock likewise said its findings did not demonstrate iPhone compromises.

Follow Notices and Review Activity

Optimizely’s published response says the vulnerability has been fixed, the injected code removed, active sessions ended, tokens revoked and access reset for affected accounts. Organisations that used the platform may provide their own guidance to customers or employees. Visitors should follow notices from the specific site or service they used, rather than assume all pages under a listed brand were affected.

People who entered card details into a site’s own payment form during the exposure window can review statements and contact their card issuer about suspicious transactions. Cryptocurrency users should verify wallet addresses through a trusted channel before sending funds and check transaction records for activity they do not recognize. Apple users should install an applicable security update if their device is running an older version. Further clarity depends on technical details from Optimizely and any subsequent reporting about the scope, data access and impact.

Key Questions

What happened in the Optimizely incident?

Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation product to add malicious JavaScript to some customer projects. Report URI says the code was served to visitors through affected Optimizely snippets on November 16, 2026.

Does a listed organisation mean its whole website was affected?

No. Report URI’s list can include a particular site or subdomain. Hudson Rock cautioned that an affected subdomain alone does not establish exposure across an organisation’s full website, products, customer base or checkout system.

What should I do if I visited an affected site?

Check accounts and payment or wallet activity for anything you do not recognize, and follow guidance from the organisation whose site you visited. The available findings do not establish that every visitor’s data was captured or every device was compromised.

Were iPhones confirmed to be compromised?

No. Report URI described code that could direct iPhones and iPads toward exploit kits, while Hudson Rock said its findings were delivery observations, not demonstrated iPhone compromises. Report URI advised eligible users to update to iOS 18.7.3 or later, or iOS 26.3 or later.

Has Optimizely fixed the issue?

Optimizely said it fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens and reset access for affected accounts. The public account does not explain the vulnerability’s technical mechanics or confirm whether data was successfully stolen.

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 Security Risks Of Exposed AI Sessions And Agent Logs

Research describes malware targeting AI-tool sessions, a vendor breach affecting some Warp traces, and a reported fix for an OpenAI reasoning flaw.

Ukraine Strikes Town In Russia That Houses A Federal Tax Service Data Center

Three people were injured in a drone-related incident in Gorodets. A Ukrainian monitoring channel reported that a Federal Tax Service data center was attacked.

How To Check AI Automation Data Practices For Privacy And Compliance

A ThorstenMeyerAI.com checklist recommends reviewing account security, file handling, device privacy and document workflows around AI tools.

PHP2Shell, Check Point Gateways, And The Wiper Malware Threat

Check Point says attackers exploited unpatched gateways, and in some cases used a wiper. CISA set a November 16 deadline for federal agencies.