On-chain investigationBitcoin · Litecoin · TRON · Ethereum · BNB Chain17 November 2026

The Optimizely hack took $2,260 in crypto, in 19 payments. The $7,040 first reported counts the thief's own swap.

A script trusted by some of the web's biggest sites showed visitors the wrong wallet address for most of a day. We traced the wallets behind it, coin by coin, into the next morning.

At a glance
On 16 November, malware reached the websites of 178 companies through Optimizely, a tool that sites load to test page designs. Among other things, it swapped crypto addresses on the page for the thief's own. First reports put the take at about $7,040. We followed every payment into the thief's 8 wallets. Victims paid $2,260 in 19 payments. The first count also included a Bitcoin transfer from the thief's own swap. The thief had sent $4,920 of stablecoins to a swap service, and 0.076 BTC came back 14 minutes later to the same wallet. By the morning of 17 November, the Bitcoin and the Litecoin had moved to new addresses.
$2,260
Paid by victims, in 19 payments
$7,040
Received by the wallets, as first reported
$4,920
Swapped into Bitcoin by the thief in 14 minutes
178
Companies with an infected script
Key findingsEach line has its own share link
  1. $2,260

    What victims paid into the thief's wallets on 16 November, in 19 payments on 5 chains. First reports said about $7,040.

  2. $4,920

    Stablecoins the thief sent to a swap service at 13:03 UTC. 0.076 BTC came back to the same wallet 14 minutes later.

  3. 92%

    Share of the Bitcoin in the first count that came from that one swap transaction.

  4. $54

    The median victim payment. 6 payments were under $25. The largest was 15 LTC, about $670.

  5. 4 of 8

    Wallets in the malware that never received a coin: Solana, TON, Bitcoin Cash and Dogecoin.

  6. 0.085 BTC

    Moved to a deposit address at 05:39 UTC on 17 November. It had not moved again when we last looked.

01 · What happenedThe Optimizely hack, in one day

Did you copy a crypto address from a big website on 16 November? If so, check where your money went. For most of that day, pages on the BBC, CNN, Zoom and other big sites could show the wrong address.

Nobody had to break into those sites. Each one loads a tool from Optimizely, a US software company. The tool lets a site show two versions of a page and keep the better one. That day, someone slipped their own code into the tool on the sites of 178 companies. We call that person the thief. Report URI, a web security firm, found 188 infected copies among the 1,611 it checked.

The code did three jobs. It copied card numbers that people typed into forms. Security teams call that web skimming, or formjacking. It tried to break into iPhones. And when a page showed a crypto address, the code swapped in one of the thief's addresses.

Optimizely blamed a flaw in the signup flow of one of its products, BleepingComputer reports. Most of the infected copies were clean again that night.

The first count of the damage came from the thief's wallets. By that evening, they had taken in about $7,040, Report URI found. News reports repeated that figure. Bitquery reads every transfer on Bitcoin and the other chains those wallets use. So we went through each payment and split victim money from the thief's transfers.

Victims paid about $2,260. Most of the Bitcoin in the first count came from the thief's own swap. The thief traded dollar tokens for Bitcoin, and the Bitcoin came back to the same wallet. Below, we show who paid, how that swap worked and where the coins sat a day later. We cover the crypto only. Card theft leaves no trace on a blockchain.

Victims paid $2,260. The first count was $7,040what the thief's wallets received on 16 November 2026
WHAT THE WALLETS RECEIVED, AND WHAT VICTIMS PAIDReceived by 19:25 UTC, as first reported: $7,040$4,930: a swap by the thief, paid back in Bitcoin$2,110: victimsPaid by victims by the end of 16 November$2,26019 payments, the last at 19:57 UTCvictim paymentsthe thief's swap coming back
The blue part is one Bitcoin transaction at 13:18 UTC. It is the payout of a swap the thief made. Bitcoin data comes from the Bitcoin dataset.

