Skip to content
Crypto.world

The Ledger

Predict.fun Wallet Drains Hit $398,000 Across 29 Accounts

Bitquery traced 397,708 USDT drained from 29 Predict.fun accounts on BNB Chain in two waves on October 22 and 27. The transactions were signed with the accounts’ owner keys, while Predict.fun said its externally hosted API documentation site may have been compromised.

Predict.fun Wallet Drains Hit $398,000 Across 29 Accounts

“fully reimburse all affected users”

Predict.fun, in a statement quoted by Bitquery

Predict.fun says it will repay users after 397,708 USDT left 29 of its BNB Chain accounts in two waves, on October 22 and October 27. Bitquery’s investigation found that each drain was signed with the affected account’s owner key. It found no Predict.fun market or exchange contract called in the 33 drain transactions.

The October 27 wave brought the incident into public view, but it was not the first. Six accounts lost 125,029 USDT five days earlier, a wave Bitquery found no public report of before the later outflows. The October 27 wave accounted for 272,679 USDT, most of it taken in a 34-minute run.

Two waves, five days apart

On October 27, 19 accounts lost $262,000 over 34 minutes, about one account every two minutes. The largest single loss in the investigation was 109,000 USDT, taken from one account in two transfers during the October 22 wave. Across all 29 affected accounts, the five largest losses represented 73% of the total.

Bitquery’s count of 397,708 USDT covers the two main waves. The investigation separately records another 4,900 USDT taken from one account about an hour after Predict.fun’s statement; that money went to Railgun. Keeping that later drain separate matters: it is not included in the 397,708-USDT figure.

Owner keys signed every drain

Predict.fun accounts use smart wallets controlled by an owner key. Bitquery says each of the 33 drains it examined carried a signature from the affected wallet’s own key, and the wallet performed the transfer after validating that signature. The on-chain record establishes which key signed, but not who held the key or how it was obtained.

The investigation describes Predict.fun’s API as a way to place trades from users’ own code. Its developer instructions direct users of smart wallets to export a Privy key for programmatic access. A copied key could authorize transfers from the wallet, but Bitquery’s findings do not establish how the keys involved in these drains were exposed.

The API-docs theory remains unproven

Predict.fun said its API documentation site, hosted by an outside provider, may have been hacked and that it had taken the site offline. The company also promised a full report and reimbursement for affected users. Bitquery says the proposed connection is plausible because API users may export their owner keys, but Predict.fun has not said how the site may have been used or shown that it caused the thefts.

The money moved quickly after leaving the accounts. Bitquery traced transfers from BNB Chain through Relay, LI.FI and Across to Ethereum; it counted 166.8 ETH deposited into Tornado Cash across the two waves. The first Tornado Cash deposit after the October 27 run came less than 11 minutes after that run began, and the investigation says the deposits were complete before the first public post about the drains.

A further 4,900 USDT left after the statement

The later 4,900-USDT loss shows that taking the documentation site offline did not prevent every subsequent transfer. Bitquery traced the funds from that account into Railgun, rather than Tornado Cash. Its data covers BNB Chain transfers through 16:22 UTC and Ethereum activity through 15:57 UTC on October 27, so the findings do not describe transactions after those cutoffs.

Sources

  1. Original source Bitquery bitquery.io

Other pages read

  1. Predict.fun (X post, 27 Oct 2026) x.com

Related stories

Explore

More articles