Security & privacy

Optimizely supply chain attack injected skimmers into CNN, BBC and Zoom sites

Attackers exploited Optimizely Web Experimentation to inject malicious JavaScript into customer snippets, serving card skimmers and iOS exploit kits to visitors of major sites including CNN, BBC and Z

A broken glass cube leaking dark code onto a desk with circuit boards.
Illustration generated for this article

A critical supply chain compromise hit Optimizely Web Experimentation on Monday, allowing attackers to inject malicious code into scripts served to visitors of at least 178 organizations. Major platforms including CNN, the BBC, Zoom, Salesforce and IKEA were affected as the attacker leveraged a vulnerability in the experimentation platform to modify customer project configurations. The incident exposed users to crypto wallet address swapping, credit card skimming and attempted iOS device exploitation before Optimizely remediated the flaw.

What happened

The attack began at 04:21 UTC on Monday when the first injection appeared in the BBC’s Optimizely snippet. Over the following hours, the attacker modified the Project JavaScript field within customer projects to load a malicious loader script. Report URI, a firm that monitors web scripts, identified infected snippets belonging to 178 distinct organizations. The compromised code was served directly from cdn.optimizely.com, meaning it carried the vendor’s valid security certificate and bypassed many standard trust checks. Even sites that hosted the snippet on their own domains were affected because the content originated from the same vulnerable project configuration.

The malicious payload evolved throughout the day. Initially, it focused on replacing cryptocurrency wallet addresses with those controlled by the attacker. Later, at 13:43 UTC, a card skimmer was added to capture payment details entered into form fields. For mobile users, the code attempted to load secondary exploit kits targeting iOS devices. Optimizely issued an incident notice at 01:02 UTC the following day, stating that it had fixed the vulnerability, removed the malicious code and secured affected accounts. A mass cleanup effort concluded by 21:52 UTC on Monday, though some sites like TalkTalk remained infected slightly longer.

How it works

Optimizely Web Experimentation allows companies to test different versions of their web pages by loading a JavaScript snippet. This snippet updates automatically when settings change and executes custom code defined in the Project JavaScript field. The attacker gained write access to this field across multiple unrelated customer projects, inserting a loader that fetched external malicious scripts. The loader existed in three variants: one that directly fetched a payload from 1688360[.]cc, one that hid the destination using base64 encoding to evade text searches, and one that contained a full copy of the payload to execute if the external domain was blocked.

Once executed, the payload performed several actions depending on the user’s device and behavior. It scanned page text, forms and clipboard data for cryptocurrency wallet addresses near keywords like "wallet" or "send," replacing valid addresses with the attacker’s after verifying the checksum. It also captured credit card numbers, expiry dates and CVVs from standard form fields, though it could not read data entered into cross-origin iframes such as those used by Stripe or Adyen. On iOS devices, the code attempted to load exploit kits named Coruna and DarkSword via hidden iframes, targeting specific iOS versions to potentially gain deeper system access.

Key details

  • At least 178 organizations were affected, including CNN, the BBC, Zoom, Salesforce, GitLab, IKEA, HSBC and Equifax.
  • The attack exploited a vulnerability in Optimizely Web Experimentation to inject malicious JavaScript into the Project JavaScript field of customer projects.
  • Malicious code was served from cdn.optimizely.com with a valid certificate, making detection difficult for standard security tools.
  • The payload included a crypto wallet address swapper, a credit card skimmer and iOS exploit kits (Coruna and DarkSword) targeting iOS 13 to 18.7.
  • Approximately $7,040 in cryptocurrency was stolen within nine hours, though the total number of compromised cards remains unknown.
  • Optimizely has fixed the vulnerability and removed the code, but some customers may need to rotate credentials and audit their configurations.

Why it matters

This incident highlights the severe risks inherent in third-party JavaScript dependencies. Because the malicious code was served from a trusted domain with a valid certificate, traditional network security measures often failed to flag it. For engineering teams, this underscores the importance of monitoring not just the availability of third-party services but the integrity of the code they deliver. The ability of a single vulnerability in a SaaS platform to compromise hundreds of high-profile websites demonstrates how supply chain attacks can scale rapidly and bypass perimeter defenses.

For developers building products that handle sensitive user data, this event serves as a reminder that client-side security is complex and fragile. The attacker’s use of base64 encoding to hide domain names and the conditional loading of exploits based on iOS versions show a sophisticated understanding of evasion techniques. Teams must assume that any third-party script running on their site has full access to the DOM and user inputs, necessitating strict controls on what code is allowed to execute and how data is handled in the browser.

What you can do

  • Audit all Optimizely projects by checking the Project JavaScript field and experiment custom code for unfamiliar scripts, specifically looking for "1688360", "atob(" or unauthorized domains.
  • Rotate credentials for all users, API tokens and integrations with write access to your Optimizely account to ensure no persistent access remains.
  • Implement a strict Content Security Policy (CSP) with specific script-src and connect-src directives, avoiding unsafe-eval or strict-dynamic which can allow malicious payloads to run.
  • If your site accepts card payments, treat transactions from Monday as potentially compromised and monitor for fraud, especially if you do not use cross-origin iframes for payment processing.
  • Advise users who visited affected sites to update their iOS devices to version 18.7.3 or later, or iOS 26.3 or later, to patch the targeted vulnerabilities.
  • Block known malicious indicators such as the domain 1688360[.]cc and associated IP addresses in your firewall and endpoint protection systems.
  • #supply chain security
  • #javascript
  • #web security
  • #optimizely
  • #ios exploits

Tools from the Bytechap store

Keep reading

All stories