On November 16, 2026, a sophisticated supply-chain attack was discovered, affecting 178 globally recognized organizations. Threat actors compromised the Optimizely Web experimentation platform to inject malicious JavaScript into the websites of major brands like CNN, BBC, Zoom, and Salesforce. The malware was a multi-purpose toolkit capable of stealing financial information, hijacking cryptocurrency transactions, and deploying exploit kits against vulnerable mobile devices. The attack leveraged the trust placed in third-party scripts, demonstrating a critical vector for widespread compromise. While remediation efforts were swift, the incident exposed thousands of users to data theft and further infection.
The attack was not a direct breach of the 178 affected companies but a compromise of a shared third-party service, Optimizely. Attackers exploited a weakness in Optimizely's platform to add malicious JavaScript to the projects of their customers. This script was then served to website visitors from Optimizely's legitimate content delivery network (CDN) at cdn.optimizely.com, making it difficult to block without disrupting legitimate site functionality.
Once a visitor's browser loaded an affected page, the malicious script would execute and connect to an attacker-controlled domain, 1688360[.]cc/track.js, to fetch the primary payload. This payload was a versatile malware with three main functions:
The attack timeline shows rapid execution, with the malicious script being injected and activated on major sites like bbc.com within a few hours on November 16.
The attack chain began with the compromise of customer accounts on the Optimizely platform. The threat actors used this access to inject a malicious script loader into the target websites' Optimizely snippets. This loader was often obfuscated using Base64 encoding to evade initial detection.
The loader's primary function was to fetch the main payload from 1688360[.]cc/track.js. This external script contained the logic for the skimming, crypto clipping, and exploit delivery operations. The use of a legitimate, trusted CDN for the initial script delivery is a key element of this supply-chain attack, falling under MITRE ATT&CK technique T1190 - Exploit Public-Facing Application by abusing the functionality of the Optimizely service.
The subsequent loading of malware onto the visitor's browser is a classic T1189 - Drive-by Compromise. The malware itself used T1059.007 - JavaScript for execution within the browser context. Data theft, including payment card information and cookies, aligns with T1555.003 - Credentials from Web Browsers. The cryptocurrency address swapping is a form of T1565.002 - Transmitted Data Manipulation.
The business impact of this attack is multi-faceted. For the 178 affected organizations, the primary damage is reputational. Having their websites serve malware erodes customer trust, even if their own servers were not breached. Companies like Salesforce and Equifax had to temporarily disable Optimizely scripts, potentially impacting their marketing and A/B testing operations.
For end-users who visited the compromised sites, the impact is more direct. They face the risk of financial loss from stolen credit card details and hijacked cryptocurrency payments. The attack reportedly netted the criminals over $7,000 in cryptocurrency in a short period. Furthermore, users with outdated iOS or iPadOS devices were at risk of full device compromise from the Coruna and DarkSword exploit kits. This could lead to the theft of sensitive personal data, account credentials, and further malware installation.
1688360[.]cc1688360[.]cc/track.jscdn.optimizely.comSecurity teams may want to hunt for the following patterns to detect similar activity:
track.js1688360[.]ccbase64 -d*.jsDetecting this type of attack requires monitoring the integrity and behavior of third-party scripts loaded on web properties.
D3-ITF: Inbound Traffic Filtering countermeasure.D3-NTA: Network Traffic Analysis is key here.For response, if a compromise is suspected, immediately disable the integration with the compromised third-party service. Isolate affected web properties and begin an investigation to determine the scope of the compromise and which users were impacted.
Preventing supply-chain attacks that abuse third-party scripts requires a defense-in-depth approach.
Harden category.M1021): Use technical controls like CSP and SRI as a primary defense. This is a critical hardening step.M1051 - Update Software.M1047): Periodically audit all external scripts running on your websites to identify any unauthorized or modified code.Implement a strong Content Security Policy (CSP) to prevent browsers from executing scripts from untrusted domains.
Ensure end-user devices, especially mobile devices, are patched and running the latest OS versions to protect against exploit kits.
Regularly audit and monitor third-party scripts and their behavior on web properties to detect unauthorized changes or malicious activity.
While not a direct defense, training users to be cautious of unexpected website behavior and to report it can aid in early detection.
In the context of this Optimizely attack, Inbound Traffic Filtering should be implemented at the client-side using a robust Content Security Policy (CSP). A well-configured CSP acts as a filter, instructing the user's browser on which sources of content (scripts, styles, images) are trusted and can be loaded. For this specific threat, the CSP should explicitly whitelist cdn.optimizely.com but, more importantly, deny all other unknown script sources by default (e.g., using script-src 'self' cdn.optimizely.com). This would have prevented the browser from connecting to the malicious domain 1688360[.]cc to download the track.js payload, effectively breaking the attack chain at a critical step. Organizations should deploy CSPs in report-only mode first to identify all necessary domains, then move to enforcement mode. This technique shifts the defense to the browser, providing a crucial layer of protection against compromised third-party scripts.
To detect and respond to attacks like the Optimizely compromise, organizations should employ Network Traffic Analysis focused on client-side egress traffic. Security teams should use web proxy logs, DNS logs, and NetFlow data to monitor for connections from internal user devices to suspicious or newly observed domains. In this incident, a rule to alert on any connection to the domain 1688360[.]cc would have immediately flagged compromised users. More proactively, security teams can establish a baseline of normal domains contacted by third-party scripts (like those from Optimizely) and alert on deviations. Analyzing traffic for patterns like a high volume of requests for a specific .js file from an unusual domain can also serve as an early warning indicator of a potential supply-chain attack in progress.
The delivery of the Coruna and DarkSword exploit kits targeting older iOS and iPadOS versions underscores the importance of rigorous software update policies. Organizations must enforce policies requiring all managed devices, including mobile phones and tablets, to be on the latest OS and application versions. Mobile Device Management (MDM) solutions should be configured to automatically push updates or, at a minimum, alert on non-compliant devices and restrict their access to corporate resources until they are patched. This D3FEND technique directly mitigates the impact of the exploit delivery phase of the attack. Even if a user visits a compromised site, a fully patched device would not be vulnerable to the exploit kits, preventing device compromise and subsequent data theft.
A clean version of the BBC's Optimizely snippet was captured.
A version of the BBC's snippet with the malicious injection was observed.
The main malicious payload was observed loading on bbc.com.
Report URI discovers and reports the widespread supply-chain attack.
Affected companies like Salesforce begin disabling Optimizely scripts to mitigate.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.