How a Popular Tool Infected Zoom and Salesforce
TL;DR: A suspected supply chain attack on Optimizely caused major websites like Zoom and Salesforce to serve malware. The malicious code was designed to steal cryptocurrency, payment details, and exploit iOS devices, putting countless users at risk.
Key facts
- Category
- Cybersecurity
- Impact
- Critical
- Published
- Source
- BleepingComputer
Full summary
A supply chain attack on Optimizely led to major sites like Zoom and Salesforce unknowingly serving malware designed to steal user data.
A suspected supply chain attack has compromised Optimizely, a popular A/B testing and personalization platform, turning many of the world's most visited websites into unwitting distributors of malware. According to reporting from BleepingComputer, malicious JavaScript was injected into sites that use the service, including major brands like Zoom, Salesforce, GitLab, CNN, Fox News, and the BBC. This code was designed to execute a range of harmful actions, from stealing cryptocurrency and payment card information to exploiting vulnerabilities in iOS devices. The incident highlights the significant and often hidden risks associated with third-party dependencies, where a single breach at a vendor can have a cascading effect across thousands of their customers and millions of their end-users. The attack effectively weaponized the trust that these major brands placed in a widely used marketing technology tool.
The attack works by exploiting the fundamental architecture of the modern web. Websites routinely embed scripts from third-party services like Optimizely to add functionality without having to build it themselves. When you visit a site like Zoom, your browser is instructed to fetch and execute code not just from Zoom's servers, but also from Optimizely's. In a supply chain attack, threat actors don't target their ultimate victim directly. Instead, they find a weaker link in the chain—in this case, the third-party vendor. By compromising Optimizely's infrastructure, the attackers were able to modify the legitimate JavaScript file served to all of its customers. This meant that any visitor to an affected site would automatically download and run the malicious payload. This technique is highly effective because the malicious script is delivered from a trusted, expected domain, making it difficult for traditional security measures to detect.
This incident is not an isolated event but part of a growing and alarming trend of software supply chain attacks. It bears a strong resemblance to the Magecart attacks that have plagued e-commerce sites for years, where attackers inject card-skimming code into third-party payment scripts. It also echoes larger-scale breaches like the SolarWinds attack, which compromised a software update mechanism to distribute malware to high-profile government and corporate targets. The core issue is that modern applications are not monolithic but are assembled from hundreds of different components and services. Each of these dependencies represents a potential attack vector. While companies invest heavily in securing their own code and infrastructure, their overall security is only as strong as the weakest link in their digital supply chain. This attack on Optimizely serves as a powerful reminder that implicit trust in any external vendor is a dangerous assumption.
The key takeaway for developers, CTOs, and security teams is the urgent need to move from a model of trust to one of verification. Simply whitelisting a vendor is no longer sufficient. Teams must implement technical controls to ensure the integrity of the third-party code they execute. A first step is maintaining a comprehensive inventory of all external scripts, often called a Software Bill of Materials (SBOM). More advanced measures include implementing a strict Content Security Policy (CSP) to control which domains can execute code. However, since the malicious script came from a trusted domain, CSP alone would not have stopped this attack. The most robust defense is Subresource Integrity (SRI), a security feature that allows a browser to verify that a fetched file has not been tampered with by comparing its cryptographic hash to one provided by the website. While SRI adds some operational complexity, the scale and impact of this incident make a compelling case for its wider adoption. Ultimately, organizations must assume that any of their dependencies could be compromised and build defenses accordingly.
Why it matters
This attack demonstrates how a single compromised third-party script can turn thousands of trusted websites into malware distributors. For engineering and security teams, it proves that whitelisting a vendor is not enough; you must also verify the integrity of the assets they serve to protect your users.
Business impact
A compromised third-party tool directly exposes a company's customers to data theft, creating significant legal, financial, and reputational risk. This incident forces businesses to re-evaluate the security posture of their vendors and the hidden liabilities within their software supply chain.
⚡ Action needed
Review your site's third-party scripts and implement security controls.
Action checklist
- 1Audit all third-party JavaScript running on your web properties.
- 2Investigate if your organization uses Optimizely or other A/B testing tools.
- 3Implement or strengthen your Content Security Policy (CSP) to limit script execution.
- 4Consider using Subresource Integrity (SRI) for critical external scripts.
- 5Monitor for unusual outbound network traffic from your website.
Tags
Related on Notifire
Related stories
Primary source: BleepingComputer
