Optimizely Supply-Chain Attack Injects Malicious JavaScript Into 178 Major Websites
A supply-chain compromise at Optimizely, the widely used web experimentation and feature-flagging platform, allowed attackers to plant malicious JavaScript that was served to visitors of 178 organizations, including some of the most heavily trafficked destinations on the internet. The incident, reported on 16 November 2026, underscores how a single third-party script dependency can expose an enormous blast radius of otherwise well-defended brands.
What Happened
According to reporting by Cyber Security News, attackers inserted malicious code into Optimizely's Web experimentation platform. Because Optimizely's snippet is embedded across customer sites to run A/B tests and personalization campaigns, the injected JavaScript was distributed automatically to every site loading the compromised component. The affected roster reads like a who's-who of global business and media: Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, and Peacock, among others.
The compromise was identified by researcher Scott Helme of Report URI, who is known for his work on security headers, content security policy, and third-party script monitoring. His discovery highlights a recurring theme in modern web security: the client-side attack surface now extends well beyond a company's own codebase and into the vendor scripts it trusts.
Why Third-Party Scripts Are a Prime Target
Optimizely sits in a category of tooling that is especially attractive to attackers. Experimentation platforms must execute arbitrary JavaScript in the context of the host page, often with minimal friction for marketing and product teams. That means a compromise at the vendor does not require breaching any of the 178 customers individually — the malicious payload simply rides along with the legitimate script delivery path.
This is the same pattern seen in earlier high-profile supply-chain incidents involving analytics, customer-support widgets, and tag managers. The economics favor the attacker: one intrusion yields access to hundreds of sites and potentially millions of sessions. For defenders, the lesson is that vendor risk management must extend to client-side JavaScript, not just to backend APIs and data processing agreements.
Reported Objectives: Card Skimming and iPhone Targeting
The headline summary indicates two apparent goals: stealing credit card data and targeting iPhone users. Card-skimming via injected JavaScript — often called formjacking or web skimming — typically involves silently capturing payment details as shoppers type them into checkout forms, then exfiltrating that data to attacker-controlled infrastructure. Because the script runs in the victim's browser, it can bypass many server-side controls.
The reported iPhone targeting suggests the campaign may have included device-specific logic, potentially serving different payloads or behaviors based on user-agent or platform detection. Device-aware targeting is a common technique in malvertising and exploit-delivery chains, allowing attackers to tailor content to the most monetizable or vulnerable segment of a site's audience. Specific technical details of the iPhone-focused component have not been fully detailed in the initial reporting.
The Scale of Exposure
The list of affected organizations spans media, SaaS, retail, financial services, aviation, and cryptocurrency hardware. That diversity is itself instructive. Organizations in regulated sectors such as banking and consumer credit — HSBC and Equifax appear on the list — face heightened scrutiny around third-party risk and incident disclosure. Meanwhile, SaaS providers like Zoom, Salesforce, and GitLab must consider whether their own customers' trust is affected by a compromise in a marketing-adjacent tool.
It is important to note that inclusion on the list reflects exposure to the compromised script, not confirmation that every visitor was maliciously acted upon. Determining actual impact requires forensic analysis of which sessions loaded the payload and what data, if any, was captured.
Defensive Lessons
Several practical takeaways emerge for security teams:
- Inventory every third-party script. Maintain a current register of all external JavaScript loaded by production properties, including owners and business justification.
- Enforce Content Security Policy. A restrictive CSP with nonces or hashes, and tightly scoped
script-srcdirectives, can limit the impact of a compromised vendor domain — though it requires ongoing maintenance. - Monitor for script changes. Integrity monitoring and change detection on third-party resources can shorten detection time, as demonstrated by the researcher-led discovery in this case.
- Apply least privilege to vendor integrations. Experimentation and personalization tools rarely need access to payment fields; scoping and isolating them reduces skimming exposure.
- Prepare disclosure and notification playbooks. When a shared vendor is compromised, customers will look to the brands they trust for guidance, not to the vendor.
What Comes Next
Expect affected organizations to conduct forensic reviews of their checkout and authentication flows, and Optimizely to face questions about how its platform was breached and what controls failed. Regulators in jurisdictions with strict breach-notification rules may take interest if payment data was captured. For the wider industry, the incident is a reminder that the browser is a shared trust boundary — and that the security of a website is only as strong as the weakest script it chooses to load.
Source: Cyber Security News — Hackers Infect 178 Major Websites via Optimizely