02 · The attackA supply chain attack on 178 companies

A supply chain attack hits a supplier to reach its customers. Here the supplier was Optimizely, and the customers were the sites that load its code. A browser treats that code like the site's own. So the code can read and change anything on the page.

Report URI's list runs from banks and airlines to news sites and streaming services.

6 of the 178 companies work in cryptocompanies with an infected Optimizely script, by sector
THE 178 COMPANIES WITH AN INFECTED SCRIPT, BY SECTORBanking and finance32Technology and SaaS23Retail and fashion20Streaming12News and media10Airlines and travel9Healthcare8Industrial8Telecoms7Crypto and trading6Insurance6Property6Food and hospitality5Home5Nonprofit4Gambling4Professional services4Logistics3Automotive3Education3
The count and the sectors are Report URI's. A site with no wallet address on its pages gave the malware nothing to swap.

Only 6 of the 178 companies work in crypto or trading. One of them is Ledger, which makes hardware wallets. Last month we traced the Ledger CryptoBilis hack.

Crypto people call an address swapper a clipper. Older clippers run on the victim's own machine and change an address after the user copies it. This clipper ran inside the web page. It replaced addresses in the page text, in links and in anything the visitor copied.

How the clipper swapped an addressthree steps, inside the visitor's browser
HOW THE ADDRESS SWAP WORKS1. The page shows an addressThe site owner put it there:bc1q...the site's walleta donation, a deposit, an invoice2. The script swaps itOn the page, in links, on copy:19g9rZc...the thief'sthe page looks the same3. The visitor paysThe coins go to the thief.No way to reverse itthe site never sees the paymentThe malware carried 8 addresses, one per kind of coin. It matched the format of the address on the page.
The visitor sees a normal page. The site's owner sees nothing, because the swap happens after the page loads.

The thief built the first clipper about four hours after the bad code appeared on a site. Report URI counted 26 builds of the code that day. Later builds added wallets and removed none. The last build carried 8 addresses, one for each kind of coin it looked for.

Attacks on the web page in front of a wallet are common. A hijacked domain drained users of Across Protocol this month. In October, a DNS hijack at Name.com turned 12 DeFi sites against their own users.

03 · The victimsHow much crypto was stolen, and from whom

A payment to a swapped address looks like any other payment. So we read the full history of all 8 wallets. Four of them never got a coin. Those were the wallets for Solana, TON, Bitcoin Cash and Dogecoin.

The other 4 wallets took in 19 payments from outside that day, from 18 senders. The first came about 90 minutes after Report URI first saw the clipper on bbc.com. The last came ten hours later.

19 payments in ten hoursevery payment to the thief's wallets on 16 November 2026, in UTC
16 NOVEMBER 2026, UTC: EVERY PAYMENT TO THE THIEF'S WALLETSBNB ChainTRONBitcoinLitecoinEthereumOwn swap04:21 first injection08:10 clipper first built13:43 card skimmer added20:40 clean-up starts04:0006:0008:0010:0012:0014:0016:0018:0020:0022:0013:03 to 13:18: thief swaps $4,920 to BTC15 LTC, $670: the largestone victim payment, sized by valuethe thief's swap
Each red dot is a payment from outside. The blue mark is the swap the thief made. TRON data comes from the TRON dataset.

Most payments were small. The median was $54, and 6 of them were under $25. The largest was 15 LTC, worth about $670.

Litecoin and TRON took the mostvictim payments by chain, in dollars at the time of each payment
WHAT VICTIMS PAID, BY CHAIN: $2,260 IN 19 PAYMENTSLitecoin$765 in 3 paymentsTRON$718 in 7 paymentsBitcoin$596 in 4 paymentsEthereum$101 in 1 paymentBNB Chain$82 in 4 payments
One 15 LTC payment makes up most of the Litecoin bar. Litecoin data comes from the Litecoin dataset.

