Optimizely / Report URI — Malicious Code Injection Campaign via Third-Party Script Supply Chain

Publication date: November 17, 2026
Category: Supply chain attacks (realtime trigger)

Introduction

A sophisticated digital supply-chain attack has exposed the inherent risks associated with relying on third-party web services in the modern web ecosystem. On November 16, 2026, security researcher Scott Helme and his team at Report URI identified malicious JavaScript code embedded within Optimizely files associated with 178 high-profile organizations, including the BBC, CNN, Zoom, Salesforce, and GitLab. Rather than breaching the internal servers of these major corporations directly, the threat actors abused a trusted web testing and optimization platform to inject malicious payloads straight into visitors’ browsers.

What is Optimizely (General Analysis)?

Optimizely is an enterprise software platform designed to help businesses perform A/B testing, user experience personalization, and statistical analytics on their websites. To function, a website integrates a lightweight JavaScript snippet provided by Optimizely. This script is loaded asynchronously or synchronously into the visitor’s browser, allowing it to modify interface elements, execute experiments, and measure user interactions.

In this incident, this legitimate mechanism was weaponized into a supply-chain attack. Instead of breaking into the servers of 178 distinct organizations separately, the attackers compromised a shared intermediary vendor, compelling millions of trusting users to download unauthorized code while browsing news outlets, communication tools, and enterprise platforms.

Because this incident does not currently feature a formally assigned CVE identifier in the NVD database at the time of writing, it is classified on an estimated basis under third-party software integrity flaw taxonomies, bearing a High Severity rating (Estimated CVSS v3.1: 8.2 / Estimated Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N), reflecting the ability to manipulate content delivered to end-users via a privileged third-party channel.

How Does It Work? (Technical Analysis)

The attack mechanism operated by substituting or tampering with authorized scripts distributed via Optimizely’s infrastructure service. Forensic analysis conducted by Report URI established the exact timeline of the incident, using the BBC as a primary paradigm:

  • Initial Infection Flow: At 02:21 UTC on November 16, Report URI traffic captures and monitoring recorded a clean Optimizely snippet on the BBC domain (bbc.com). However, two hours later at 04:21 UTC, an injected version containing obfuscated instructions was detected.
  • Payload Execution and Deployment: By 08:28 UTC, researchers observed the manipulated script proceeding to download and execute a primary malicious payload inside end-user browsers.
  • Functional Objectives of the Code:
    • Cryptocurrency Redirection: Dynamic modification of payment destination addresses on transaction pages to divert crypto assets into wallets controlled by the attackers.
    • Payment Card Skimming: Capturing data entered into unsegregated payment forms, although forms hosted on isolated external payment gateways (such as Stripe or Adyen) remained out of reach for this specific skimmer.
    • Mobile Exploit Kits: Deploying vectors designed to identify and exploit known vulnerabilities in outdated Apple iOS and iPadOS versions on iPhones and iPads.
    • Session Hijacking: Partial extraction of session cookies to facilitate unauthorized access to active user accounts.
  • Vendor Remediation: Optimizely confirmed the breach, stating that the issue was contained, the internal vulnerability patched, and the malicious code purged from affected projects before the day concluded (23:11 UTC on November 16).

Affected Systems / Environments

The incident directly impacted visiting users across 178 organizations utilizing Optimizely services during the temporal attack window on November 16, 2026. Notable affected entities include:

  • Media Organizations: British Broadcasting Corporation (BBC), Cable News Network (CNN).
  • Communication and Collaboration Platforms: Zoom Video Communications.
  • Management and Development Solutions: Salesforce, GitLab.
  • General Platforms: Roughly 190,000 live websites globally utilize the platform technologically (according to BuiltWith metrics), although the malicious impact was restricted to specific projects where files were manipulated by attackers.
  • End-User Devices: Modern web browsers and mobile devices running vulnerable, unpatched versions of Apple iOS and iPadOS.

Mitigation and Detection

Remediation

Since the primary vector resides within third-party infrastructure, mitigation falls across service providers, website operating organizations, and end-users:

  1. Mobile Device Updates: Promptly apply the latest Apple security patches on iOS and iPadOS devices to mitigate mobile exploit kit execution.
  2. Financial Transaction Audit: Thoroughly review cryptocurrency transfers executed on November 16, cross-referencing destination addresses against trusted communication channels.
  3. Card and Account Monitoring: Inspect bank statements for credit cards used on affected sites and investigate anomalous sessions or unexpected changes in web account credentials.
  4. Third-Party Script Restriction: Web organizations must implement strict Content Security Policies (CSP) featuring robust directives in script-src alongside mechanisms like Subresource Integrity (SRI) and continuous behavior monitoring of external scripts.

Detection

For defensive security teams and Security Operations Center (SOC) analysts, tracking anomalies in web dependency integration is critical:

  • External JavaScript File Integrity Analysis: Deploy synthetic monitoring solutions that compare cryptographic hashes of third-party scripts at runtime.
  • Network Log Review: Inspect HTTP requests targeting unknown infrastructure domains originating from web optimization or analytics scripts.

“A software supply-chain attack demonstrates that traditional perimeter security is wholly insufficient when malicious code is transported through legitimate and widely trusted channels.”

Wrapping Up

The Optimizely incident highlights the extreme vulnerability of the modern web to third-party script supply-chain compromises. With 178 organizations impacted—including industry giants like the BBC, CNN, and Zoom—attackers demonstrated the high efficacy of leveraging trusted components as vehicles for covert payment skimmers, crypto redirection, and mobile exploits. The core takeaway is the urgent necessity of adopting a zero-trust posture toward external dependencies, demanding continuous integrity monitoring and strict content security controls by website operators.

References