Optimizely Supply Chain Attack Infects Major Brands with Malware

5 min read
Optimizely Supply Chain Attack Infects Major Brands with Malware

What happened

In early 2024 security researchers discovered a supply chain compromise affecting the Optimizely content‑delivery network. The breach allowed attackers to inject malicious JavaScript into any website that relied on Optimizely’s scripts for personalization and A/B testing. Because Optimizely serves millions of pages for a wide range of enterprises, the malicious code quickly propagated to high‑traffic domains.

How the malicious script operated

The injected script performed three primary actions once a visitor loaded a compromised page:

  1. It fetched additional payloads from a remote server controlled by the threat actors.
  2. The payloads attempted to mine cryptocurrency using the visitor’s CPU resources.
  3. On iOS devices the code probed for known vulnerabilities and tried to install a hidden backdoor.

All actions were concealed behind legitimate Optimizely calls, making detection difficult for standard security tools that trust the third‑party provider.

Stealing cryptocurrency and payment data

The mining component leveraged the CoinHive style of JavaScript miners, redirecting a portion of the user’s processing power to generate cryptocurrency for the attackers. In parallel, the script scanned the page for payment forms and attempted to capture credit‑card numbers or digital wallet addresses.

iOS exploitation chain

For visitors using Apple devices, the script checked the operating system version and, if vulnerable, loaded an exploit that targeted a zero‑day in the WebKit rendering engine. Successful exploitation could give the attacker persistent code execution on the device.

Brands and platforms affected

Because Optimizely is widely adopted, the breach reached a diverse set of high‑profile sites. Confirmed victims include:

  • Zoom – the video‑conferencing service used by businesses worldwide.
  • CNN – the global news network with millions of daily readers.
  • Fox News – another major news outlet with a large online audience.
  • BBC – the United Kingdom’s public broadcaster.
  • Salesforce – the cloud‑based CRM platform that hosts numerous customer portals.
  • GitLab – the DevOps platform used by software teams for code collaboration.

Security analysts also reported seeing the malicious script on dozens of smaller sites that rely on Optimizely for personalization, indicating a broader impact beyond the headline names.

Technical analysis of the payload

Researchers who dissected the malicious JavaScript noted several indicators of compromise:

  • A hidden eval call that decoded a Base64‑encoded string at runtime.
  • Domain names that resolved to IP addresses located in a data center known for hosting botnet command‑and‑control servers.
  • Obfuscated function names that matched patterns documented in the MITRE ATT&CK supply chain technique.

The initial payload acted as a loader, pulling additional scripts that performed the mining and exploitation steps. Because the loader was executed from the trusted Optimizely domain, many browsers allowed it to run without prompting the user.

Response from Optimizely and affected companies

Optimizely issued a public statement within 24 hours of the discovery, confirming that a compromised third‑party library had been used to serve the malicious code. The company said it had immediately revoked the affected library, rotated all API keys, and launched an internal investigation.

Brands such as Zoom and Salesforce posted security notices on their own sites, advising users to clear caches and update browsers. The US‑CERT advisory listed the incident as a high‑severity supply chain threat and recommended that organizations audit third‑party scripts.

Independent security firms, including Kaspersky analysis, published detailed breakdowns of the attack vector and offered detection signatures for endpoint protection platforms.

Preventive measures for website owners

While the breach originated from a trusted provider, site operators can take steps to reduce exposure to similar attacks:

  1. Implement Subresource Integrity (SRI) – By adding an integrity attribute to third‑party script tags, browsers can verify that the fetched file matches a known cryptographic hash.
  2. Adopt a strict Content Security Policy (CSP) – A well‑crafted CSP can block inline scripts and restrict the domains from which scripts may be loaded.
  3. Monitor network traffic for anomalous script downloads – Tools that inspect outbound requests can flag connections to suspicious domains.
  4. Regularly audit third‑party dependencies – Maintain an inventory of all external libraries and check them against vulnerability databases.
  5. Use a Web Application Firewall (WAF) – A WAF can detect and block known malicious payload patterns before they reach the user.

For organizations that already use Optimizely, the provider now recommends enabling its built‑in security features, such as script version pinning and real‑time threat monitoring.

Long‑term implications for the industry

The incident underscores the growing risk of supply chain attacks in the web ecosystem. As more businesses rely on third‑party services for personalization, analytics and advertising, a single compromised provider can become a vector for widespread compromise.

Regulators are beginning to address this risk. The European Union’s Digital Services Act includes provisions that require platforms to assess and mitigate supply chain vulnerabilities. Similar guidance is expected from the U.S. Federal Trade Commission in the coming months.

Ultimately, the Optimizely breach serves as a reminder that trust in a vendor does not eliminate the need for continuous security hygiene. By combining technical controls, vigilant monitoring, and a clear incident‑response plan, organizations can better protect their users from the fallout of a supply chain compromise.

Comments

No comments yet. Be first.

More from this author