Researchers Find Crypto Malware in Optimizely Scripts

50Importance
updatingStatus
3News media
Published
Updated

A JavaScript supply-chain attack on Optimizely Web exposed visitors to the websites of 178 organizations. The incident affected company sites that included Zoom, BBC, CNN, Salesforce, GitLab, HSBC, and Ledger, and one analysis found infected code in 188 of 1,611 Optimizely scripts.

Key claims & sources

✓
Attackers inserted malicious JavaScript into Optimizely Web projects, exposing visitors to websites of 178 organizations.
✓
The attack was reported as a major JavaScript supply-chain incident tied to Optimizely Web.
✓
On November 16, hackers used Optimizely Web to send malware JavaScript to visitors of websites of 178 companies.
✓
Report URI analyzed 1,611 Optimizely scripts and found infected code in 188 of them.

What it means

Optimizely Web is a testing and personalization platform used inside company websites, so a compromise there can reach site visitors rather than only internal systems. The incident sits in the broader class of JavaScript supply-chain attacks, where a shared script can affect many downstream properties at once. The fact that this involved websites rather than a single app installation makes the exposure part of the public web stack, not a back-office issue.

Web operators that rely on Optimizely Web now have to treat third-party scripts as a security boundary, not just a marketing tool. Visitors who loaded affected pages may have been exposed to injected code, so site owners will need to audit embeds, rotate scripts, and review what runs in the browser. Companies named in the incident include Zoom, BBC, CNN, Salesforce, GitLab, HSBC, and Ledger.

This case shows how much reach a single compromised web service can have across unrelated brands, from media outlets to finance and software firms. It also underlines a trade-off in modern websites: the more shared JavaScript a site loads, the larger the blast radius when one component is tampered with. That tension sits at the heart of browser-based tracking, testing, and personalization, which are widely used but hard to isolate cleanly.

What remains open is which specific Optimizely projects were altered, how long the malicious code stayed live, and which companies were affected in practice beyond the list already named. The 1,611-script analysis points to the scale of the review, but the full scope of exposure is still not set out here. A fuller accounting would need matching timestamps, affected site logs, and confirmation from each operator.

Market reaction i

Total crypto marketall crypto assets combined no single asset in the event: read against the whole market

The total crypto market rose 0.5% in the 4 hours after the first headline, after falling 0.8% in the 2 hours before.

$2.2T market cap at the headline
-0.8% 2 h before
+0.5% 4 h after
-1.8% 10 h after (so far)
First headline

44 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 17 00:25
The Defiant scoop
Breaks the event
+5 h 29 m
Nov 17 05:54
Coinpedia context
Its angle: cyberattack, injecting, targeted; with quotes
+8 h 4 m
Nov 17 08:29
Coinpedia echo
No new facts: screenshots, additional, vulnerable
+9 h
Nov 17 09:25
CR Cryptopolitan context
Its angle: administrators, documentation, protections; with quotes

Other recent incidents

WhenWhat happenedFigure
1 days ago MORE Markets · Unknown incident $308k
1 days ago Lighter · API key leakage incident $10.4M
2 days ago Luxor Commander · Unknown incident no figure in dollars
2 days ago Chain Games · Reward Logic Flaw incident $20k
3 days ago Kava Lend · Smart contract vulnerability incident $3.8M

4327 incidents stored