Cybersecurity

Malicious Optimizely Scripts Reached 178 Organizations, Exposing Website Visitors to Data Theft

A malicious JavaScript campaign distributed through Optimizely Web reached visitors across 178 organizations, according to security researcher Scott Helme. The payload included cryptocurrency address substitution, payment-card skimming, cookie theft and iOS exploit delivery mechanisms, highlighting the security risks associated with trusted third-party website scripts.

Editorial illustration showing a third-party JavaScript supply-chain attack affecting enterprise websites through compromised trusted scripts.

AI-generated editorial illustration by TeamRedevs; conceptual artwork.

Overview

A security incident involving the Optimizely Web experimentation platform has exposed a significant weakness in how modern websites manage third-party JavaScript dependencies.

On 16 November 2026, security researcher Scott Helme of Report URI identified malicious JavaScript being served to visitors of 178 organizations through Optimizely Web.

The affected organizations included well-known companies and services such as Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock.

The malicious code was capable of replacing cryptocurrency wallet addresses, collecting payment-card information, stealing certain browser cookies and screenshots, and loading additional iOS exploit chains.

This was not simply an ordinary website malware infection. It demonstrated how an attacker could potentially reach visitors through software dependencies that the affected organizations themselves trusted.

What happened inside Optimizely Web?

Optimizely Web is used by organizations to run website experiments, personalize user experiences and test different page configurations.

Customers typically load a JavaScript snippet from Optimizely's content delivery infrastructure.

These snippets can contain customer-specific configuration and custom JavaScript, including a field called Project JavaScript or projectJS.

According to Report URI, attackers inserted malicious code into this custom JavaScript field across multiple customer projects.

The affected snippets continued to be served through the legitimate Optimizely CDN, meaning visitors could receive the malicious code from a domain that the websites already trusted.

This distinction is important.

The researcher explicitly said that the incident was not a CDN cache-poisoning attack: Optimizely's CDN served the modified content it had been given.

The mechanism by which the attacker obtained write access across unrelated customer projects remained unknown in the investigation. A compromised platform system, compromised credentials or another form of unauthorized access were possibilities, not established explanations.

What could the malicious JavaScript do?

The investigation identified several capabilities within the malicious payload.

CapabilityPotential impact
Cryptocurrency address replacementSubstitutes attacker-controlled wallet addresses when visitors copy legitimate addresses
Payment-card skimmingCollects card numbers, expiry dates and CVV information from exposed form submissions
Cookie theftCollects browser cookies not protected by the HttpOnly attribute
Screenshot collectionCaptures rendered page content and sends it to attacker-controlled infrastructure
iOS exploit deliveryLoads additional exploit chains based on the visitor's device and iOS version

1. Cryptocurrency wallet substitution

The script searched for cryptocurrency wallet addresses across website content, forms and other browser interactions.

When it found a supported address, it could replace it with an attacker-controlled address.

This is particularly dangerous because a visitor might believe they are copying a legitimate payment address while actually copying a different destination.

2. Payment-card skimming

The payload was expanded to include payment-card collection functionality.

It monitored form submissions and browser network requests for payment-card details.

The researcher identified card information being sent to an external collection endpoint.

However, hosted payment fields running inside cross-origin iframes, such as those used by Stripe and Adyen, were outside the payload's direct access in the examples examined.

3. iOS exploit delivery

The investigation also found additional infrastructure associated with Coruna and DarkSword exploit chains.

Report URI documented different delivery paths depending on the iOS version.

Importantly, the presence of exploit delivery code does not establish that every visitor's device was successfully compromised.

The actual number of affected cards, stolen cookies and successfully exploited devices was not established by the investigation.

How many organizations were affected?

Report URI examined 1,611 distinct Optimizely JavaScript snippets.

Its investigation identified:

  • 188 infected JavaScript snippets.
  • 178 affected organizations.
  • Multiple industry sectors.
  • Confirmed cryptocurrency transactions to attacker-controlled wallets.

The affected sectors included financial services, technology, retail, streaming, media, travel, healthcare and telecommunications.

The malicious code was being removed during the investigation.

