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

🔍 Read the full analysis: What Should AI Users Do After Malware Hit 178 Websites? 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

Security researcher Scott Helme of Report URI says malicious JavaScript was served through Optimizely to visitors of 178 organisations on November 16, 2026. Optimizely says it fixed a vulnerability and removed the code; visitors should update iPhones and iPads, avoid using crypto addresses copied from affected pages, and contact their bank if they entered card details into a site’s own form. The available findings do not establish that every listed organisation or visitor was 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 said an unauthorized party exploited a vulnerability to add code to some customer projects; the incident put visitors at risk of credential, payment and cryptocurrency theft, but does not establish that every visitor or listed organisation was compromised.

Report URI says it found the script in 188 of 1,611 Optimizely snippets it checked, and believes the actual number may be higher. The first injection it observed was at 04:21 UTC on November 16. By 23:11 UTC, Report URI says, the infected Optimizely files had been cleaned. The company’s status page, updated November 17, said it had fixed the vulnerability and removed injected code from affected projects.

According to Report URI’s analysis, the code attempted to replace cryptocurrency wallet addresses in page content and clipboard data, capture card details entered into a site’s own form fields, and collect cookies and screenshots. It also directed some iPhones and iPads toward the Coruna and DarkSword exploit kits. The script’s behavior depended on the device and visitor activity. Report URI says the payload was rebuilt 26 times during the day; that count describes script revisions, not confirmed infections.

The delivery mechanism matters: customer websites loaded Optimizely snippets they had already chosen to trust. Report URI says the attacker inserted code into the Project JavaScript field of customer projects while leaving the rest of each snippet unchanged. It says the incident was not a CDN cache-poisoning attack. Optimizely told BleepingComputer that it had ended active sessions, revoked tokens and reset access for affected accounts, and had notified affected customers.

At a glance
reportWhen: The reported activity occurred November…
The developmentReport URI reported that malicious JavaScript reached visitors to 178 organisations through Optimizely Web on November 16, and Optimizely confirmed an attacker exploited a vulnerability to add code to 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

What Visitors Should Do Now

The incident shows how a compromise at a third-party service can expose visitors across many separate websites without those sites themselves being hacked. A trusted script can run in a page visitors already know, making malicious changes difficult to spot. The reported list spans finance, technology and retail, but a listed organisation is not proof that its entire website, checkout system or customer base was affected.

Visitors who used an affected page should take precautions based on what they did there, rather than assume their device or account was compromised. Report URI advises iPhone and iPad users to install iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock, which examined the mobile delivery stage, cautions that its findings show delivery attempts, not demonstrated iPhone compromises.

Anyone who copied a cryptocurrency address while an affected page was open should verify the destination independently before sending funds; Report URI says the script could also alter clipboard contents. If someone entered payment-card details into a site’s own form during the exposure window, they can contact the card issuer, monitor transactions and follow its guidance. Report URI says card details entered into hosted payment frames such as Stripe or Adyen were outside the script’s reach. Users should also be alert to unusual account activity and use official channels to change credentials if they have reason to believe those credentials were exposed.

Report URI’s review found that 24 of 159 organisations it assessed blocked the code with their security policies, while 68 had no policy. This is a measure of site defenses in its review, not a count of compromised organisations or visitors.

De'Longhi Magnifica Duo Fully Automatic Espresso Machine with Milk Frother, Silver

De'Longhi Magnifica Duo Fully Automatic Espresso Machine with Milk Frother, Silver

As an affiliate, we earn on qualifying purchases.

How the Optimizely Script Was Altered

Optimizely Web lets businesses run experiments on their websites using a small JavaScript snippet. Each customer’s snippet can include experiments and an optional Project JavaScript field for custom code that runs on pages using the snippet. Report URI says the attacker wrote malicious code into that field in customer projects, so visitors received it from an address their sites already trusted.

Report URI published a list of 178 organisations, including sites associated with Zoom, the BBC, CNN, HSBC, Salesforce, IKEA, GitLab and UNICEF USA. BleepingComputer said it independently confirmed that the script loaded or attempted to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. The list includes individual domains and subdomains: an affected subdomain does not establish that a company’s entire website or services were exposed.

Report URI also described an earlier wave beginning November 13, involving scripts from Kissmetrics, StorifyMe and Minute Media on sites not included in the 178-organisation list. Hudson Rock reported the same pattern and said how the code entered those services remained 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 Scope and Attack Path

Important details remain unresolved. Optimizely has not publicly explained how a vulnerability in its signup flow enabled the attacker to write to multiple unrelated customer projects. Report URI says it does not know how the attacker obtained that access, and Hudson Rock says the disclosure does not explain the bug’s code-level mechanics.

The 178 figure refers to organisations identified by Report URI, not a verified count of people whose data was stolen. Its review found the code in 188 of 1,611 snippets, and the researcher said the real number may be higher, but the comparison does not establish how many visitors encountered the script. Nor is there confirmation in the source material that every attempted action succeeded. Hudson Rock specifically says its iPhone findings do not demonstrate device compromises. The extent of any stolen payment information, cookies, screenshots or cryptocurrency remains unclear.

Customer Notifications and Security Review

Optimizely says it has fixed the vulnerability, removed injected code, notified affected customers, ended active sessions, revoked tokens and reset access for affected user accounts. Customers using Optimizely Web can review the company’s incident notices, check their project custom code and site logs for activity during the reported period, and follow any instructions Optimizely provides. The source material does not give a further public investigation deadline or a confirmed total of affected visitors.

For individual users, the immediate steps are to update Apple devices to the versions cited by Report URI, avoid relying on wallet addresses copied from a page that may have loaded the script, and contact a card issuer if card details were entered into a site’s own payment form. Whether additional technical findings or verified evidence of data theft will be released remains to be seen.

Key Questions

Were all 178 organisations fully compromised?

No. Report URI identified 178 organisations whose sites were affected by the script, but a listed site or subdomain does not show that every page, product, checkout system or customer was exposed.

Does the report confirm that iPhones were infected?

No. The script directed some iPhones and iPads toward exploit kits, but Hudson Rock described its findings as delivery observations, not demonstrated device compromises.

What should I do if I copied a crypto address from a potentially affected page?

Check the destination address independently before sending funds. Report URI says the code could replace wallet addresses in page content and clipboard data, including while the affected tab was open.

Should I replace my payment card?

The source material does not recommend that every visitor replace a card. If you entered card details into a site’s own form during the exposure period, contact your card issuer, monitor transactions and follow its advice. Report URI says hosted payment frames such as Stripe or Adyen were outside the script’s reach.

How did Optimizely respond?

Optimizely said it fixed the vulnerability, removed injected code from affected projects, notified affected customers, 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

Key AI Developments In 2026: 9 Trends To Follow

Explore the nine key AI trends shaping 2026, from advancements in generative models to ethical frameworks, and understand their implications for the future.

Preparing AI Agents For Business Means Testing The Hard Days

Firmulate’s July 2026 model league found gaps in deal execution and rule-following, and its enterprise pilot offers read-only company-data tests.

SenseTime’s Milestone Year: First H1 Profit And Revenue Growth In AI Sector

SenseTime achieves its first-ever first-half profit alongside a 23.4% revenue increase, signaling potential financial improvement in AI sector.

Why GitHub’s AI Pull Request Numbers Put Review In The Conversation

GitHub says agents started more than 40% of September pull requests. Its figures and new review tools highlight costs, oversight and open questions.