Skip to content
Crypto.world

The Ledger

A Negative Fee Drained $90,528 From the WAX Bridge

Five WAX bridge withdrawals on October 22 released about $90,528 in USDC, USDT, DAI, WETH and WBTC without charging the withdrawing account. Bitquery traced the funds across Solana and Ethereum, reporting that nearly all reached HitBTC deposit addresses within 38 minutes.

A Negative Fee Drained $90,528 From the WAX Bridge

$90,528 left the WAX bridge

Five withdrawals drained about $90,528 from the WAX Multi-Chain Bridge on October 22, sending assets to Solana and Ethereum without debiting the WAX account that requested them. The withdrawals included 52,986 USDC, 21,558 USDT, 840 DAI, 2.55 WETH and 0.11 WBTC, according to Bitquery’s on-chain investigation.

The total exceeds early estimates of roughly $75,000 because those counted only stablecoins. Bitquery values the WETH and WBTC at about $15,100 combined, using prices from the attacker’s swaps; its full estimate prices USDC, USDT and DAI at $1 each. The theft happened in five transactions spanning 86 seconds.

The withdrawal math accepted a minus sign

The bridge’s withdraw function added the requested fee to the withdrawal amount before subtracting the total from the user’s balance. It did not reject fees below zero. By setting the fee equal to the negative withdrawal amount, the account made the debit zero while the bridge still released the corresponding assets on the destination chain.

“The thief set the fee to minus the amount, so the charge came to zero.”

Gaurav Agarwal, Bitquery

Bitquery’s review found no negative-fee attempt in more than 3,100 recorded withdrawals dating back to March 2021. Since June, the investigation counted 446 withdrawals by other accounts, all with a fee of zero. The missing check turned an input the bridge had not previously encountered into a way to bypass the balance charge.

Each withdrawal took most of its vault

The first transaction sent 52,986 USDC to Solana. The next four sent USDT, DAI, WETH and WBTC to Ethereum, with each withdrawal taking at least 81% of the corresponding vault’s assets. The WBTC vault was left with 87 satoshis, valued by Bitquery at about seven cents.

The WAX account, fasdfas.al, was about 40 minutes old when it made the withdrawals. All five requests were signed in under a minute each, Bitquery says. Bitquery also found a second account tried the negative-fee method about five hours later, but the bridge did not sign those requests and no funds left the vaults.

Bitquery traced the funds to HitBTC deposit addresses

After obtaining gas to claim the assets on the destination networks, the account moved the stolen USDC to a Solana deposit address and swapped the other four assets for ETH before sending them to an Ethereum deposit address. The last of the stolen funds reached a HitBTC deposit address 38 minutes after the first withdrawal, Bitquery says. Both deposits were swept onward within an hour.

The exchange attribution rests on Bitquery’s address labels and the subsequent wallet movements, rather than a public confirmation from HitBTC. The chain record does not establish whether the exchange froze any funds or identify who controls the wallets involved, the firm says. The $115,600 total that reached HitBTC that morning also includes two deposits Bitquery says were not stolen from the bridge.

WAX replaced the contract and added transfer caps

WAX replaced the bridge contract’s code 5 hours and 11 minutes after the first withdrawal and added per-transfer limits later that day, Bitquery reports. The attacker’s USDC withdrawal was 21 times the new cap. The bridge resumed signing withdrawals on the afternoon of October 23, after a 30-hour period in which it signed none.

WAX said its native WAXP token and the WAX blockchain itself were not affected; the incident was confined to the bridge, according to Bitquery’s account of the response. The investigation says the on-chain record can show where funds moved, but not whether HitBTC froze an account.

Sources

  1. Original source Bitquery bitquery.io

Other pages read

  1. WAX (X post, 22 Oct 2026) x.com
  2. WAX block explorer (attack transaction) waxblock.io

Related stories

Explore

More articles