In its 21:52 UTC sweep on 16 November, Report URI found only one of the 188 infected snippets still containing the malicious code, compared with 169 infected snippets at 20:56 UTC.

This indicates significant cleanup activity, but it should not be interpreted as proof that every affected customer environment was fully remediated.

Why this incident matters for developers and SaaS companies

The most important lesson is that a website can have clean application code and still expose visitors to malicious JavaScript.

Third-party scripts frequently receive substantial browser permissions.

This includes the ability to interact with page elements, inspect form fields and communicate with external servers, depending on browser security controls.

Many companies allow marketing and product teams to add analytics, experimentation, personalization and advertising scripts without requiring every change to pass through the main engineering release process.

That creates an additional software supply-chain dependency.

For SaaS companies, the incident raises several practical questions:

  • Which third-party scripts execute on production pages?
  • Who can modify those scripts?
  • Are changes recorded and reviewed?
  • Are unexpected external network requests monitored?
  • Are payment forms isolated from unrelated scripts?
  • Are Content Security Policy reports actively monitored?

Recommended security measures

  1. Maintain an inventory of all third-party JavaScript dependencies.
  2. Monitor changes to vendor-hosted JavaScript files.
  3. Use restrictive Content Security Policy directives.
  4. Monitor unexpected external script and network destinations.
  5. Keep payment fields isolated using appropriately configured hosted payment components.
  6. Restrict who can publish custom scripts through marketing and experimentation platforms.
  7. Investigate historical browser and security logs when a vendor script is compromised.

Subresource Integrity can help verify fixed script contents, although it is difficult to use with dynamically changing experimentation scripts.

Content Security Policy can provide additional protection when correctly configured.

What remains unknown?

At the time of this briefing, the attacker's original access method had not been established.

StepSecurity's independent investigation also reported that it could not find a public Optimizely statement explaining how the affected project scripts were modified.

Optimizely's public status page showed a separate Recommendations tracking and reporting service issue, not a confirmed public incident report explaining this JavaScript campaign.

The distinction matters: the available research demonstrates malicious code distributed through Optimizely-hosted scripts, but it does not establish the precise underlying security breach mechanism.

The incident should encourage every organization relying on third-party website scripts to treat those scripts as production software dependencies requiring monitoring, access control and incident-response procedures.

Why this is trending

Hacker News

The Report URI investigation appeared among the leading stories on the Hacker News front page, with 133 points and 24 comments at retrieval. Discussion focused on third-party script permissions, marketing-controlled JavaScript and the limitations of relying on trusted domains.

Read the Hacker News discussion

Reddit

  • r/cybersecurity: approximately 80 votes on a discussion concerning malicious scripts loaded through Optimizely.
  • r/pwnhub: approximately 27 votes on research connecting poisoned scripts to major websites and iOS exploit infrastructure.

Participants discussed how the scripts could affect users even when a company's own application code remained clean.

Other platforms

  • X: No independently verified high-traction public post retrieved.
  • daily.dev: No matching public developer post verified.
  • TechCrunch: No dedicated report found in the retrieved coverage.

Sources

  1. Report URI — World's Largest Brands Infected With Malware Via Optimizely — 16 November 2026. Original investigation by Scott Helme documenting infected snippets, affected organizations, attack capabilities and cleanup.
  2. StepSecurity — OPTIMJACK: Optimizely-Hosted Scripts Loaded a Crypto Clipper and Card Skimmer — 17 November 2026. Independent technical analysis of public scan records, payload changes, infrastructure and indicators of compromise.
  3. Optimizely Service Status — Checked 17 November 2026. Public status information; the displayed November 16 incident concerned a separate Recommendations service issue.
  4. Hacker News discussion — 16–17 November 2026. Developer and security-community response.
  5. Reddit r/cybersecurity — 16 November 2026. Technical community discussion.
Share

Further reading

Building a product in this space?

MORE FROM THE NEWSROOM

Related news

All news
Back to all news

READY WHEN YOU ARE

Building in this space?

We help teams turn industry shifts into shipped products. Let’s talk about your roadmap.