Together, the payments come to about $2,260. One payment may not belong in that sum. A busy service wallet sent $51 of TRX, and the thief may have bought that TRX to pay network fees. Without it, the total is $2,210.

Two payments came from wallets that our labels mark as Revolut's and Bybit's. In those cases, the victim likely pasted the swapped address into a withdrawal form.

Time (UTC) and chainPayment on 16 November
09:57 · BNB Chain1.00 USDT, $1
10:01 · BNB Chain1.00 USDT, $1
10:26 · TRON21.89 USDT, $22
10:31 · TRON168.70 TRX, $51, may be the thief's
11:13 · Bitcoin0.0052807 BTC, $341, from a Revolut wallet
12:04 · BNB Chain60.00 USDT, $60
12:11 · TRON350.00 USDT, $350
12:50 · TRON15.00 TRX, $5
12:51 · TRON175.00 USDT, $175
14:23 · TRON100.00 USDT, $100
14:30 · BNB Chain20.00 USDT, $20
15:24 · Litecoin15.00 LTC, $674
15:51 · Litecoin1.35 LTC, $61
16:25 · Bitcoin0.00084 BTC, $54
16:39 · Litecoin0.67 LTC, $30
16:50 · TRON16.00 USDT, $16, from a Bybit wallet
17:28 · Ethereum0.0553 ETH, $101
18:53 · Bitcoin0.00078436 BTC, $51
19:57 · Bitcoin0.00231063 BTC, $150

04 · The countWhy the first count was $7,040

Report URI added up what the wallets had received, and its sum is correct. It also noted that the TRON wallet was in use months before the attack. But one Bitcoin transfer in the sum did not come from a victim.

At 13:18 UTC, the Bitcoin wallet received 0.076 BTC in one transfer. That transfer was 92% of the Bitcoin in Report URI's count.

Take it out, and the count falls to about $2,110. Our own count of victim payments up to that time gives the same figure. One more Bitcoin payment, worth $150, came in half an hour later.

05 · The swapThe thief's own swap

The 0.076 BTC came from the thief. Early that afternoon, in under two minutes, the thief's wallets sent stablecoins to three deposit addresses on three chains. A stablecoin is a token meant to hold $1. A deposit address is an address a service hands out to receive a customer's coins.

Fourteen minutes after the first deposit, one Bitcoin transfer paid three amounts to the thief's Bitcoin address.

$4,920 of stablecoins in, 0.076 BTC outthe thief's swap on 16 November 2026
IN: THREE DEPOSITSOUT: ONE TRANSACTION, 13:18 UTC4,310.82 USDCEthereum, 13:03:59 UTCarrived on 12 November0.06667279 BTCprices 1 BTC at $64,656to the thief's address546.80 USDTTRON, 13:05:06 UTCvictim payments0.00844891 BTCprices 1 BTC at $64,718to the thief's address62.00 USDTBNB Chain, 13:05:20 UTCvictim payments0.00095043 BTCprices 1 BTC at $65,234to the thief's addressA swap serviceon wallets our labelsmark as HitBTC'sno account needed$4,920 in, 0.076 BTC out, 14 minutes after the first deposit.
Each deposit has a matching Bitcoin output in the same transaction. Deposit data comes from the Ethereum and BNB Chain datasets.

Each amount matches one deposit. The two larger pairs work out to the same Bitcoin price, within 0.1%. Each payout is worth a little less than its deposit. The gap is about 1% for the two larger ones and 2% for the smallest. A swap fee would leave that gap.

Our labels mark the deposit addresses and the paying wallet as HitBTC's. HitBTC is an exchange. But the two largest deposit addresses are shared. Tens of thousands of senders have paid into each one since July. That points to a swap service, a site that trades one coin for another without an account. So the chain shows a swap on wallets labeled as HitBTC's. The chain shows no account in the thief's name. The wallets behind the Kava hack used a swap on the same exchange's wallets two days earlier.

