Field report SW-32 / P2 · sheet /boards

Boards & GovernanceFiled from the territory

Supply-Chain Hack Hit 178 Brand Websites Including Zoom and CNN

A single Optimizely vulnerability served malware to visitors of 178 sites including Zoom, CNN, HSBC and IKEA. The cleanup was fast; the damage remains uncounted.

Grid
SW-32 / P2
Surveyed
November 18, 2026
Reading
3 min read
Correspondent
Sophie Lindqvist
Hackers Target Zoom, CNN, 176 Other Global Brands In Cyberattack
Fig. SW-32 / P2Hackers Target Zoom, CNN, 176 Other Global Brands In Cyberattack — yeiferr / pixabay

Field notes

  1. Malware reached visitors of 178 organisations' websites via an Optimizely vulnerability detected on November 16.
  2. Infected scripts fell from 169 to one by 21:52 UTC on November 16 after remediation.
  3. The malware stole card data, browser cookies and crypto payment addresses, and deployed iOS exploit kits Coruna and DarkSword.
  4. Chainalysis estimates cryptocurrency hacks have stolen over $22.3 billion since 2021.
  5. The number of compromised devices and stolen records remains unconfirmed.

One vulnerability in a single third-party platform exposed visitors to 178 organisations' websites — including Zoom, CNN, HSBC, Equifax, Salesforce and IKEA — to malware designed to steal cryptocurrency and payment card data. The incident, detected on Monday, November 16, is a textbook supply-chain attack (a breach of a trusted intermediary service rather than the target organisations themselves), and its consequences are still not fully measured.

That last point matters most. Cybersecurity firm HudsonRock confirmed that affected websites served malicious code to visitors. What HudsonRock could not confirm — and what nobody has so far quantified — is how many devices were actually compromised or how much financial data was taken. Every assurance below should be read against that gap.

How did the attack work?

According to cybersecurity researcher Scott Helme, attackers injected malicious JavaScript (code that runs in a visitor's browser) into customer projects hosted on Optimizely, a website experimentation and personalisation platform. Websites relying on Optimizely then delivered the compromised scripts to their visitors automatically.

The attackers never needed to break into 178 corporate networks individually. One weakness in one trusted vendor did the work. Optimizely has confirmed that an unauthorised party exploited a vulnerability in its Experimentation platform to introduce the malicious code.

What did the malware do?

According to Reuters, the malicious scripts pursued several objectives at once:

  • Replaced legitimate cryptocurrency payment addresses with attacker-controlled wallets, diverting funds during transactions
  • Captured credit and debit card details entered into website payment forms
  • Stole browser cookies (small files that can hold login sessions), potentially granting account access
  • Took screenshots of users' screens
  • Deployed two iOS exploit kits, named Coruna and DarkSword, targeting Apple iPhones and iPads

The iOS component shows the operation was not limited to financial theft. It also aimed at vulnerabilities in mobile devices — a scope that suggests deliberate planning rather than opportunistic vandalism.

What does this change for the affected companies?

Responses have varied, and the variation is itself informative:

  • Optimizely said it has fixed the vulnerability, removed the injected code, secured affected user accounts and introduced additional safeguards against unauthorised code delivery. The company did not say how long the vulnerability existed before detection.
  • Salesforce said it is investigating unauthorised changes to its Optimizely scripts and disabled them as a precaution.
  • Equifax stopped using the platform entirely after investigating, though it found no evidence its internal systems were compromised.
  • HSBC said unauthorised scripts were no longer active on its websites.
  • IKEA is investigating the potential impact.

Reuters reported that Apple, Zoom and CNN had not immediately responded to requests for comment. Silence from three of the largest names on the list leaves their exposure publicly unassessed.

The clean-up, at least, was fast. Report URI's findings show infected scripts falling from 169 to just one by 21:52 UTC on November 16. Speed of remediation, however, says nothing about what was harvested before detection.

Why third-party risk is the real story

The attack does not establish that the internal networks or databases of all 178 organisations were breached. It demonstrates something arguably more unsettling: cybercriminals can exploit a single trusted digital service to reach a vast pool of potential victims without touching any of their targets directly.

Blockchain intelligence firm Chainalysis estimates cryptocurrency hacks have yielded more than $22.3 billion in stolen funds since 2021. That figure explains the incentive structure behind attacks of this kind — and why payment-address substitution, the quietest of the malware's functions, may prove the costliest.

For internet users, the practical lesson is limited but real: exercise caution with online payments, especially cryptocurrency transactions, and keep mobile devices and applications updated.

For executives, the harder question is governance. Who in your organisation continuously audits the external scripts running on your customer-facing sites? The attack raises pointed questions about the responsibility of both technology providers and their clients to monitor third-party software and strengthen safeguards around services handling customer information. Optimizely patched quickly. Nobody has yet explained why the vulnerability was there in the first place — or how many similar ones remain across the ecosystem of vendors that modern websites depend on.

via leadership.ng (Source)

Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

Correspondent covering money, funding and market shifts around corporate strategy and chief-executive leadership at CEO Frontier.

479 articles

Filed under

Adjacent sheets

« Previous articleNext article »

End of sheetSW-32 / P2 · November 18, 2026