PublicAML

Premia exploit: 191.8 ETH turned into 5.27 BTC within an hour, and 4 BTC of it was deposited to HitBTC the same morning

PublicAML Ā· On-chain investigation Ā· 7 November 2026

On 1 November 2026 an attacker drained six Premia v3 option vaults on Arbitrum in two transactions one second apart and walked away with 191.78 ETH, about $434,000. Within 30 minutes all of it had left: 181.5 ETH was swapped into bitcoin through Chainflip and NEAR Intents, and 10 ETH went to Solana as USDC. The swaps paid 5.27 BTC to eight addresses, and by 09:29 UTC the attacker had cut that bitcoin into round 0.5 and 1 BTC pieces and sent 4.0 BTC to six deposit addresses at the exchange HitBTC. Early reports of 251 ETH sitting unmoved and of $280,000 frozen by bridges do not match what this wallet did.

191.78 ETH

paid to the attacker by its exploit contract on Arbitrum at 03:15:39–03:15:40 UTC on 1 Nov (about $434k at $2,264)

5.27 BTC

paid out by Chainflip (3.23 BTC, five swaps) and NEAR Intents (2.04 BTC, three swaps) to eight attacker addresses, 03:25–04:15 UTC

4.0 BTC

sent in six round pieces to six HitBTC deposit addresses; HitBTC swept them into its hot wallet at 09:29 UTC

0 ETH

left on the attacker wallet on either chain by 1 Nov 03:44 UTC, apart from gas

Contents

What is known

Premia is an options protocol; its v3 ā€œunderwriter vaultsā€ put depositors’ collateral to work selling options through option pools. On 1 November 2026 six of those vaults on Arbitrum (WBTC, WETH and ARB, calls and puts) lost most of the collateral they held directly. Blockaid described the method: the attacker created empty option pools, used flash loans to buy options so that vault collateral was locked into those pools, then withdrew that collateral as pool liquidity — the vaults trusted any newly created pool. Loss estimates range from about $400,500 (Blockaid, during the attack) and $437,000 (The Defiant) to $464,600 (PeckShield). Premia had not published a post-mortem when this was written. PeckShield reported that the stolen funds moved to Ethereum and were swapped into bitcoin through Chainflip and NEAR Intents.

The drain, read from the chain

The attacker wallet 0xbeBa8CEfD0D75d747C5AD966Dc17C0Bb60D84dBd got its Arbitrum gas at 01:28 UTC through MetaMask’s bridge, deployed its exploit contract 0x577168c8c6fa937495c3d6961f1d7d734b2d785f at 03:14:36 and called it at 03:14:37. One minute later, at 03:15:39 and 03:15:40, the contract paid the wallet 43.24 ETH and 148.54 ETH: 191.78 ETH in total. The WBTC and ARB taken from the vaults had already been turned into ETH inside the contract; the wallet never held anything else of size.

Out of ETH in 30 minutes

From 03:18 to 03:31 UTC the wallet sent the 191.78 ETH on Arbitrum to nine addresses in round amounts. 30 ETH went to two Chainflip deposit channels and came out as bitcoin. 20 ETH went to a NEAR Intents deposit address and also came out as bitcoin. 131.82 ETH went to six more NEAR Intents deposit addresses with the instruction to deliver ETH on Ethereum — to the same wallet; NEAR Intents’ hot wallet 0x2CfF890f0378a11913B6129B2E97417a2c302680 paid it 131.57 ETH there between 03:26 and 03:31. The last 10 ETH went to a deposit address of a cross-chain service whose sweeper contract swapped it into 22,639.78 USDC and burned that through Circle’s CCTP for Solana, where it was minted at 03:19:29 and forwarded thirteen seconds later to a Solana wallet JEJGkbBaoas7soCcTXK67q9VZ9rg3wJWSLEfj83ZgZi9 that makes hundreds of transactions a day — a service’s wallet, not one the attacker controls.

