Threat level Guarded
Submit a tip

Major threats, straight to your inbox

Only the threats that matter: actively exploited flaws, big breaches and attacks that need action. No spam, unsubscribe any time.

Optimizely Breach: Malware Hit Zoom, BBC, HSBC and 175 More

Optimizely breach: attackers injected card skimmers, crypto stealers and iPhone exploits into 178 sites incl. Zoom, BBC and HSBC. What to do now.

Optimizely Breach: Malware Hit Zoom, BBC, HSBC and 175 More

Threat card

Threat type
Supply Chain
Disclosed
Nov 16, 2026
Affected
Optimizely Web snippets of 178 organisations (188 snippets) on 16 Nov 2026, including Zoom, BBC, CNN, HSBC, Salesforce, GitLab, IKEA, Equifax and Crocs India; site visitors' cards, cookies, crypto transfers and unpatched iPhones

The short version

  • An attacker abused a flaw in Optimizely's Experimentation signup flow and injected malicious JavaScript into 188 Optimizely Web snippets of 178 organisations.
  • The payload swapped crypto wallet addresses, skimmed card data, stole cookies and screenshots, and served Coruna and DarkSword iOS exploit kits.
  • The code ran from cdn.optimizely.com with a valid certificate, so visitors saw no warning on brands like Zoom, BBC and HSBC.
  • Optimizely says it blocked the signup route, removed the code, revoked tokens and notified customers.

Last updated: 17 Nov 2026, 16:00 IST. This is a developing story.

Summary: The Optimizely breach let an attacker write malicious JavaScript into the Optimizely Web snippets of 178 organisations on 16 November 2026, including Zoom, the BBC, CNN, HSBC, Salesforce, GitLab, IKEA and Equifax. Visitors were exposed to a crypto wallet swapper, a payment card skimmer, cookie and screenshot theft, and iPhone exploit kits. Anyone who paid by card or sent crypto on an affected site on 16 November should check statements and treat that card as exposed.

The Optimizely breach is one of the largest web supply-chain attacks of 2026. Instead of hacking each brand, the attacker abused a flaw in Optimizely, the A/B testing and experimentation platform that many large websites load on every page, and pushed one malicious payload through Optimizely’s own CDN (cdn.optimizely.com) with a valid certificate. To a browser, the code looked like trusted first-party experiment code.

What happened in the Optimizely breach

The incident was first documented by Scott Helme of Report URI, a firm that monitors the scripts websites run. His team checked 1,611 Optimizely Web snippets and found malicious code in 188 of them, belonging to 178 organisations. Banking and finance made up the largest group, with 32 organisations, and HSBC sites in several markets (including the US, Hong Kong, Mexico, Singapore, Australia and the UAE) were on the list. Crocs India (crocs.in) also appeared.

Timeline (UTC, per Report URI and follow-up analysis):

  • 13 to 16 Nov: An earlier wave by the same actor reached sites through other third-party scripts (Kissmetrics, StorifyMe and Minute Media).
  • 16 Nov, 02:21: Last clean capture of the BBC’s Optimizely snippet.
  • 16 Nov, 04:21: First Optimizely injection seen, in the BBC snippet.
  • 16 Nov, 13:43: A payment card skimmer was added to the payload.
  • 16 Nov, 17:13 to 17:57: A second iOS host was added and a Coruna iframe was injected for visits from iOS 18.6 or earlier.
  • 16 Nov, 19:24 to 19:59: A sweep found 186 of 1,611 snippets infected.
  • 16 Nov, 21:52: Only one of the 188 compromised files still carried malicious code.

Report URI counted 26 rebuilds of the payload during the day, which shows the attacker was actively adding features and new wallets in real time.

How the attacker got in

Optimizely has said an unauthorised party exploited a vulnerability in the Experimentation account signup flow. The company says it blocked that signup route, shipped fixes, removed the malicious code from customer projects, revoked access tokens, ended active sessions and notified affected customers. Optimizely has not named the actor, and no group has claimed the attack so far.

Technical details

