As reported by SecurityAffairs, the OPTIMJACK campaign represents one of the most consequential supply chain compromises of 2026, with attackers injecting malicious JavaScript through Optimizely's Web Experimentation platform into 178 organizations' websites — including some of the highest-traffic properties on the internet.

Threat Alert: As reported by SecurityAffairs, the OPTIMJACK campaign represents one of the most consequential supply chain compromises of 2026, with attackers injecting malicious JavaScript through Optimizely's Web Experimentation platform into 178 organizations' websites — including some of the highest-traffic properties on the internet.

Why This Matters: The CDN Trust Problem

This incident exposes a structural weakness that most enterprises have failed to address: third-party scripts loaded from trusted CDN domains bypass virtually every browser-based security control. The malicious code in OPTIMJACK was served from cdn.optimizely.com with Optimizely's valid TLS certificate, meaning Content Security Policy (CSP) headers that whitelist Optimizely's domain — as most affected sites do — provided zero protection.

The attack surface here is enormous. Optimizely Web Experimentation is used by thousands of sites to A/B test content changes. The platform's Project JavaScript feature allows customer-specific code to run on every page load. By compromising the platform itself rather than individual customer accounts, the attackers achieved a force multiplier: a single intrusion propagated malicious code to 178 downstream victims simultaneously.

Multifaceted Payload: Beyond Simple Skimming

What sets OPTIMJACK apart from typical Magecart-style skimming is the breadth of its payload:

Why This Matters: The CDN Trust Problem
Cryptocurrency wallet address hijacking — swapping destination addresses during transactions, with verified on-chain transfers to attackers
Payment card skimming — traditional formjacking targeting checkout flows
Credential and session theft — cookie exfiltration enabling session hijacking
Screenshot capture — potential for capturing sensitive on-screen data
iOS exploit delivery — deploying Coruna and DarkSword exploit kits against iPhone and iPad visitors

The inclusion of iOS exploit chains elevates this from financial crime to potential espionage territory. The targeting of Ledger (a hardware wallet manufacturer) alongside major financial institutions like HSBC and Equifax suggests deliberate targeting of high-value cryptocurrency and financial data.

Who Is Most at Risk

Any organization using Optimizely Web Experimentation was exposed, but the risk profile varies dramatically:

  • Financial services and crypto platforms — direct financial loss via wallet hijacking and card skimming
  • Media organizations — massive visitor volume means broad malware distribution even if per-user value is lower
  • E-commerce and SaaS platforms — checkout and authentication flows were directly targeted
  • Mobile-first audiences — iOS exploit delivery creates persistent device compromise for affected users

Shield53 Recommendations

Immediate Actions

  • Verify remediation status with Optimizely — confirm that your Project JavaScript snippets have been cleaned and the underlying vulnerability is patched in your environment
  • Audit all third-party scripts — not just Optimizely. Review Subresource Integrity (SRI) hashes for all externally-loaded JavaScript and implement SRI where supported
  • Review CSP policies — move from domain-based whitelisting to hash-based or nonce-based CSP for third-party scripts. Domain allowlists are insufficient against this attack class
  • Hunt for indicators of compromise — search web server and CDN logs for anomalous outbound connections from client browsers, unexpected POST requests to unknown domains, and patterns consistent with card skming or wallet address injection
  • Notify affected users — for organizations with known exposure, issue security advisories recommending users check crypto transaction histories, rotate session cookies and passwords, and update iOS devices

Structural Changes

  • Implement a third-party script inventory and approval process — know exactly what external code runs on your properties and who controls it
  • Adopt Subresource Integrity for all third-party resources where technically feasible
  • Deploy client-side runtime protection — solutions that monitor DOM mutations and form submissions in real time can detect skimming behavior regardless of source
  • Establish vendor security requirements for SaaS providers whose code executes on your domains — including incident notification timelines and right to audit
The OPTIMJACK campaign demonstrates that the third-party script trust model is fundamentally broken when a single vendor compromise can simultaneously impact BBC, CNN, Zoom, and Equifax. Organizations must stop treating CDN-served JavaScript as inherently trustworthy simply because it comes from a known domain.

Optimizely's disclosure has been notably sparse — they have not disclosed the nature of the vulnerability, the timeline of attacker access, or whether the attacker retains any residual access. Until these questions are answered, Shield53 recommends treating this as an active threat requiring continuous monitoring rather than a resolved incident.