The Optimizely Hack: How a Trusted Script Became a Malware Delivery Channel

AdobeStock_196234506
emma-stevens-bio-portrait
Written by Emma Stevens
Senior Threat Intelligence Advisor

Key takeaways for the Optimizely cyber attack

  • Attackers exploited a flaw (CVE-2026-132224) in Optimizely's Web Experimentation product and planted malicious JavaScript in customer projects on November 16, 2026.
  • Researchers found infected Optimizely snippets associated with 178 organizations, including major brands and Optimizely's own websites.
  • The compromised snippets were served from Optimizely's CDN or, in some cases, customer domains. They loaded malicious code from attacker-controlled infrastructure, with an inline fallback in some versions.
  • Optimizely says it fixed the flaw, removed the injected code, ended active sessions, revoked tokens, and reset access for affected accounts. Researchers reported card skimming and cryptocurrency theft.
  • Any team that runs Optimizely Web Experimentation should check the Project JavaScript field in every project for code it did not write.

On November 16, 2026, attackers used a vulnerability, CVE-2026-132224, in Optimizely's Web Experimentation platform to inject malicious JavaScript into customer projects. The attack was dubbed ‘The OPTIMJACK’ by security researchers. Researchers were able to identify infected snippets associated with 178 organizations after examining 1,611 Optimizely snippets. The snippets were served from Optimizely’s CDN or, in some cases, from customer domains; they then loaded the attacker’s code or ran an inline fallback. Optimizely confirmed the incident on November 17. The attack is a reminder that a vendor you trust can become the path malware takes into your visitors’ browsers. 

What happened?

On November 17, Optimizely posted an incident notice saying an attacker exploited CVE-2026-132224 in Experimentation and used it to add malicious JavaScript to some customer projects. Optimizely told BleepingComputer that the flaw was in the Experimentation account signup flow. The malicious code was added to a field called Project JavaScript, which runs custom code on pages where the snippet loads. BleepingComputer reported that a researcher found 188 infected script files across 178 organizations including Optimizely's own website and login portal. Beazley Security reported related malicious scripts involving three other services, with earlier activity observed from November 13. 

Why did this attack work so well?

The compromised snippets still appeared to come from Optimizely’s CDN, over a connection using Optimizely’s certificate, and the attacker left the rest of each snippet intact. That made the snippet itself appear to come from a trusted source. The injected loader usually fetched the payload from an attacker-controlled domain, which could be visible in browser or network monitoring. Some versions also included an inline fallback that ran if the external payload was blocked.

Optimizely’s Content Security Policy documentation says some features require unsafe-eval in the script-src directive. Security researchers reported that this setting allowed an inline fallback copy of the malware to run on a company’s website. Teams using Optimizely should review whether their Content Security Policy permits unsafe-eval, whether their configuration requires it, and whether they can remove it. 

Researchers reported that the malware could swap cryptocurrency addresses and skim payment-card details. Related reporting also described code that attempted to deliver iOS exploits. Hudson Rock said the available evidence did not establish successful device exploitation. Researchers identified Coruna and DarkSword in the exploit chain related to iOS, both are well-known iOS exploit kits and frameworks. 

Who is affected?

Any organization that uses Optimizely Web Experimentation, and any visitor to an affected site, may have been exposed. Earlier this year, Optimizely disclosed a separate vishing incident that exposed basic business contact information. 

Are third-party breaches really down? 

We’re seeing attackers target third and fourth party vendors more often. Verizon’s 2026 Data Breach Investigations Report found that 48% of breaches involve a third party, up from 30% the year before. Our annual 2026 State of the Underground report found that ransomware group attacks increased 19%, while 41% fewer observed breaches points to lower visible breach activity, not necessarily lower risk. Our research noted that reporting gaps, non-disclosure, geopolitical tensions, disruption efforts, and changing attacker behavior may all be shaping what defenders can see. 

Increasingly in our research, we are seeing that threat actors see vendors as attractive targets because one compromise can reach many organizations at once because vendors tend to have a much larger blast radius. That raises the pressure on each victim, and in ransomware cases, the pressure to pay. Report URI found malicious code in 188 script files across 178 organizations, all served through one vendor’s platform. While this was not ransomware, it shows the reach of a supply chain attack. Politically or Ideologically motivated threat actors may seek to take a vendor offline for an extended period of time to further their cause or further communicate their views. 

Supply chain attacks are often harder to spot, because sometimes they simply blend in. The malicious code came from a trusted vendor’s own network, so the sites that ran it had little reason to look twice. It became visible because the vendor disclosed it and researchers documented the code across affected sites.

What Bitsight data shows

Bitsight's fourth-party can identify organizations that leverage Optimizely. A vendor's risk includes the providers beneath it. Teams that run Optimizely should understand that map, because a problem at any of those providers can affect the pages they run. A Bitsight TI search returned 252 results for ‘OPTIMJACK’ from November 1-17. Bitsight TI also logged 1,987 items that mention Optimizely on November 16 and 17. In the six weeks before that, it logged about 80.

Current response and mitigation

Optimizely says it patched the flaw and removed the injected code. The company also said it ended active sessions, revoked tokens, reset access for affected accounts, added protections against unauthorized code delivery, and notified affected customers. Organizations should check their own projects rather than assume the vendor caught everything. 

How Bitsight can help

  • Threat intelligence: Bitsight TI tracks discussion of new vulnerabilities and campaigns across news, social, and other sources, so security teams can see activity like this as it develops.
  • Supply chain exposure: Bitsight Beacon extends SOC visibility into critical vendors with validated, actionable threat intelligence.
  • External exposure: Bitsight External Attack Surface Management helps teams find internet-facing infrastructure and assess exposure across their environment and vendor ecosystems.
  • Fourth-party visibility: Bitsight's fourth-party data shows the software and service providers behind your vendors, so you can judge which vendors matter most.

Wrapping up

The Optimizely attack worked because it used trust that customers had already placed in the vendor. Optimizely has fixed the flaw, but the lesson applies to any team that loads third-party code onto its pages. A trusted domain doesn't mean trusted code.

Optimizely cyber attack: What to do next

  • Find every Optimizely deployment: Inventory each site, app, and test environment that loads an Optimizely snippet, including the ones your marketing and product teams manage.
  • Review Project JavaScript: Check each project's custom code for anything you did not write, especially loaders that reference unfamiliar domains.
  • Check change history: Review project edits and account activity from November 13 onward, and flag any change you cannot tie to a known update.
  • Block known indicators: Block 1688360[.]cc, the loader domain named in public reporting, and search your logs for requests to it.
  • Reset access: Rotate passwords and API tokens for Optimizely accounts, and confirm who has access.
  • Tighten your Content Security Policy: Remove unsafe-eval wherever you can, and restrict script sources to the domains you need.
  • Look for skimming: Scan checkout and login pages for unexpected scripts or outbound requests, and involve your payment provider and fraud team if affected pages handle card payments.
  • Follow the vendor's guidance: Watch Optimizely's status page for updates and any steps it recommends for your account.
Bitsight cta background color
2026 GigaOM TPRM Radar cover

See why GigaOm named Bitsight a Leader in TPRM

In GigaOm’s latest Radar report for Third-Party Risk Management, Bitsight was positioned as a Leader and Fast Mover for its externally sourced cyber risk ratings, continuous monitoring, API-first integrations, and vendor risk visibility.

 

Get the report

Bitsight cta background color