If your website loads a vendor’s JavaScript, that vendor can run code in your customers’ browsers, and an attacker who reaches the vendor’s hosted files can do the same. That is the lesson of the Optimizely incident, where scripts served on well-known sites tried to swap crypto wallet addresses, skim card details and attack iPhones. Security teams should check their own third-party script inventory now.

What happened

According to BleepingComputer, researcher Scott Helme reported on Monday that 188 JavaScript files belonging to 178 organizations were infected. His team arrived at that count after analyzing 1,611 scripts used by Optimizely, a platform companies use to test and personalize their sites. The altered files sat on Optimizely’s content delivery network and pulled in a further malicious script from a remote domain.

BleepingComputer checked urlscan.io records and found the malicious script loaded, or tried to load, on sites including Zoom, CNN, the BBC, Salesforce, GitLab, KLM and Air France. The scans show loading or attempted loading on those named sites, so they do not establish that every visitor was exposed. The payload reportedly replaced crypto wallet addresses with attacker-controlled ones, searched pages for card numbers and security codes, and loaded iOS exploit kits that Helme identified as Coruna and DarkSword. Helme saw about $7,000 in transactions to the embedded wallets on November 16.

Helme’s team also reported that cleanup had cut the number of infected files, with only one of the 188 still holding malicious code at 21:52 UTC on November 16. That is a single snapshot, not a final count. How the attackers modified so many customer projects remains unknown, and BleepingComputer has asked Optimizely for comment.

Why it matters

Nobody has yet explained how the attackers got in. It is unclear whether Optimizely’s infrastructure, stolen credentials or another route was involved, and the reports say nothing about whether any customers had weaknesses of their own. What is clear is that the altered code ran through a vendor’s delivery channel. This suggests the real exposure sits in the browser, where a marketing or experimentation tag runs with the same privileges as the site’s own code. Most organizations review backend dependencies far more closely than the scripts their growth teams add.

The mix of payloads also stands out. Wallet swapping and card skimming are direct monetization, while the iOS exploit kits point at device compromise. Combining these in one malicious script shows how valuable code that runs on many high-traffic sites can be to an attacker.

The pattern is familiar from our coverage of how one trusted tool can open a route into many victims, as in ScreenConnect abuse against MSP customers. Concentrated trust creates concentrated risk.

What it means for you

Start with an inventory. List every third-party script your public pages and checkout flows load, who owns each one and who can change it. If you use Optimizely, review your project files and any scripts served from its CDN for references to unfamiliar domains or Base64-encoded strings decoded at runtime.

Then add controls that limit the damage:

  • Tighten your Content Security Policy so pages can only connect to approved domains, which can block data leaving to an attacker’s server.
  • Keep third-party scripts off payment pages where you can, or isolate card fields in a hosted frame.
  • Monitor script content for changes, not just availability, and alert on new outbound destinations.
  • Search your web logs and CSP reports for the malicious domain named in BleepingComputer’s report.
  • Ask your vendors direct questions. How do they protect customer project access, do they enforce multifactor authentication, and how fast can they notify you of a change to hosted files? Add the answers to contract reviews.

    If your site was affected, consider notifying payment partners and customers, and advise staff to keep iOS devices updated. More guidance sits on our cybersecurity page.

    What to watch

    • Whether Optimizely explains how attackers reached so many customer projects, and whether credentials or infrastructure were involved.
    • Any rise in the number of affected organizations beyond the 178 Helme counted.
    • Further reports of card theft or device compromise tied to the injected script.
    • Similar hijacks at other script and personalization vendors.
    • Sources