Cyberattack Through Optimizely Hits 178 Major Websites, Including BBC, CNN and HSBC

 

Cyberattack Through Optimizely Hits 178 Major Websites, Including BBC, CNN and HSBC

Illustrative image: a laptop screen glowing with warning code in a dark room, with a smartphone beside it.

Malicious code planted inside the Optimizely web experimentation platform reached visitors to the websites of 178 major organisations on Monday, November 16, 2026 — including Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock.

Security researcher Scott Helme, of the firm Report URI, found the campaign and published a detailed analysis on Monday. He checked 1,611 Optimizely scripts and found 188 infected, belonging to 178 organisations.

Optimizely has confirmed the incident. The company said an unauthorised party exploited a vulnerability in its Experimentation product and used it to add malicious JavaScript to some customer projects. It said it has fixed the vulnerability, removed the injected code, secured affected user accounts and notified affected customers.

How the attack worked

Optimizely Web works by having each customer load a JavaScript "snippet" from cdn.optimizely.com, which includes an optional field called Project JavaScript that runs first and can affect every experiment in a project. The attacker wrote a small loader into that field and left the rest of the snippet untouched, so the file was still served from Optimizely's domain with Optimizely's certificate, and browsers and security tools treated it as normal.

In Zoom's snippet, the added code quietly created a new script tag that pulled a file called track.js from the domain 1688360.cc. Report URI found three versions of the loader, including one hidden in base64 code. None of the affected websites had to be hacked directly: the malicious code came through a trusted third-party script that each site loaded on every page, and the snippets for Optimizely's own sites, including login.optimizely.com, also carried it. The first injection was recorded at 04:21 UTC on November 16 in the BBC's snippet, and the malicious code was live for roughly 17 hours in total.

What the malware did

The payload was a multi-purpose kit. Its crypto clipper scanned each page for wallet addresses on Bitcoin, Ethereum and other major cryptocurrencies, and swapped them for attacker-controlled addresses in page text, in the clipboard and in outgoing web requests. By 19:25 UTC, the attackers' wallets had received about $7,040 in cryptocurrency, according to Report URI.

A card skimmer, added at 13:43 UTC, watched form submissions for a card number, expiry date and CVV, then sent the details to the attackers' server. Cards typed into a site's own form fields were exposed. Cards entered into hosted payment frames such as Stripe or Adyen were out of its reach. The script also sent page addresses, readable cookies and screenshots of pages to the attackers.

On Apple mobile devices, the script loaded exploit kits for iPhones and iPads: Coruna for iOS 13 to 17, and DarkSword for iOS 18. A separate chain for iOS 26 only fingerprinted the device.

What happened next

Most of the malicious code was gone by 21:52 UTC on Monday, when only TalkTalk's snippet was still infected, down from 169 at 20:56 UTC. Optimizely told BleepingComputer that an unauthorised party exploited a vulnerability in the Experimentation account signup flow, and said it blocked the vulnerable path, deployed a fix, removed the injected code and notified all affected customers. Report URI said it does not know how the attacker got write access to so many unrelated customer projects, and said it had ruled out poisoning of the CDN cache.

What users and website owners should do

Users should update to iOS 18.7.3 or later, or iOS 26.3 or later. Anyone who visited one of the affected sites on Monday, November 16, and copied a crypto wallet address from it should check the address they actually pasted before sending anything, and check card statements from that day.

Website owners that use Optimizely should open every Project JavaScript field and every experiment's custom code, and look for 1688360.cc and any script they did not write. Teams should review users, API tokens and integrations, then rotate their credentials.

What to watch next

  • Whether any further infections are found, and whether the attackers' infrastructure is taken down.
  • How much money was ultimately stolen, and how many people were affected.

Sources: Report URI analysis by Scott Helme, "World's Largest Brands Infected With Malware Via Optimizely", November 16, 2026; Cyber Security News, November 17, 2026; Optimizely status page and statement, November 17, 2026; BleepingComputer reporting via The CyberSec Guru, November 17, 2026.

>

Comments

Popular posts from this blog

Senate Blocks Iran War Powers Resolution in 48–51 Vote, Backing Trump

Canadian Home Sales Down 10.6% From a Year Ago in October, CREA Reports

Mary Peltola Flips Alaska Senate Seat, Defeating Dan Sullivan