NEWS

Optimizely Supply Chain Attack Injects Card Skimmer and Crypto Swapper Into 178 Organizations' Scripts

Attackers abused Optimizely's signup flow to plant malicious JavaScript that loaded on CNN, BBC, Salesforce and Zoom, skimming cards and swapping crypto wallets.

Dylan H.

News Desk

November 17, 2026
2 min read
Optimizely Supply Chain Attack Injects Card Skimmer and Crypto Swapper Into 178 Organizations' Scripts

Overview

On November 16, 2026, attackers exploited a vulnerability in the account signup flow of Optimizely's Experimentation platform and injected malicious JavaScript into customer projects. Because many sites load Optimizely snippets directly, the code ran in visitors' browsers on high-profile properties.

Researcher Scott Helme analyzed 1,611 scripts and found 188 infected Optimizely JavaScript files belonging to 178 organizations. BleepingComputer confirmed through urlscan.io that sites including CNN, Fox News, BBC, Salesforce, Zoom, GitLab, KLM and Air France loaded or attempted to load the malicious script.

What the Script Does

  • Pulls a second-stage payload from a remote track.js file. Some copies hide the URL with Base64, and one variant embeds a fallback copy in case the remote file is blocked.
  • Replaces cryptocurrency wallet addresses shown on a page with attacker-controlled ones.
  • Skims card numbers, expiry dates and security codes entered on a page and tries to send them to an attacker server.
  • Delivers the Coruna and DarkSword iOS exploit kits to iPhones and iPads.
  • Can collect cookies, page URLs and screenshots.

Helme found wallets tied to the script had received about $7,000 as of November 16. Some wallets were active before the attack, so the real amount stolen is unclear.

Response

Optimizely blocked the vulnerable path, deployed a fix, removed injected code from affected projects, ended active sessions, revoked tokens and reset access for affected accounts. It also blocked delivery of the malicious code through Cloudflare and notified customers, with updates on its status page. Salesforce disabled Optimizely scripts across preview and production instances as a precaution.

By 21:52 UTC on November 16, only one of the 188 infected files still contained malicious code. The earliest injection was seen early that morning. How long the flaw existed and how many visitors were exposed are not yet known.

Recommendations

  • Visitors: If you used an affected site on November 16, check recent crypto transfers for swapped destination addresses and watch card statements for unauthorized charges. Update iOS and iPadOS.
  • Site owners: Inventory third-party scripts, enforce a Content Security Policy with strict script-src and connect-src rules, and use Subresource Integrity where a vendor allows pinned files.
  • Optimizely customers: Review your project snippets for unfamiliar code or Base64 strings and rotate tokens and credentials.

Sources