0x604b5644604b…604b5647

ConfirmedSecurity478 vB68 sat/vB2 min decode

Supply-Chain Scripts Hit 178 Firms in Crypto Wallet Swap Attack

Malicious Optimizely-hosted scripts hit 178 organizations, swapping copied BTC, ETH and SOL addresses; attacker wallets collected about $7,040 before cleanup.

Malicious Scripts Exposed Visitors to Crypto Wallet Swaps at 178 Organizations
WitnessMalicious Scripts Exposed Visitors to Crypto Wallet Swaps at 178 OrganizationsFirmbee / pixabay

Outputs

  1. Malicious code hit 188 JavaScript files across 178 organizations via Optimizely

  2. Attacker-linked wallets received about $7,040 in crypto assets

  3. 187 of 188 files were cleaned by 4:52 p.m. ET Monday (21:52 UTC)

  4. Scripts swapped copied or typed BTC, ETH and SOL addresses and harvested card data, cookies and screenshots

  5. Ledger, HSBC, BBC, CNN, Zoom and Salesforce were among affected organizations

Attackers injected malicious code into 188 JavaScript files served through the website-optimization platform Optimizely, exposing visitors at 178 organizations worldwide to crypto wallet-address swaps. Wallets linked to the attackers received roughly $7,040 in crypto assets before cleanup began, according to incident reporting on the campaign.

The tampered scripts could replace Bitcoin (BTC), Ether (ETH) and Solana (SOL) addresses that users copied or typed on affected sites with addresses controlled by the attackers. Beyond clipboard and input manipulation, the code could collect bank-card information, browser cookies and screenshots, and deliver exploit tooling to some iOS devices.

Ledger, HSBC, BBC, CNN, Zoom and Salesforce were among the named affected organizations. The breadth of the victim list illustrates the operational problem: a single compromise of a shared third-party script propagated to visitors across banks, media companies and software vendors simultaneously.

How far did the compromise spread?

The attack targeted shared JavaScript dependencies rather than individual websites. Because thousands of pages embed the same optimization script, one insertion point reached users across many institutions in one operation. That structure inverted the usual economics of web attacks: instead of breaching 178 targets, the attackers breached one distribution channel serving all of them.

The financial haul remained small relative to the exposure. Attacker-linked wallets collected about $7,040 in crypto assets, a figure that likely reflects how many users actually copied a wallet address on an affected site during the infection window rather than the full number of exposed sessions. Data theft capabilities — card details, cookies, screenshots — do not appear in that on-chain total.

What has been fixed, and what is still unknown?

By 4:52 p.m. ET Monday (21:52 UTC), 187 of the 188 affected JavaScript files had been cleaned, leaving one outstanding. The specific route used to compromise the scripts remained under investigation. That gap matters: without knowing whether the initial access came through compromised credentials, a compromised build pipeline or a supplier, operators cannot verify the vector is closed.

The incident adds to a pattern of attacks on trusted third-party web infrastructure, where script-based distribution lets one intrusion scale across otherwise unrelated domains. For the affected organizations, the operational consequences extend past remediation: any user who transacted a wallet address, entered card data or authenticated during the exposure window may have handed credentials or funds to the attackers.

For crypto users specifically, the address-swap mechanism is difficult to detect after the fact. A transaction sent to a substituted address confirms on-chain as normal, leaving no reversal path once funds move.

Investigators have not yet named the actors or disclosed the infection timeline. Identifying the compromise route — and whether the remaining file and any harvested data are contained — will determine whether this stays a $7,040 theft or becomes a broader credential-exposure event across the 178 affected organizations.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles