0x14aacea014aa…14aace9d

ConfirmedSecurity524 vB42 sat/vB3 min decode

Optimizely Web Script Injection Hit Sites Tied to 178 Firms

Malicious Optimizely Web scripts hit sites tied to 178 organizations including Ledger, Zoom and HSBC, harvesting payment data and targeting iOS devices, Report URI said.

Optimizely Web Attack Exposes Visitors Across 178 Organizations
WitnessOptimizely Web Attack Exposes Visitors Across 178 OrganizationsPexels / pixabay

Outputs

  1. Malicious code via Optimizely Web affected visitors to sites tied to 178 organizations

  2. Named organizations include Ledger, Zoom, CNN, BBC, Fox News, HSBC, Equifax, Salesforce, IKEA and Air France-KLM

  3. Report URI said the injected scripts collected payment information and exploited iOS devices

  4. Ledger is the only crypto-industry name on the list, which spans five sectors

Malicious code delivered through the Optimizely Web experimentation platform exposed visitors to websites connected with 178 organizations, including crypto hardware wallet maker Ledger, according to an analysis by security firm Report URI. The incident puts a major crypto brand inside a far wider web-security breach spanning technology, media, finance, retail and travel.

Report URI said the injected scripts were built to collect payment information and exploit iOS devices. That combination — payment-card harvesting plus mobile-device exploitation — makes the attack financially motivated rather than an act of vandalism, and it extends the risk surface from corporate infrastructure to end users browsing normally.

Which organizations were named?

The list of 178 affected organizations, as reported by Report URI, includes:

  • Ledger — the France-based crypto hardware wallet firm, the only named digital-asset company
  • Zoom — enterprise communications
  • CNN, BBC and Fox News — major media outlets
  • HSBC — global banking
  • Equifax — consumer credit reporting
  • Salesforce — enterprise software
  • IKEA — retail
  • Air France-KLM — airline group

The spread matters. This is not a crypto-specific breach; Ledger sits alongside household names across five sectors, which signals the attack vector scaled across the mainstream web rather than targeting digital-asset users specifically.

How did the attack path work?

The described infection route runs through the Optimizely Web platform itself and reaches website visitors through malicious scripts. Optimizely Web is a third-party tool that companies embed to run A/B tests and personalize page content, and any script compromise in that supply chain propagates to every customer site loading the tool.

That supply-chain shape explains the scale. A single injected payload at the vendor level doesn't need to breach 178 separate networks — it rides the trusted script tag each of those sites already serves to visitors. For the named organizations, the operational consequence is the same regardless of sector: browsers visiting their pages executed attacker-controlled JavaScript.

What does Ledger's involvement mean for crypto users?

For the crypto industry, Ledger's inclusion ties the incident to digital assets without centering it on any token or blockchain network. The reported script objectives — payment information and iOS devices — make this a conventional web-security failure with financial-data theft at its core, not a smart-contract exploit or exchange hack.

Still, the context sharpens the concern. Ledger customers are, by definition, people holding assets worth protecting, and a malicious script harvesting payment details from visitors to a crypto company's site overlaps with exactly that demographic. Anyone who browsed an affected Ledger-related page during the injection window should treat their payment information as potentially exposed.

What should affected visitors and firms watch next?

No figure for the number of affected visitors, the duration of the injection or the volume of stolen data appears in the Report URI findings as reported. The organizations named now face questions about disclosure timelines, script-integrity monitoring and whether harvested payment data has surfaced in fraud channels. For the broader market, the incident adds weight to a structural shift already underway: subresource integrity controls and tighter third-party script governance, which firms dependent on vendor-delivered JavaScript are under growing pressure to adopt.

via tokenpost.com (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,514 articles