Field report W-63 / P4 · sheet /operations

Operations & RestructuringFiled from the territory

Supply-Chain Cyberattack Hit 178 Websites Via Optimizely Scripts

Malicious code pushed through Optimizely reached 178 organisations' websites, targeting crypto payments, card data and iPhones; Salesforce and Equifax have responded.

Grid
W-63 / P4
Surveyed
November 17, 2026
Reading
3 min read
Correspondent
Amara Osei
Cyberattack Hits 178 Websites, Targets Cryptocurrency, iPhone Users
Fig. W-63 / P4Cyberattack Hits 178 Websites, Targets Cryptocurrency, iPhone Users — Pexels / pixabay

Field notes

  1. A cyberattack distributed malicious JavaScript to websites of 178 organisations via the Optimizely platform.
  2. The scripts targeted crypto payment addresses, credit card details, cookies and iOS devices.
  3. Salesforce disabled its compromised Optimizely scripts; Equifax stopped using Optimizely and found no breach of its own systems.
  4. Findings were reported by researcher Scott Helme and independently corroborated by HudsonRock.
  5. It remains unclear how many users were actually compromised.

Malicious JavaScript reached visitors of 178 organisations' websites, including Zoom, HSBC, Equifax, CNN, Salesforce and IKEA, in a supply-chain attack (an attack on a trusted external service provider rather than the target itself) designed to steal cryptocurrency, harvest payment data and exploit iPhones.

Security researcher Scott Helme documented the campaign, according to a Reuters report. The attackers used Optimizely, a third-party website optimisation platform, to push hostile scripts to browsers loading legitimate pages. The code was written to perform four distinct actions:

  • Replace legitimate cryptocurrency payment addresses with wallets controlled by the attackers, diverting transactions without the user's knowledge
  • Steal credit card details entered by visitors
  • Collect sensitive browsing data, including website cookies (small files that store session and login state) and screenshots
  • Deploy exploit code on iPhones and other Apple devices running iOS, opening a path to full device compromise

What did the affected companies do?

Salesforce confirmed it was investigating unauthorised changes to its Optimizely scripts. The company disabled those scripts as a precaution, it said. It did not state whether any visitor data had been taken.

Equifax went further and stopped using Optimizely entirely. The credit-reporting firm said its investigation had found no evidence that its own systems were compromised. It made no claim about whether visitor-side data collection had occurred before detection.

Cybersecurity firm HudsonRock independently reported finding evidence that the affected websites were serving malicious code to visitors. That second confirmation establishes the distribution beyond a single researcher's dataset.

How wide was the damage?

The honest answer is that nobody yet knows. It was not immediately clear whether the malicious code successfully compromised users across all 178 affected websites, or what the extent of any resulting breaches was. Distribution of a script does not guarantee that every attempted action — a redirected crypto payment, a captured card number, an exploited iPhone — succeeded.

Some organisations have begun investigating the incident and taking steps to limit potential exposure. Others among the 178 have not made public statements. Zoom, HSBC, CNN and IKEA are named in the Reuters reporting as affected operators.

Why does third-party code create the exposure?

The incident exposes a structural weakness in how major websites are assembled. When a page loads scripts from external providers such as Optimizely, the security posture of every visitor depends on the weakest vendor in the chain. Attackers who compromise one platform gain code execution on every site that embeds it — here, across 178 organisations in different sectors, from banking to media to furniture retail.

For the enterprises involved, the attack demonstrates that first-party defences did not fail in the conventional sense. Equifax, for example, reports no compromise of its own systems; the hostile code ran in visitors' browsers under the banner of a trusted integration. That distinction shifts scrutiny toward vendor management, script integrity monitoring and the decision to disable or drop third-party tooling quickly when an incident surfaces.

For consumers, the practical risks were concrete: cryptocurrency sent to a swapped wallet address is generally unrecoverable, stolen card details feed fraud directly, and harvested cookies can enable session hijacking (taking over an active login without a password). iOS users faced the most severe scenario, potential device-level compromise through exploit code.

The episode joins a growing pattern of attacks that ride trusted software distribution channels rather than breaching targets head-on. With 178 organisations confirmed affected, the immediate priorities for the sector are detection of what the scripts actually executed, notification of affected users, and audit of every third-party script with access to production pages.

via leadership.ng (Source)

Share this article:

More from Amara Osei

Amara Osei

Show full bio

Market editor covering people, launches and day-to-day practice in corporate strategy and chief-executive leadership at CEO Frontier.

449 articles

Filed under

Adjacent sheets

« Previous articleNext article »

End of sheetW-63 / P4 · November 17, 2026