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

🔍 Read the full analysis: AI Users: How To Check For Malware After The Optimizely Website Attack on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get hardware and tech essentials 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

Optimizely confirmed that an unauthorized party exploited a vulnerability to add malicious JavaScript to some customer projects. Report URI says the code reached visitors of 178 organisations on Nov. 16 and attempted actions including crypto-address swapping and card-data theft; the reported iPhone exploit-kit activity is not evidence that devices were compromised. The code was removed, but the full impact and the vulnerability’s mechanics remain unclear.

Optimizely says an unauthorized party exploited a vulnerability in its Experimentation platform to add malicious JavaScript to some customer projects, exposing visitors to potentially harmful code on November 16. Security researcher Scott Helme’s Report URI analysis says the script was served to visitors of 178 organisations; the company says it fixed the vulnerability and removed the injected code, but the number of people affected and whether any data was stolen are not established in the available reports.

Report URI says it found the code in 188 of 1,611 Optimizely snippets it checked, and that the real total may be higher. The snippets are small JavaScript files that customer websites load to run page experiments. According to the researcher, the attacker inserted code into the projects’ optional Project JavaScript field, while the rest of each snippet remained unchanged. Affected websites were therefore serving a file from a supplier they already trusted.

The payload reportedly attempted several actions, depending on a visitor’s device and activity. Report URI says it could replace cryptocurrency wallet addresses in page text, form fields or the clipboard; monitor card details typed into a site’s own forms; and collect cookies or screenshots. It also directed some iPhones and iPads toward the Coruna and DarkSword exploit kits. Hudson Rock cautioned that its findings show delivery attempts, not demonstrated iPhone compromises.

Report URI observed the first Optimizely injection at 04:21 UTC on November 16 and says the infected files had been cleaned by 23:11 UTC that day, a span of about 19 hours. Optimizely’s status update, posted at 01:02 UTC on November 17, says it fixed the vulnerability and removed code from affected projects. The company also told BleepingComputer it had ended active sessions, revoked tokens, reset access for affected accounts and notified customers it identified as affected.

At a glance
reportWhen: Attack observed November 16, 2026; Opti…
The developmentOptimizely confirmed a vulnerability was exploited to inject malicious JavaScript into some customer projects, while Report URI reported the code was served to visitors of 178 organisations on Nov. 16, 2026.
Crypto market snapshot
Fear & Greed Index
12/100 — Extreme Fear
Bitcoin BTC$63,997▼ 1.6%
Ethereum ETH$1,791▼ 2.2%
Tether USDT$0.9992▼ 0.0%
BNB BNB$587.63▼ 0.6%
USDC USDC$0.9996▼ 0.0%
XRP XRP$0.9627▼ 0.2%
Solana SOL$72.74▲ 1.4%
TRON TRX$0.3071▲ 0.2%
Live data · CoinGecko · alternative.me (24h change)

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 Injected Script Could Affect Visitors

The incident matters because visitors may have encountered malicious code while using familiar websites, even though those sites were not necessarily hacked directly. A trusted third-party script can run in a page’s browser environment, creating a route to attempt to alter what users see or capture information they enter. That makes this a software supply-chain incident, with risk extending across customer sites that use the same service.

There are important limits to what the reporting establishes. The presence of a site or subdomain on Report URI’s list does not show that every page, checkout flow, product or customer was exposed. Hudson Rock specifically warned that an affected subdomain does not establish exposure across an organisation’s entire website or customer base. Report URI also says card numbers entered in hosted payment iframes, such as those used by Stripe or Adyen, were outside the script’s reach; its account says the code could monitor card details entered into a site’s own fields.

For individuals, the practical concern is whether they visited an affected page during the exposure window and entered sensitive information or interacted with a wallet address while the script was active. The supplied reporting does not identify confirmed thefts or prove that a visitor’s device was compromised. For organisations, the findings also highlight that security controls on a customer’s own site may not block code delivered through an already-authorised vendor.

Products Worth Considering

Apple MacBook Pro 16.2-inch with M5 Max, 18-core CPU, 32-core GPU, 36GB Memory, 2TB SSD, Wi-Fi 7, Space Black

Apple MacBook Pro 16.2-inch with M5 Max, 18-core CPU, 32-core GPU, 36GB Memory, 2TB SSD, Wi-Fi 7, Space Black

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)

Apple MacBook Pro 16-inch (2021, M1 Pro, 10-core CPU, 16-core GPU, 16GB RAM, 512GB SSD, Silver)

Apple MacBook Pro 16-inch (2021, M1 Pro, 10-core CPU, 16-core GPU, 16GB RAM, 512GB SSD, Silver)

As an affiliate, we earn on qualifying purchases.

How Optimizely’s Customer Scripts Work

Optimizely Web is used to test different versions of web pages. Each customer site loads a project-specific snippet from the platform, which can include experiments and custom code. Report URI says the attacker wrote JavaScript into the custom-code field for customer projects; the file continued to be delivered from Optimizely’s address, which affected sites already trusted.