On Ethereum, from 03:32 to 03:44 UTC, the 131.5 ETH went out in five round amounts: 81.5 ETH to three Chainflip deposit channels (0x7Dd0f781655a628AcEB44ce07f2F5e9a641E048A, 0x23eb7AEEA82cbF9CB37fD16420a1074ba1073125, 0x53DF77e44a66212E7BC674354c7ED0bCA1871918, all forwarding to Chainflip’s vault 0xF5e10380213880111522dd0efD3dbb45b9F62Bcc) and 50 ETH to two NEAR Intents deposit addresses. Both services publish the status of a swap: Chainflip’s swap API and NEAR Intents’ 1Click API return the destination asset and address for each deposit. All eight that took the money to bitcoin did so — five through Chainflip for 3.2317 BTC, three through NEAR Intents for 2.0363 BTC — each to a fresh bc1q address. Every Chainflip swap went through the same broker account, charging 0.3%.

Round pieces, and HitBTC

The eight payouts arrived between 03:25 and 04:15 UTC. Each was spent once the same day, almost always into a round piece plus change: 1.0 or 0.5 BTC to a new address, the remainder to a change address that was later combined with other change. Six of the round pieces — two of 1.0 BTC and four of 0.5 BTC, 4.0 BTC in all — went to addresses that never spent on their own. At 09:29 UTC all six were swept together with 523 other inputs into one 27.35 BTC transaction to bc1qdfl3dfnwwvlqa5jpckh0ccwpjczh5y566c4g76, a hot wallet of the exchange HitBTC. That is how an exchange collects its customers’ deposit addresses: the six are HitBTC deposit addresses, and the 4.0 BTC was credited to one or more HitBTC accounts that morning.

About 1.1 BTC more left in three swaps marked with an OP_RETURN memo beginning ā€œ=|lifiā€, the tag LI.FI’s routing adds to bitcoin deposits; about 1 BTC (0.5 BTC to bc1qkvwph7r683m7qkrz09k7p369a8lyk4q58200ca, 0.35 BTC to bc1q09dez4x32zp27jhg6xffxwdc0mxx07pjxvd0l8 and two small taproot outputs) is not yet traced. On 4 November the attacker sent 0.09 ETH from the emptied Ethereum wallet through THORChain to 0xfa3C17e19F433Cc13820C930957428288250Da17 on Base, which is gas money for a next step there.

What the early reports got wrong

Some early summaries said the attacker swapped the funds into SOL, that Mayan and Relay froze about $280,000, and that 251 ETH remained unmoved on an Ethereum address. In this attacker wallet’s flows on Arbitrum and Ethereum we found no SOL swap other than the 10 ETH USDC leg described above, no transfer through Mayan or Relay, and no wallet left holding ETH: by 03:44 UTC on 1 November the wallet held 0.07 ETH of gas. If a freeze happened, it was not on this path.

What this page does not say

It does not say who the attacker is, or that Premia, Chainflip, NEAR Intents, Circle, LI.FI, THORChain or HitBTC did anything wrong: the swap services executed valid deposits, and an exchange cannot see what arrives at a deposit address before it is credited. It does not describe the vault flaw beyond what Blockaid has published. The loss range is Blockaid’s, The Defiant’s and PeckShield’s; the routes, swap destinations, bitcoin peel, HitBTC sweep and balances are PublicAML’s own reading of the chain on 7 November 2026. The HitBTC account behind the six deposits is the one lead that ends at an institution able to identify a customer.

Addresses in this case

Attacker wallet (the same address on Arbitrum and Ethereum)

Exploit contract on Arbitrum (not indexed by PublicAML)

The attacker’s gas wallet on Base, funded through THORChain on 4 Nov (not indexed by PublicAML)

Check an address yourself

Free, no sign-up. Paste any address to see whether it is linked to this or any other incident:

Sources: Blockaid’s, PeckShield’s and The Defiant’s reports of 1 November 2026 as summarised by crypto.news, Phemex and the PandaSecurity write-up on DEV Community; Arbitrum and Ethereum data via the Etherscan API and Blockscout; Chainflip’s public swap-status API and NEAR Intents’ 1Click status API for the swap destinations; Circle CCTP message decoded from the Arbitrum receipt, Solana via public RPC; Bitcoin via Blockstream and mempool.space; read by PublicAML on 7 November 2026. Price: ETH $2,264 (the attacker’s own 10 ETH → USDC swap). This is an information resource about transactions between addresses, not financial or legal advice, and it names no individual as responsible for anything.