Optimizely Hack Put a Card Skimmer on Zoom and BBC Sites: What to Do

A hijacked Optimizely script ran a card skimmer and iPhone attack code on 178 sites, including Zoom and the BBC, on 16 November. Who is at risk and what to do.

Clurky News DeskNov 19, 20265 min read
OPTIMJACK graphic: Optimizely script icon pointing to a card and wallet
Graphic showing Optimizely scripts loading a skimmer that targets cards and crypto wallets. Image: StepSecurity

For about 16 hours on most affected sites, starting on 16 November (Philippine time), a hijacked Optimizely script ran a card skimmer, a crypto-wallet swapper and iPhone attack code on the websites of 178 organizations, including Zoom, the BBC, CNN and HSBC. If you entered a card number or copied a crypto wallet address on a big-brand website that day, it is worth checking.

The attack was found by security researcher Scott Helme of Report URI and traced in detail by StepSecurity, which calls the campaign OPTIMJACK. The code has since been removed.

What is Optimizely, and how did one tool reach 178 websites?

Optimizely is a service that companies use to test changes to their websites, for example showing two versions of a page to see which one gets more clicks. To do that, each website loads a small piece of code (a script) from Optimizely's servers at cdn.optimizely.com on every visit.

Each customer's script includes a field called Project JavaScript, where the company can add its own code. According to StepSecurity, the attacker wrote malicious code into that field for many unrelated customers at once. Optimizely's servers then delivered it to every visitor, as they normally would. Visitors' browsers trusted it because it came from the same address the sites always use.

In his write-up, Helme shows Zoom's website loading its script from Optimizely's servers. This kind of attack is called a supply-chain attack: the attacker breaks into a supplier, not the website itself.

Optimizely has confirmed that "an unauthorized party exploited a vulnerability" in its Experimentation product, StepSecurity reports. The company says it fixed the flaw, removed the code, ended active sessions, reset affected accounts and notified customers. It has not explained how the attacker could write to so many customers' projects.

What did the malicious code do?

StepSecurity's analysis found four parts:

  • Crypto wallet swapper. When you copied a wallet address for Bitcoin, Ethereum, Solana and five other coins on an affected page, the code quietly replaced it with the attacker's address.
  • Screenshot and cookie theft. After a swap, it captured the visible page and sent it, with the site's cookies, to the attacker.
  • Card skimmer. It captured card numbers, expiry dates and CVV codes typed into checkout forms. It could not read payment boxes hosted by a separate payment company inside the page.
  • iPhone and iPad attack code. On Apple devices it loaded a second stage linked to two known exploit kits, Coruna (aimed at iOS 13 to 17) and DarkSword (iOS 18). StepSecurity did not analyse these files, so whether they worked is not confirmed.

When was the code live, in Philippine time?

From StepSecurity's timeline, converted to Philippine time (PHT):

  • 12:21 PM, 16 November: first injection, on a BBC page.
  • 9:43 PM, 16 November: card skimmer added.
  • 11:06 PM, 16 November: Report URI's system flags the first malicious activity.
  • 4:40 AM to 5:10 AM, 17 November: mass cleanup of the scripts.
  • 7:11 AM, 17 November: Helme reports all files clean.

Which websites carried the code?

StepSecurity lists CNN, the BBC, Fox News, Zoom, Salesforce, GitLab, HSBC, KLM, IKEA, Equifax, Ledger and Peacock, plus Optimizely's own sites. By sector, 32 were in banking and finance, 23 in technology, 20 in retail, 12 in streaming, 9 in airlines and travel, and 7 in telecoms.

Being on the list means the code was served on the site. It does not mean every visitor lost data.

Was I affected, and what should I do?

You are most at risk if you typed a card number or copied a crypto address on one of these sites between about noon on 16 November and 5 AM on 17 November (PHT). In that case, StepSecurity advises replacing the card and checking wallet addresses on a hardware wallet screen. Everyone else should mainly update their iPhone.

What to do:

  1. Card used on an affected site in that window: call your bank or card issuer, ask to block and replace the card, and check recent transactions.
  2. Crypto sent that day: compare the address you sent to with the one you meant to use.
  3. iPhone or iPad: go to Settings > General > Software Update and install the latest version, following Apple's update steps. StepSecurity says devices on iOS 18.6 or older that visited affected sites deserve a closer check.

How much was stolen?

Helme estimated the attacker's crypto take at $7,040 (around ₱448,500) as of 16 November, while Galaxy Digital's Alex Thorn put victim payments at about $2,300 (around ₱146,500), StepSecurity reports. Stolen card numbers and cookies leave no public record, so the real cost is unknown.

Why does this keep happening?

Helme argues that websites load too much outside code without checking it. He recommends removing third-party scripts a site does not need, recording when a script changes, and using a Content Security Policy, a browser rule that limits where a page may load code from. If you run a website, the same habit applies to your own software: our guide on checking whether a PHP website is patched covers one example.

Sources

  1. StepSecurity
  2. Scott Helme: Reflecting on the Optimizely incident
  3. Apple Support: Update your iPhone or iPad
ShareFacebookXLinkedInWhatsAppRedditEmail
Clurky News Desk

News and guides from Clurky. Every article is checked against its sources before it is published. Clurky is owned and run by Argal, who sets its editorial standards.

Comments

Log in to leave a comment.

Log in