Report URI says this was not a content delivery network cache-poisoning attack. It reported that Optimizely’s own websites also carried the code. The published list names 178 organisations, including sites associated with Zoom, the BBC, CNN, HSBC, Salesforce and IKEA. BleepingComputer reported independently confirming that the script loaded or attempted to load on several listed sites using urlscan.io scans. Some entries are individual subdomains or tools, rather than an organisation’s full website.

Report URI also described an earlier wave beginning November 13 involving the same actor’s injector in scripts from Kissmetrics, StorifyMe and Minute Media. Those sites were not included in the Optimizely list. Hudson Rock said how the code entered those three 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 November 17 status-page update

Exposure and Data Theft Remain Unconfirmed

The available reporting does not establish how many individual visitors received the script, how many interacted with the targeted fields, or whether any wallet funds, payment details, cookies or screenshots were successfully taken. Report URI’s figure of 178 organisations describes organisations whose visitors were reportedly served the code, not a count of affected people or confirmed victims.

Optimizely has not publicly detailed the vulnerability’s code-level mechanics in the supplied material, including how an issue in the signup flow permitted writing to multiple customer projects. It is also not clear whether all affected projects and customer sites have been identified. Report URI says its sample may not cover the full number of infected snippets. The separate November 13 activity involving three other providers remains unresolved as well.

The source material advises iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later. It says those releases came out months earlier, but it does not confirm that updating would reverse any exposure from this incident. Nor does the reporting establish that every device that loaded the page was vulnerable to the exploit kits.

Updates, Patches and User Checks

Optimizely says it fixed the vulnerability, removed injected code from affected projects, ended active sessions, revoked tokens, reset access for affected accounts and notified affected customers. The next substantive update would need to clarify how the signup-flow flaw worked, how many customer projects were involved, and what investigation found about possible data theft or device compromise. Customers using the platform should follow direct notices from Optimizely and their own organisations rather than assume that every page or account was affected.

Visitors concerned about exposure can check whether their phone or tablet is running a supported, current operating-system version and install available security updates through the device’s settings. Anyone who entered payment details into a website’s own payment fields during the reported window can contact their card issuer, monitor transactions and follow the issuer’s instructions; this is a precaution, not confirmation that their information was stolen. Crypto users should independently verify wallet addresses before sending funds and avoid relying on an address copied from a page or clipboard without checking it.

People who entered account credentials on a potentially affected page can change those passwords through the service’s official site and enable multifactor authentication where available. These steps reduce ongoing account risk but cannot establish whether data was captured during the incident. The reports do not provide a confirmed victim list or say that any particular user must take a specific remedial action.

Key Questions

What happened in the Optimizely website attack?

Optimizely confirmed that an unauthorized party exploited a vulnerability in its Experimentation platform to add malicious JavaScript to some customer projects. Report URI says visitors to sites run by 178 organisations were served the code on November 16, 2026.

Does being on the affected-site list mean a company’s whole website was compromised?

No. The list includes individual sites and subdomains. Hudson Rock warned that an affected subdomain does not establish that an organisation’s entire website, product, checkout system or customer base was exposed.

Was an iPhone or iPad compromise confirmed?

No confirmed device compromise is established in the supplied reports. Hudson Rock described its findings as evidence of exploit-kit delivery, not demonstrated iPhone compromises. Users should install available operating-system security updates.

What should I do if I entered card details on a potentially affected site?

Monitor the account and contact the card issuer for guidance if you are concerned, particularly if you entered details into a site’s own payment fields during the reported exposure window. The reporting does not confirm that any particular card details were stolen.

Has Optimizely removed the malicious code?

Optimizely says it fixed the vulnerability and removed injected code from affected projects. Report URI says it observed the infected files being cleaned by 23:11 UTC on November 16. The full impact and the flaw’s mechanics remain unclear.

Source: ThorstenMeyerAI.com

Nothing in this article is financial or investment advice. Cryptocurrency and precious-metal investments carry significant risk — do your own research and consider a licensed advisor.
You May Also Like

Europe’s MiCA Regulations Go Live—Key Dates and Immediate Impacts

Navigating Europe’s MiCA regulations’ key dates reveals immediate impacts and future compliance needs that every crypto business must understand to stay ahead.

Bitcoin Up Or Down On September 24?

Market interest in Bitcoin’s direction on September 24 is high, with trending signals and volatility. Confirmed details are limited; full analysis inside.

Will Canada Win On 2026-07-04?

Analysis of Canada’s prospects to win on July 4, 2026, based on current betting markets and expert opinions, with key developments and uncertainties outlined.

XRP Stablecoin Launch: What It Means for the Crypto Market

By launching the RLUSD stablecoin, Ripple could revolutionize crypto liquidity and challenge competitors, but what regulatory hurdles will it face next?