The stablecoins had two sources. About $610 was victim money from that morning, which we counted above. The rest was 4,311 USDC that sat in the wallet before the attack. It came in on 12 November from a wallet our labels mark as OxaPay's. OxaPay is a payment gateway, a service that lets shops take crypto. The same gateway wallet also paid this address in March.

That USDC is no part of this hack's losses. It may be income the thief earned, or it may come from an earlier theft. The chain cannot tell us which.

06 · The moneyWhere the coins went

For the rest of that day, the coins sat still. Then, early on 17 November, the thief emptied the wallets.

Where the coins sat a day laterthe thief's wallets, read at 06:45 UTC on 17 November 2026
WHERE THE MONEY SAT AT 06:45 UTC ON 17 NOVEMBERVictims, 16 November$2,260 in 19 paymentsAlready in the wallet4,311 USDC from 12 NovemberThe thief's walletsBitcoin, Litecoin, Ethereum, BNB Chain, TRONThe swap, 16 November$4,920 in, 0.076 BTC outBitcoin, $5,540deposit address, unspentLitecoin, $765new address, unspentEther, $136payment gateway addressTRON, $168deposit address20 USDT stayed in the wallet on BNB Chain.
Every arrow is a public transfer. Dollar values use the price at the time of each move.

The Bitcoin, 0.085 BTC, went to what looks like a deposit address at a custodial service. That is a firm that holds coins for its users. Days earlier, coins at that address were swept up together with coins from almost 1,000 other addresses. We have no label for the service. The Litecoin moved to a new address and stopped there. When we last read both addresses, on the morning of 17 November, neither had sent the coins on.

The ether went to an address that forwards what it gets to the gateway wallet named above. Other people pay into that address too, so it may belong to a shop the thief paid. The TRON funds went to an address the thief's wallet has used since March. That month, the wallet also paid into Shuffle, a crypto casino, going by our labels.

Anyone can follow these wallets with the Bitquery MCP.

07 · For victimsWhat to do if you paid on 16 November

Look at each crypto payment you made that day after you copied an address from a website. Compare the address you paid with the 8 addresses in the record at the end.

If it matches, nobody can reverse the payment. A freeze is still possible. The Bitcoin sits at what looks like a custodial service, and the swap ran on an exchange's wallets. Both kinds of firms keep records and respond to police requests.

So report the payment to the police, and to your exchange if you paid from one. Give them the transaction ID. Guides on how to recover stolen crypto often promise more than that. Be careful with anyone who offers to get the coins back for a fee.

Did you type a card number on one of the sites that day? Treat the card as exposed and call your bank. For larger cases, we also run crypto investigation services.

08 · The limitsWhat the chain cannot tell us

We do not know who the thief is. The swap service and the payment gateway hold records that could say.

We treat a payment as a victim payment when it reached one of the 8 addresses after the first clipper build. The sender must have no other tie to the thief. Someone could still have paid one of these addresses for another reason.

An earlier wave of the same campaign ran for three days before the Optimizely one, through other companies' scripts. One analysis says that wave carried the iPhone attack and no clipper. We did not test that ourselves.

The thief's Ethereum address works on dozens of chains. We read nine of them. Only Ethereum and BNB Chain had victim payments.

09 · The methodHow we traced the stolen crypto

We took the 8 addresses from Report URI's write-up. For each wallet, we read every coin in, every coin out and the address on the other side. For Bitcoin and Litecoin, we opened each transfer to see who paid and who else got coins in the same batch. Then we checked the wallet totals against public block explorers.

We left out fake tokens that bots sent to the wallets, a trick called address poisoning. Dollar values use Bitquery's price for each coin at the time it moved. Exchange names come from Bitquery's address labels.

Each chain's full history is also sold as files on the Bitquery Data Store. We used the Bitcoin, Litecoin, TRON, Ethereum and BNB Chain datasets.

Limits on these findings

