Optimizely Supply Chain Breach: Malicious Code Injected into 178 High-Profile Websites

A significant supply chain security breach has sent shockwaves through the digital landscape after an attacker successfully exploited a vulnerability within Optimizely, a leading digital experience platform. By compromising the platform’s website testing infrastructure, the unauthorized party was able to inject malicious JavaScript into the codebases of 178 major organizations, exposing millions of visitors to a multifaceted cyberattack. The breach, which impacted industry giants including Zoom, the BBC, CNN, Salesforce, GitLab, and IKEA, highlights the persistent and escalating risks associated with third-party software dependencies.

The breach was first brought to light by security researchers at Report URI, led by noted expert Scott Helme. According to their investigation, the scope of the infection was substantial; of the 1,611 Optimizely snippets analyzed by the team, 188 were found to contain malicious code. The fact that the provider itself, Optimizely, was also among the organizations impacted underscores the severity of the incident and the systemic nature of the vulnerability.

Optimizely officially acknowledged the security incident in a status notice published on November 17. The company stated that an “unauthorized party exploited a vulnerability in Experimentation,” a core component of their platform. By leveraging this flaw, the attacker gained the ability to append unauthorized JavaScript directly into customer projects. Optimizely moved quickly to address the crisis, confirming that the flaw has since been patched, the malicious code has been removed, and additional security measures have been implemented to protect affected user accounts.

The Anatomy of the Malicious Injection

The sophistication of the attack lay in its surgical precision. Rather than replacing entire scripts, the attacker inserted malicious code into the "Project JavaScript" field of the affected customer projects. This field is a powerful feature that allows developers to run custom code on every page where the Optimizely snippet is deployed. Because the remainder of the legitimate script was left untouched, the tampered files continued to be served from Optimizely’s trusted content delivery network (CDN). Crucially, the scripts were still signed with Optimizely’s valid security certificate, a factor that allowed the malicious activity to bypass standard browser security warnings and detection mechanisms.

Report URI’s analysis revealed that the injected JavaScript was designed to execute a diverse array of malicious functions, turning trusted websites into vehicles for financial fraud and data theft. One of the primary objectives was cryptocurrency theft. The script was configured to detect and swap legitimate cryptocurrency wallet addresses displayed on the websites with those belonging to the attacker. This technique, often referred to as "wallet swapping," is a highly effective way to siphon funds from unsuspecting users. By 19:25 UTC on November 16, the attacker’s wallets had already received approximately $7,040 in illicit gains before the accounts were emptied early the following morning.

Beyond simple wallet hijacking, the injected script functioned as a sophisticated digital card skimmer. As visitors interacted with forms on the compromised websites, the malware captured sensitive payment card details in real-time. While the script was limited by browser security—meaning it could not access data entered into secure, hosted payment iframes—the sheer volume of traffic on sites like the BBC or Zoom meant that the potential for data exfiltration was immense. The script also extended its reach to sensitive session data, stealing user cookies and capturing screenshots of pages, which could potentially be used for account takeovers or deeper intelligence gathering.

The threat was particularly acute for mobile users. On iPhones and iPads, the malicious JavaScript was programmed to deliver specific iOS exploit kits, identified by researchers as "Coruna" and "DarkSword." These kits represent a significant escalation in the danger posed by the breach, as they attempt to exploit vulnerabilities in the operating system itself. In response to these findings, Report URI issued an urgent advisory to mobile users, recommending immediate updates to iOS 18.7.3 or later, or iOS 26.3 or later, to patch the underlying vulnerabilities targeted by these kits.

The Timeline and the Broader Threat Landscape

The window of opportunity for the attacker was relatively brief, yet highly active. The first instance of unauthorized code injection was recorded at 04:21 UTC on November 16. By 23:11 UTC the same day, Report URI reported that all infected files had been remediated. Despite this swift response, the impact of nearly 20 hours of exposure on such high-traffic websites is likely to be profound.

While the identity of the attacker remains unknown, the investigation into their methodology suggests a high degree of experience. Report URI noted that one of the cryptocurrency wallets associated with the attack had been active since March 2026, and the attacker appears to be linked to a previous campaign involving similar injections via other third-party scripts. This suggests that the breach was not an isolated incident but rather part of an ongoing, coordinated effort to exploit weaknesses in the software supply chain.

The incident has reignited debates regarding the fragility of the modern web. "Supply chain breaches may be an inherent weakness of the web in its current form, but this doesn’t excuse organizations from failing to reduce their own attack surface," remarked William Wright, CEO of Closed Door Security. Wright’s assessment highlights the tension between the convenience of third-party integrations and the security risks they introduce. When companies rely on external platforms like Optimizely for their digital infrastructure, they effectively extend their security perimeter to include those partners. If that partner is compromised, the client organization becomes vulnerable regardless of their internal security posture.

As the dust settles, security professionals emphasize that the true scale of the breach may never be fully known. Report URI acknowledged that their analysis was limited to the snippets they were able to verify within the available timeframe. Given the widespread use of Optimizely’s services across the global internet, it is highly probable that the actual number of affected organizations exceeds the 178 confirmed cases.

For the organizations involved, the aftermath involves not only the technical cleanup but also the arduous process of investigating potential data breaches, notifying impacted users, and addressing the fallout from the card-skimming activity. For the broader cybersecurity community, the Optimizely incident serves as a stark reminder that in an interconnected digital economy, the security of an organization is only as strong as the weakest link in its supply chain. As attackers continue to evolve their tactics—moving from simple website defacement to sophisticated, persistent, and multi-functional script injections—the reliance on third-party scripts requires more rigorous auditing, sandboxing, and real-time monitoring to prevent future catastrophic failures.