The payload was a multi-purpose kit, not a simple skimmer. Based on published analysis it did four things:

  • Crypto clipper: swapped cryptocurrency wallet addresses on the page for attacker wallets. Researchers counted roughly $7,000 received on 16 November.
  • Card skimmer: captured card number, expiry date and CVV on form submit and sent them to an attacker server.
  • Session and screen theft: collected cookies (any not marked HttpOnly) and screenshots.
  • iOS exploitation: read the iOS version and opened an exploit chain in a hidden iframe. Coruna was served to iOS 13 to 17, DarkSword to iOS 18, and a separate component only fingerprinted iOS 26 devices. Google researchers have documented Coruna with 23 exploits across five chains; DarkSword chains six bugs against iOS 18.4 to 18.7. Report URI says iOS 18.7.3+ and iOS 26.3+ are patched.

MITRE ATT&CK mapping: T1195 (Supply Chain Compromise), T1189 (Drive-by Compromise), T1203 (Exploitation for Client Execution), T1056.003 (Web Portal Capture), T1539 (Steal Web Session Cookie), T1113 (Screen Capture), T1565.002 (Transmitted Data Manipulation).

Published indicators (from public reporting on Report URI’s findings, verify before blocking):

  • eil786npto9u5bq.icu (34.87.36.58): iOS router and Coruna pages
  • l7bcsnwc7nzr3uo.icu: Coruna telemetry
  • Paths: /A8/ and /JIUJIU888/index.js (Coruna loader), /B9/, /D11/, /D12/ (DarkSword)

One useful finding: at HSBC, a Content Security Policy blocked the external track.js file and its data theft, but an inline copy still ran. CSP helped, but only partly.

Impact

Exposure covered card data, browser cookies, screenshots and crypto transfers for visitors on 16 November, plus device compromise risk for unpatched iPhones and iPads. Confirmed fraud totals and the number of affected users have not been published. Because the code was served from legitimate brand sites, ordinary users had no visible warning sign.

What security teams should do now

  1. Check if you use Optimizely Web. Review the Project JavaScript change history in Optimizely for any edits on 13 to 16 November you did not make, and confirm your snippet is clean today.
  2. Rotate Optimizely credentials and API tokens and review which users can edit Project JavaScript.
  3. Treat card data entered on 16 November as exposed. Notify your payment processor and consider PCI DSS incident steps if checkout pages loaded the snippet.
  4. Invalidate sessions and rotate any secrets stored in non-HttpOnly cookies.
  5. Hunt in proxy, DNS and CSP report logs for the domains and paths listed above.
  6. Push iOS updates through MDM to iOS 18.7.3+ or iOS 26.3+ and review devices that visited affected sites.
  7. Tighten third-party script controls: strict CSP with script-src allowlists, Subresource Integrity where possible, and continuous client-side script monitoring.

For consumers: watch bank and card statements, ask your bank for a new card if you paid on an affected site on 16 November, and confirm any crypto transfer address matched the one you intended.

What to do now

0 of 6 done

Questions readers ask

What is the Optimizely breach?

On 16 November 2026 an attacker abused a flaw in Optimizely's Experimentation signup flow and injected malicious JavaScript into the Optimizely Web snippets of 178 organisations, so their visitors received malware from trusted sites.

Which websites were affected by the Optimizely hack?

Named sites include Zoom, the BBC, CNN, Fox News, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, Peacock and Crocs India, among 178 organisations in total.

Was my card data stolen in the Optimizely breach?

Only if you entered card details on an affected site while the skimmer was live on 16 November (added at 13:43 UTC). If you did, treat the card as exposed and ask your bank for a replacement.

Are iPhones at risk from Coruna and DarkSword?

Unpatched iPhones and iPads were targeted. Update to iOS 18.7.3 or later, or iOS 26.3 or later, which Report URI says are patched.

Sources

  1. The Hacker News: Hijacked Optimizely scripts served card skimmer and iOS exploit kitsthehackernews.com
  2. Technology.org: Optimizely breach hits 178 websitestechnology.org
  3. Cyber Security News: Optimizely websites hijacked, indicatorscybersecuritynews.com
  4. Oneindia: Cyberattack hits 178 organisations including HSBC, BBC, Zoomoneindia.com
Share this story
Get the next major threat first

One short email when something serious breaks.

Threatspedia Desk

Threatspedia covers major cyber threats only, verified against primary sources. Read our editorial policy, or report a correction.

Threat alerts

Be first to know when a major threat breaks.

One short email when something serious happens, plus a weekly roundup. Free, no noise.