Optimizely supply chain attack

The Optimizely Supply Chain Attack: How Malicious Scripts Reached Millions

When you visit a major news site or a video conference platform, you trust that what loads on your screen comes from the company you think it does. In a supply chain attack that exposed this assumption, attackers compromised Optimizely Web Experimentation, a widely-used A/B testing service, and injected card-stealing code into scripts delivered to visitors of CNN, BBC, Zoom and at least 175 other organizations. This incident shows how a single vulnerability in a third-party service can turn thousands of websites into unwilling malware distributors.

Optimizely Supply Chain Attack: Card Skimmers Hit Major Sites

What Happened: The Optimizely Compromise

Optimizely Web Experimentation, a service used by thousands of websites to run A/B tests and personalization experiments, was compromised by an attacker who exploited a flaw in the platform. The attacker used this vulnerability to inject malicious code into JavaScript files that Optimizely's customers load on their websites. For at least a window of time on November 17, 2026, visitors to sites operated by CNN, the BBC, Zoom and approximately 175 other organizations received this compromised code in their browsers. Report URI, a security monitoring firm that watches third-party script loading, detected the injection and raised the alarm. The code remained active long enough to reach a significant population of users before being removed.

How the Attack Worked: Injection Into Trusted Code

Supply chain attacks work by targeting a service that sits between a company and its users. When a website owner uses a third-party service like Optimizely, they embed scripts on their pages that load from Optimizely's servers. If an attacker can control what those scripts contain, they can reach every visitor to every site using that service. In this case, the attacker manipulated Optimizely's platform so that when users visited compromised websites, their browsers downloaded and executed the malicious payload. Because the script originated from a trusted domain (Optimizely's own infrastructure), security filters and browser protections often pass it through without scrutiny. The code was not visibly hosted on CNN's or BBC's servers; it came through the third-party dependency both sites had chosen to trust.

The Payload: Card Skimmers and iOS Exploits

The malicious code served to visitors was built to steal payment card information and, on iOS devices, to deliver exploit kits. Card skimmers are scripts that run silently on e-commerce or payment pages and capture credit card numbers, expiration dates and security codes as users type them in. The iOS exploit component suggests the attacker was also trying to compromise Apple users through browser vulnerabilities. The sophistication of hosting two different payloads indicates this was not a random attack but a deliberate, multi-pronged campaign targeting high-traffic sites where users are likely to enter sensitive financial data. BBC and CNN sites themselves do not typically accept payment cards, which suggests the attacker was either aiming to harvest data from ads or cookies from third-party services embedded on those pages, or was opportunistically infecting any user who visited these sites.

Why This Matters: The Third-Party Risk Blind Spot

Large organizations like CNN, BBC and Zoom invest heavily in their own security but have little direct control over the Optimizely platform's code. They rely on Optimizely to maintain the integrity of the service. When a vulnerability exists in a third-party platform, no amount of a website owner's security measures can fully prevent the injection. This creates a paradox in web security: the more a site depends on external services for functionality (analytics, A/B testing, ads, fonts, CDN content), the more potential entry points an attacker gains. A 2024 report from Report URI and others documented that the average website loads scripts from dozens of third-party domains, yet most website owners have visibility into only a handful of them. The Optimizely incident is one of several supply chain compromises (including past incidents involving SolarWinds, 3CX and others) that have made organizations acutely aware that they cannot trust third parties blindly.

Detection and Response: How Users and Defenders Spotted It

Report URI detected the Optimizely compromise by monitoring the JavaScript resources that websites load and flagging unexpected changes in their content. When millions of users suddenly request the same script from the same service and that script contains new, malicious code, detection systems tuned for supply chain attacks can spot the fingerprint. Browsers equipped with real-time script inspection, security vendors running endpoint protection, and network-level monitors can all alert on anomalous payloads. Once Optimizely was notified, the company had to rapidly patch the vulnerability, remove the malicious code and communicate to all affected customers. Customers, in turn, had to either wait for Optimizely to clean the scripts or temporarily disable the service on their sites. Users who visited affected sites during the active window may have had their card data compromised; payment card companies and fraud detection services would have had to watch for unusual activity on cards used on those sites.

Lessons for Organizations and Users

No website can eliminate third-party risk entirely, but organizations can reduce exposure through several practices: regularly audit which third-party scripts are loaded and why; request security certifications and incident response procedures from vendors; use Content Security Policy (CSP) headers to restrict what third-party scripts can do; employ real-time script monitoring to catch unexpected changes; and consider loading third-party code via a subdomain or iframe sandbox to limit its access to payment forms or sensitive data. For users, the lesson is that visiting a trusted site does not guarantee that everything loaded on that site came from that company. Using a password manager instead of typing credit card details manually can reduce exposure to card skimmers. Keeping browsers, operating systems and security software up to date reduces the likelihood of iOS or other exploits succeeding. Reviewing credit card statements and enabling fraud alerts with your bank are practical steps that apply to all supply chain attacks.

Frequently Asked Questions

Can I tell if my data was stolen in the Optimizely attack.

No definitive list of compromised users has been published. If you visited CNN, BBC, Zoom or one of the other 175+ affected sites on November 17, 2026, during the active window, your browser may have executed the malicious code. Check your credit card and bank statements for unauthorized charges. If you see suspicious activity, contact your card issuer and consider freezing your credit.

Why did such a large number of major websites use the same vulnerable service.

Optimizely is a market-leading A/B testing and personalization platform, and it is extremely common for large websites to use such services. The vendor's market position meant that compromising it could reach an exceptionally large audience in a single attack.

Does this mean I should avoid third-party services on websites.

Third-party services are fundamental to how the modern web works; avoiding them entirely is impractical. Instead, focus on which services handle your sensitive data. Be cautious about services embedded on payment pages, account pages or form handlers. Use separate cards or virtual card numbers where available.

How do I know if a site I use regularly was affected.

You can check Report URI's public disclosure or the official Optimizely security advisory for a list of known affected organizations. Some sites may also have sent notification emails to users. If you regularly visit a site that uses Optimizely, that site was potentially affected during the incident window.

Can I protect myself from supply chain attacks as a user.

Complete protection is not possible, but you can reduce exposure by using unique, strong passwords; enabling multi-factor authentication on sensitive accounts; monitoring your financial accounts; using privacy-focused browsers or extensions that block tracking and malicious scripts; and keeping your operating system and applications patched. VPNs and Tor can mask your location and online activity, though they do not prevent code executing in your browser from stealing data you enter locally.

Source: The Hacker News (https://thehackernews.com/2026/11/hijacked-optimizely-scripts-served-card.html)