The Supply Chain Attack That Compromised Giants Like CNN, Zoom, and Salesforce
On November 16, 2026, the cybersecurity landscape witnessed one of the most sophisticated and widespread client-side supply chain attacks in recent memory, dubbed “OPTIMJACK.” By injecting malicious JavaScript code into scripts hosted by the Optimizely platform, attackers successfully compromised the websites of 178 internationally renowned organizations. Among the affected entities are major corporations such as CNN, Zoom, Salesforce, Fox News, the BBC, IKEA, and HSBC. This incident highlights a critical vulnerability in how large enterprises rely on third-party tools, allowing external code to execute in end-user browsers without proper real-time inspection.
The Anatomy of the Web Injection
The primary vector of OPTIMJACK was not a direct breach of the affected companies’ infrastructure, but rather a manipulation of projects hosted on the Content Delivery Network (CDN) of Optimizely, a legitimate and widely used platform for web optimization and testing. Security firms confirmed that the CDN passively delivered the modified code it received, ruling out theories of a network cache poisoning event.
The attackers managed to insert a malicious loader pointing to external domains, such as 1688360[.]cc/track.js. Throughout the 17-hour main exposure window, the malicious code was rebuilt and updated up to 26 times, incorporating new features and cryptocurrency wallet addresses as the day progressed. This demonstrated a high level of tactical sophistication and active monitoring by cybercriminals, who exploited the implicit trust web administrators placed in the Optimizely domain.
The Four Threats of the Malicious Payload
The injected script functioned as a multipurpose toolkit designed to maximize data and capital theft from visitors, executing four primary malicious activities:
-
Cryptocurrency Swapping (Crypto Swapping): The code continuously scanned webpage text, forms, links, and the user’s clipboard for crypto wallet addresses. Upon detection, it replaced them within milliseconds with an attacker-controlled address. This tactic affected users of networks including Bitcoin, Ethereum, TRON, Solana, TON, Litecoin, and Dogecoin, tracking over $7,040 in initial illicit transfers.
-
Credit Card Skimming (Card Skimming): The script intercepted payment form submissions and outgoing requests, validating card numbers, expiration dates, and security codes (CVV) before exfiltrating them to the attacker’s servers.
-
Data Collection and Session Exfiltration: Under specific conditions, the malware captured active URLs, extracted readable cookies via JavaScript, and used hidden code to take screenshots of the rendered page, facilitating digital identity and user account theft.
-
Targeted Exploitation of iOS Devices: Upon detecting that a visitor was using an iPhone or iPad, the script inserted references that silently redirected the device to exploit kit infrastructure. Users with older, vulnerable versions (iOS 18.6 and earlier) experienced page reloads every 60 seconds while the server attempted to inject secondary payloads at the operating system level.
Global Impact and Content Security Policy Failures
The attack impacted multiple industries transversally, with the financial and banking sector hit hardest, counting 32 exposed organizations on the victim list. Optimizely confirmed the security incident, mitigated the vulnerability that allowed the injection, and removed the compromised code from client projects, stabilizing the threat by the night of November 16, 2026.
However, OPTIMJACK revealed a systemic flaw in how companies configure their Content Security Policies (CSP). When analyzing 256 hosts affected by the breach, researchers discovered that 68 corporate sites completely lacked CSP policies. Worse yet, in 50 cases where policies did exist, they allowed the malware to execute and data to leak because the main Optimizely domain was included in the permitted sender list. Blindly trusting a third-party vendor domain proved to offer zero protection when the attack originated directly from that trusted source.
Mitigation and Future Defenses
The OPTIMJACK incident serves as a striking reminder that corporate JavaScript code does not remain guaranteed harmless over time. For organizations, the lesson is clear: monitoring script behavior in real time within customer browsers is imperative. Detecting unusual behaviors, connections to new destinations, and access to sensitive data is required, rather than relying on static configurations that blanket-approve entire domains.
For users who browsed platforms like CNN, Zoom, or Salesforce during the attack window, defense relies on rigorous containment and verification practices:
-
Immediate System Update: Apple device users are advised to update their equipment to at least iOS 18.7.3 to close vulnerabilities exploited by the campaign.
-
Crypto Transaction Auditing: Those making crypto asset movements should visually verify the destination address through a secondary trusted channel or directly on a hardware wallet screen, assuming the operating system clipboard may be compromised.
-
Preventive Banking Monitoring: Users who entered credit card data on affected sites on November 16 should immediately review their statements and enable transaction notifications with their issuers to block any fraudulent charges.
The OPTIMJACK campaign will go down in history as a case study on how the integration of legitimate web tools can turn into the ultimate Trojan horse if dynamic security controls are not implemented across the software supply chain.
