Skip to main content
Threat Intelligence · November 17, 2026

Optimizely Script Attack: What MSPs Should Check Now

Optimizely confirmed that an attacker exploited a flaw in its Experimentation product to add malicious JavaScript to some customer projects. Here is what MSPs and web teams should check on every client site that loads the snippet.

Vijilan Incident Desk· 6 min read
Short answer

Optimizely confirmed on 17 November 2026 that "an unauthorized party exploited a vulnerability in Experimentation" and used it "to add malicious JavaScript to some customer projects" [1]. It says it has fixed the vulnerability, removed the injected code from affected projects and secured affected user accounts [1]. The code reached visitors through each customer's own Optimizely Web snippet, so the sites looked normal and the script came from a trusted domain. If you or your clients run Optimizely Web, check every project now and treat 16 November as a possible exposure window for anything typed into those sites' own forms.

What Optimizely confirmed

Optimizely posted the incident on its status page at 01:02 UTC on 17 November 2026, under Web Experimentation (Snippet Delivery) [1]:

  • An unauthorized party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects.
  • Optimizely fixed the vulnerability and removed the injected code from affected projects.
  • It took steps to secure affected user accounts and added protections against unauthorized code being delivered.

Optimizely has not said how many customers were affected, how the vulnerability worked, or when the attacker first gained access [1]. No threat actor has been named.

What researchers found

Report URI, which detected the campaign, published its analysis on 16 November 2026 and updated it on 17 November [2]. These are the researcher's findings, not Optimizely's:

  • It checked 1,611 Optimizely snippets and found 188 carrying the malicious code, belonging to 178 organisations. It says the true number is likely higher. Banking and finance was the largest sector [2][3].
  • The code was written into the "Project JavaScript" field of customer projects and first appeared at 04:21 UTC on 16 November. All infected files it was tracking were clean by 23:11 UTC the same day [2].
  • The payload swapped cryptocurrency wallet addresses, skimmed card details from forms on the page, sent non-HttpOnly cookies and screenshots to the attacker, and on older iPhones and iPads tried to load browser exploits [2].
  • Researchers also traced the same injection code to three other third-party scripts (Kissmetrics, StorifyMe and minute-ly) between 13 and 16 November [3].

Why this matters to MSPs

Most MSPs do not run Optimizely themselves, but many manage or host websites for clients that do, and every client site loads third-party JavaScript it does not control. This attack changed nothing on the victims' own servers. A vendor-side flaw was enough to put a card skimmer on a bank's login or checkout page. Allowlisting the vendor's domain gave no protection, because the code came from that domain [2][3].

What to do now

  1. Find every client site that loads Optimizely Web. Search page source for cdn.optimizely.com or a self-hosted copy of the snippet.
  2. Inspect each project. Review the Project JavaScript field and every experiment's custom code for anything nobody on the team wrote, including references to the domain 1688360.cc or calls to atob( [2].
  3. Review access to the Optimizely account. List users, API tokens and integrations, remove what is not needed, and rotate credentials [2].
  4. Treat 16 November as an exposure window. Card details typed into a site's own forms (not a hosted payment page) and sessions held in non-HttpOnly cookies may have been taken. Rotate those sessions and decide with the client whether customers need to be told [2].
  5. Block the attacker's infrastructure. Add 1688360.cc, webshell.lol and the other domains Report URI lists to DNS and web filtering [2].
  6. Tighten Content Security Policy. Start in report-only mode, restrict connect-src, and avoid unsafe-eval. Report URI found the few affected sites with a strict policy blocked most of the payload [2].
  7. Update Apple devices. Users who browsed affected sites on 16 November should be on a current iOS or iPadOS release [2].

Frequently asked questions

What did Optimizely confirm?

That an unauthorized party exploited a vulnerability in its Experimentation product to add malicious JavaScript to some customer projects, and that it has fixed the vulnerability, removed the injected code and secured affected user accounts [1].

Is the vulnerability fixed?

Optimizely says it is, and that it has added protections against unauthorized code delivery [1]. Report URI says the infected files it tracked were clean by 23:11 UTC on 16 November [2]. You should still inspect your own projects.

Which organisations were affected?

Optimizely has not said. Report URI counted 178 organisations from 188 infected snippets, with banking and finance the largest group, and says the real number is likely higher [2].

What could the malicious code steal?

According to Report URI, card details typed into forms on the page, cookies that are not marked HttpOnly, screenshots, and cryptocurrency through swapped wallet addresses [2]. Card fields inside a hosted payment iframe were out of its reach.

We do not use Optimizely. Does this still matter?

Yes. The same injection code was found in three other third-party scripts [3]. Any site that loads vendor JavaScript can be changed without its own servers being touched. A strict Content Security Policy and an inventory of third-party scripts are the defences.

How can an MSP spot this kind of attack?

Watch what client sites actually serve, not just their servers: monitor third-party script changes, collect Content Security Policy reports, and alert on browser connections to new domains. That needs continuous monitoring, not a yearly scan.

How Vijilan helps

Vijilan's SOC watches endpoint, identity and web traffic around the clock, with machine speed where speed wins and a human approving the actions that carry real risk. If you want that coverage on your own estate and your clients', ThreatDefend™ runs it on CrowdStrike Falcon with Vijilan's analysts behind it. Talk to us.

Sources

  1. Web Experimentation Security Incident (Optimizely status page)
  2. World's Largest Brands Infected With Malware Via Optimizely (Report URI)
  3. Malware spread through Optimizely hits 178 organizations (Help Net Security)

Found this useful? Send it to someone who needs it.

Threat notes, once a week

What our SOC actually saw this week: new attack patterns, the detections we shipped against them, and what it means if you run an MSP. Written by the analysts, not by marketing.

One email a week. One click to stop, and we do not sell your address to anyone.

Talk to a security expert

See what 24/7 looks like when the SOC actually acts.

Book a 20-minute platform walkthrough: no slide deck, just the console.

Book a walkthrough →

Questions this answers

What did Optimizely confirm?

That an unauthorized party exploited a vulnerability in its Experimentation product to add malicious JavaScript to some customer projects, and that it has fixed the vulnerability, removed the injected code and secured affected user accounts.

Is the vulnerability fixed?

Optimizely says it is, and that it has added protections against unauthorized code delivery. Report URI says the infected files it tracked were clean by 23:11 UTC on 16 November. You should still inspect your own projects.

Which organisations were affected?

Optimizely has not said. Report URI counted 178 organisations from 188 infected snippets, with banking and finance the largest group, and says the real number is likely higher.

What could the malicious code steal?

According to Report URI, card details typed into forms on the page, cookies that are not marked HttpOnly, screenshots, and cryptocurrency through swapped wallet addresses. Card fields inside a hosted payment iframe were out of its reach.

We do not use Optimizely. Does this still matter?

Yes. The same injection code was found in three other third-party scripts. Any site that loads vendor JavaScript can be changed without its own servers being touched. A strict Content Security Policy and an inventory of third-party scripts are the defences.

How can an MSP spot this kind of attack?

Watch what client sites actually serve, not just their servers: monitor third-party script changes, collect Content Security Policy reports, and alert on browser connections to new domains. That needs continuous monitoring, not a yearly scan.