
Download the Full Advisory (PDF)
The CRITICALSTART® Cyber Research Unit (CRU) is tracking OPTIMJACK, a client-side supply chain compromise in which an unauthorized party injected malicious JavaScript into customer projects on the Optimizely Web Experimentation platform on November 16, 2026.[1, 3, 4] Visitors to the websites of at least 178 organizations across banking, technology, retail, media, travel, and healthcare received a payload that swapped cryptocurrency wallet addresses, skimmed payment cards, stole cookies and page screenshots, and routed iPhone and iPad visitors to the Coruna and DarkSword iOS exploit kits.[1, 2] Optimizely confirmed an exploited vulnerability in Experimentation and states it is fixed.[3] OPTIMJACK is the third major third-party JavaScript compromise reported since late August 2026, following the Plerdy analytics and Polymarket incidents.[5, 7] Organizations that embed third-party scripts should verify what those scripts delivered, rotate exposed session tokens, and enforce a restrictive Content Security Policy (CSP). Critical Start Security Operations Center (SOC) has increased vigilance for malicious activity based on the indicators of compromise in the full advisory and Security Engineering is reviewing detection coverage for the threat.
Optimizely Web lets customers run A/B tests by loading a JavaScript snippet on their pages. On November 16, that snippet carried attacker code for most of the day.[1] The OPTIMJACK campaign affected 178 organizations across 20 sectors, based on 188 affected snippets identified among 1,611 checked. Banking and finance organizations accounted for the largest share, with 32 affected entities, followed by the technology sector with 23. The campaign remained active between 04:21 and 21:52 UTC on November 16, 2026, with researchers identifying 26 different payload builds. Confirmed cryptocurrency theft reached approximately $7,040 by 19:25 UTC, while the total volume of stolen payment card details and browser cookies remains unknown. Optimizely confirmed the vulnerability and states it is fixed but has not disclosed its nature or how many projects were affected.[3, 4] Report URI links the actor to an earlier wave through other third-party scripts from November 13.[1] No public reporting connects OPTIMJACK to Optimizely's February 2026 voice-phishing incident.[14]
OPTIMJACK introduced no new techniques but chained five established threat categories into one delivery path, as summarized below:
1688360[.]cc/track.js, a Base64-encoded copy that defeats string searches, and an inline eval() fallback. One snippet was reinfected after cleanup.[1]However, the DarkSword chain served to iOS 18.x visitors relies on six patched vulnerabilities.[9, 10] Common Vulnerability Scoring System (CVSS) scores appear where published in the sources reviewed. Coruna, served to iOS 13 to 17 visitors, contains five chains and 23 exploits. The Cybersecurity and Infrastructure Security Agency (CISA) added three of its vulnerabilities (CVE-2021-30952, CVE-2023-41974, and CVE-2023-43000) to the Known Exploited Vulnerabilities catalog.[11]
| CVE | CVSS | Description | Relevance |
|---|---|---|---|
| CVE-2025-31277 | 8.8 | Processing maliciously crafted web content may lead to memory corruption; patched in iOS 18.6 | DarkSword initial read/write primitive[9, 15] |
| CVE-2025-43529 | 8.8 | A use-after-free issue was addressed with improved memory management; exploited as zero-day | DarkSword initial read/write primitive[10] |
| CVE-2025-14174 | 8.8 | ANGLE memory corruption; exploited as zero-day | DarkSword WebKit stage[10] |
| CVE-2025-43510 | 7.8 | Memory corruption issue addressed with improved lock state checking | DarkSword privilege escalation[10] |
| CVE-2025-43520 | 5.5 | Memory corruption issue; patched in iOS 26.1 and 18.7.2 | DarkSword privilege escalation[9] |
| CVE-2026-20700 | 7.8 | Memory corruption issue; patched in iOS 26.3 after zero-day exploitation | DarkSword chain component[9] |
The mapping below, drawn from the MITRE Adversarial Tactics, Techniques, and Common Knowledge (ATT&CK) framework, describes behaviors that are in scope:[5]
| Technique | Name | Context |
|---|---|---|
| T1195.002 | Supply Chain Compromise: Compromise Software Supply Chain | Loader injected into Optimizely customer projects and served to downstream sites |
| T1189 | Drive-by Compromise | Visitors infected by loading affected pages; iOS chains delivered in hidden iframes |
| T1059.007 | Command and Scripting Interpreter: JavaScript | track.js and boot.js executed in visitor browsers |
| T1592 | Gather Victim Host Information | iOS version and device fingerprinting before exploit selection |
| T1203 | Exploitation for Client Execution | Coruna and DarkSword WebKit and kernel exploit chains |
| T1115 | Clipboard Data | Clipboard monitoring for wallet addresses |
| T1565.002 | Data Manipulation: Transmitted Data Manipulation | Wallet address replacement in outgoing requests and navigation |
| T1056.003 | Input Capture: Web Portal Capture | Card number, expiry, and CVV capture from site forms |
| T1539 | Steal Web Session Cookie | Exfiltration of non-HttpOnly cookies |
| T1113 | Screen Capture | html2canvas rendering of the page |
| T1027 | Obfuscated Files or Information | Base64-encoded loader and inline eval() fallback |
| T1041 | Exfiltration Over C2 Channel | sendBeacon transfers to card.php and hit.php |
The OPTIMJACK campaign poses significant financial, operational, and reputational risks to organizations that rely on third-party JavaScript and website integrations. Malicious scripts can replace cryptocurrency wallet addresses, capture payment card details, and collect sensitive information entered through legitimate webpages, potentially exposing customers to financial theft and data breaches. The campaign also highlights third-party supply chain risks, as attackers can abuse trusted services such as Optimizely to inject malicious code without directly compromising an organization's primary infrastructure. Successful exploitation could damage customer trust, trigger regulatory investigations, and create potential compliance and breach notification obligations. Device-selective loading and conditional script execution further complicate detection and incident response, allowing malicious activity to remain hidden during routine security checks. Organizations should review third-party scripts and integrations, monitor suspicious DNS and browser connections, verify script integrity, and investigate potential exposure of customer and payment information.
To improve your organization's security posture considering OPTIMJACK exploitation, CRU recommends the following:
1688360, atob(, eval(, and unfamiliar scripts; ask Optimizely which project IDs changed.[1, 4]cdn.optimizely[.]com or its associated IP addresses; it is a legitimate delivery host observed in the chain, not attacker infrastructure.script-src hosts, restrictive connect-src, no 'unsafe-eval', and reporting.[1]OPTIMJACK demonstrates how compromising a single trusted third-party provider can expose hundreds of organizations and their customers to financial theft, session hijacking, and potential mobile device exploitation. The campaign highlights the limitations of perimeter-based defenses when malicious code executes directly in users' browsers through legitimate website integrations. Organizations should treat third-party JavaScript as an extension of their attack surface, not an inherently trusted component. Reviewing historical script activity, revoking potentially exposed credentials, strengthening Content Security Policy enforcement, and continuously monitoring client-side script integrity are essential to reducing exposure. Ultimately, preventing similar incidents requires greater visibility and control over the external code organizations allow to execute on their websites.
For more threat reports, including PHP2SHELL visit Critical Start's Intel Hub. This advisory was written using the best intelligence available at the time and is subject to change as additional information becomes available.
To learn how Critical Start can help you detect, investigate, and respond to threats faster, connect with a Critical Start team member.
Get Started →