All chain data was read on 17 November 2026, up to about 06:45 UTC. Anything after that is not covered. The wallets may have moved since.

The 8 wallet addresses, the times of the injection and of each build, and the count of affected companies come from Report URI's public write-up. We did not examine the malware ourselves.

We treat a payment as a victim payment when it reached one of the 8 wallets on 16 November after the first clipper build, from an address with no other tie to the thief. We cannot confirm what each sender meant to do.

One TRON payment of $51 in TRX came from a busy service wallet and may have come from the thief. With it, the total is $2,260. Without it, $2,210.

The link between the three stablecoin deposits and the Bitcoin payout rests on timing and on the amounts. The names HitBTC, OxaPay, Revolut, Bybit and Shuffle are Bitquery's own labels on addresses. We do not say any of these companies knew where the coins came from.

Dollar values use the price at the time of each transfer. TRON prices are daily. Report URI used prices from the evening of 16 November, so its dollar figures differ from ours by a few dollars.

We read the thief's Ethereum address on Ethereum, BNB Chain, Polygon, Arbitrum, Base, Optimism, Avalanche, Mantle and Blast. Other chains that use the same address format were not checked.

Wallet totals for Bitcoin and Litecoin match public block explorers. The Solana, TON, Bitcoin Cash and Dogecoin wallets show no history on public explorers. The TRON totals match Report URI's figures.

We did not check the earlier wave of the campaign, from 13 to 16 November. Card theft and the iPhone attack are outside what a blockchain records.

Links between wallets are money links. They do not prove who controls a wallet.

10 · The recordThe addresses behind the Optimizely hack

19g9rZcPeiz8rUvyWpTRyXXhPnjsWrc3kW
0xC4026b06D82b0F0B363eda0642D61CfbDc17884e
THvs6p56XkUiMkJeSc51cAP64u2RsTYqxa
ltc1q3wp7g6ds0ggg6fl6kncpa4sepn0q3qfacgred5
FVtL8NMYS9PA1v3HE67XUGCtGA9JaZUvqav2fU2LrV5n
Solana wallet, never used
UQAgM1VqSZQiJLSG5w-ovurq5CZdxLEK3_7CMmwALTA5e09p
TON wallet, never used
qzkaaf8n6grmpr0d9lx8xutn3r9lk722f566hhpe58
Bitcoin Cash wallet, never used
DBEGrxRF7KMSuhTS4c1MFviStU6efdMnu5
Dogecoin wallet, never used
79FC6BA6E10D6F7E16C80B1963D9D95AB77D6D932CCBBA11A4207757466F7846
0x623d72302c9dd12d639ccb6ff38f94e3dab015b3aface347a68f3f8acb6ba871
0707a0000c77611be27a9e9e8d376c9ce91e85caf82f49e9a8ae2a8cc8c56079
0xa22913c7c14943aeb41b2c07f48a7c94ce80e2b3343326ef24c4df8b4665ddc3
0x7d0778eeb2fb62bd9ced5b912bd1fa042852b6464f1895261561b1e04a4f63ff
C014F92FF736B3A30D069482BE3662A0D479509692A0F352E1766944385ACC5A
178A4AF4FF81E95BA8B84114E5653BB7A1CE86A92D034F676C9FC48B7EDF0CB6
bc1q5fljq9c4g7gsjgg4etpn6k3lyusahcvjfv0u99
742509BDF8ADC917B1F8F88DC407DD83D20018F75598424B6DF67F525B321966
ltc1qpxvjs8u8awg8pvpwmssqlj3gzugd9vtwjtc5fc
0x5fdd1310fe7a635e29fe2cbf7e24bae793ff6310d22ce1ad89a2084a5f201b35
TMLQvDvpgSyx94maptc3TxvmCVtT5qHVup
Run it yourself

Follow the money in plain English

Every payment and every move in this story comes from Bitquery's data. The Bitquery MCP server puts that data behind an AI assistant, so you can ask where a wallet's money went without writing a query. The full history is also sold as files on the Bitquery Data Store, as the Bitcoin dataset.

List every payment a Bitcoin or Litecoin address receivedOpen a transaction and see who paid and who was paidFollow USDT from a TRON wallet to the next addressCheck an address against Bitquery's labels
Explore Bitquery MCP →Bitcoin, Litecoin, TRON, Ethereum and BNB Chain data from Bitquery. Data read on 17 November 2026.
Legal disclaimer

This article is provided for informational and educational purposes only and reflects analysis of publicly available on-chain data as of the dates indicated. It does not constitute legal, financial, compliance, or investment advice, and nothing in it is a recommendation to buy, sell or hold any token or asset, or to use or avoid any exchange, wallet, website, software product or service.

The findings describe transactions and balances observed on Bitcoin, Litecoin, TRON, Ethereum, BNB Chain and other public blockchains between 12 and 17 November 2026. Attributions come from on-chain behaviour and Bitquery's own labels; they may be incomplete or incorrect and may be revised as more data becomes available. Optimizely has said it will publish an incident report, and its findings may differ from those described here.

References to Optimizely, Report URI, BleepingComputer, the BBC, CNN, Zoom, Ledger, HitBTC, OxaPay, Revolut, Bybit, Shuffle, Across Protocol, Name.com or any other named project, company or service describe what the public record shows and what those parties have said in public. They are not statements about any party's intent, security practices, solvency or conduct, and nothing here asserts that any named party acted unlawfully or negligently or knew of the events described. The wallets that received the payments are described by their behaviour and attributed to nobody.

Nothing herein should be relied upon as a definitive determination of fact. Readers should conduct their own independent verification before taking any action. The authors and publisher accept no liability for any loss or damage arising from reliance on this material. All trademarks and company names are the property of their respective owners.

Reported by Gaurav Agarwal for Bitquery Research, with AI tools; every figure was checked against the raw data.

FAQ

Was Optimizely hacked?

Yes, in part. On 16 November 2026, someone put bad code into scripts that Optimizely serves to the sites of 178 companies. Optimizely blames a flaw in a signup flow. The thief did not need to break into the sites' own servers.

What is a supply chain attack?

A supply chain attack hits a supplier to reach its customers. Here, the thief changed code that Optimizely serves, and each site that loads the code ran it. The sites changed nothing.

How much crypto was stolen in the Optimizely hack?

Victims paid about $2,260 into the thief's wallets, in 19 payments on 16 November. If we leave out one payment that may have come from the thief, the total is $2,210. Card theft is not part of that figure.

Why did early reports say $7,040?

The first count added up everything the thief's wallets had received by that evening. That included 0.076 BTC that a swap by the thief paid back to the Bitcoin wallet. Without it, the count comes to about $2,110.

What is a crypto clipper?

A clipper is malware that swaps a crypto address for the thief's address. Older clippers change the address after a user copies it. This one ran inside the web page and changed the address on the page, in links and in copied text.

What is formjacking?

Formjacking is code on a web page that copies what people type into a form, such as a card number. Some call it web skimming. The Optimizely malware gained a card skimmer on the afternoon of 16 November.

Is cdn.optimizely.com safe now?

Report URI found that all but one of the infected copies were clean by the end of 16 November. Site owners should still open each Optimizely project and check its code. Visitors cannot check this themselves.

Can you recover or trace stolen crypto?

Anyone can trace it, because each transfer is public. Getting it back is harder. Nobody can reverse a payment. A firm that holds the coins can freeze them if the police ask in time.

Run the next investigation in minutes

Ask any question of the blockchain. Bitquery's AI Investigations agent traces funds, attributes wallets, and writes auditable reports across every major chain. Prefer to do it yourself? Connect the Bitquery MCP server to your AI assistant, pull the raw datasets, or query the chain directly with the Bitquery API.