Community Investigation

Bitget’s $351.6M Hot-Wallet Breach: What 289 Addresses Reveal — and What Remains Unproven

REPORT
REPORT

September 26, 2026

Executive Summary

Bitget confirmed unauthorized transfers from hot wallets at 18:31 UTC on 24 September 2026. The exchange stated that cold wallets were not affected and that its protection fund exceeded $464 million. Public reporting placed the loss at approximately $351.6 million.

SentinelTX expanded the investigation to 289 addresses and 41 evidence items across Ethereum, Arbitrum, Avalanche and BNB Chain. The pattern is consistent with a hot-wallet signing or key compromise: one consolidation EOA appeared across chains, stablecoins were rapidly swapped into ETH, funds crossed bridges, and Ethereum proceeds were split into fixed-size tranches.

The clearest recovery lead is 20,763,612.55 USDC routed from Avalanche and Arbitrum through a common receiver into a Circle-labeled address. No centralized-exchange deposit or mixer exposure was confirmed in the reviewed scope.

Incident Anchors

Item

Value

Status

Evidence

Official confirmation

24 Sep 2026, 18:31 UTC

Confirmed

Bitget statement

Public loss estimate

$351.6M

Reported

CEO / media

SentinelTX scope

289 addresses; 41 evidence items

Confirmed

Case output

CEX or mixer exposure

None confirmed

Open

Reviewed scope

Core Wallet Matrix

Role

Address

Chain

Evidence

Primary consolidation

0x770b10b273fC44Fe9197D6bF20F145c2e98463Ee

Multi-chain

High

USDT0-to-ETH swap

0xe410a2e5710ee787bcaa63f52a3943ff71f0d946

Arbitrum

High

Stablecoin receiver

0xb3fa262d0fb521cc93be83d87b322b8a23daf3f0

Arbitrum / Avalanche

High

Circle-labeled route

0xfd78ee919681417d192449715b2594ab58f5d002

Multi-chain

High label; destination open

Ethereum source

0x469Ac1406dE92f82C0563477240a3627057425DC

Ethereum

High

Ethereum hub

0xa6dd3f218b65e32ccc37be30f74884133c655545

Ethereum

High inbound; mixed outflow

Avalanche downstream

0x5085b3d52b5587c18ef456fcbcde9a11d48340f8

Avalanche

High

BNB downstream

0x7c96279ec1e888aa56b9b836e0db26ca48573e1c

BNB Chain

High

What the Cross-Chain Flow Shows

The primary consolidation address was active on Ethereum as early as 7 February 2026, contradicting descriptions of it as newly created. TRDB labels on two upstream addresses are useful leads, but do not independently prove Bitget ownership.

Confirmed Chain-Level Movements

Chain

Confirmed movement

Action

Confidence

Ethereum

1,541.51 ETH

Source to distribution hub

High

Arbitrum

19,668,851.77 USDT0 → 7,111.344304 ETH

Swap and split

High

Avalanche

821,000 AVAX + 8,204,678.8 USDC

Two downstream routes

High

BNB Chain

12,719.45 BNB

Router-linked downstream

High; partial path

Arbitrum: Swap, Split and Partial Stablecoin Recovery

On Arbitrum, 19,668,851.77 USDT0 reached a dedicated swap wallet and was converted through UniswapX and 1inch intents into 7,111.344304 ETH. One branch converted 2,513 ETH into 6,561,140.178933 USDC; another 26,830.363654 USDC joined the same receiver before the route reached a Circle-labeled address.

Key Transactions

Chain

Transaction

Movement

Status

Ethereum

0xbb7f4d68c339f44e048b45bcee466bc75a086fc02d89cda8242b5031639bf8b4

1,541.51 ETH → hub

Incident-anchored

Ethereum

0x872dd53e25e071ae7ae6b653a44ff18cfc041e8fdea4ac0da72c6ef97ba4ede1

10,000 ETH

Gross hub outflow only

Ethereum

0xd955a11839263c24e49ddb850b17663d0122904cee1fb9c436e04203a88ec288

10,000 ETH

Gross hub outflow only

Ethereum: Anchored Inflow vs. Gross Hub Activity

A confirmed transaction moved 1,541.51 ETH from the Ethereum source to the hub. The hub later sent several much larger tranches. Those gross outflows cannot all be attributed to this incident because only the 1,541.51 ETH inbound is directly anchored to the investigated path.

Bridges, Routers and Recovery Leads

Interaction with a router or bridge does not mean that service controlled the attacker.

Priority

Address / service

Observed amount

Action

1

0xfd78ee919681417d192449715b2594ab58f5d002 / Circle

20,763,612.55 USDC

Preserve and freeze route

2

0xe35e9842fceaca96570b734083f4a58e8f7c5f2a / Across

1,600 ETH

Trace destinations

3

0xef4fb24ad0916217251f553c0596f8edc630eb66 / deBridge

1.001213 ETH

Preserve destination tx

4

0x2bca667d37afe8d065ca46e3261e9442e77cbeae

~1,997 ETH residual

Monitor and trace

5

0x5085b3d52b5587c18ef456fcbcde9a11d48340f8

~620,999.99991 AVAX

Monitor and trace

What Remains Unproven

No threat actor has been identified. No evidence confirms a CEX deposit or mixer. The direct link from the multi-chain consolidation address to 0x469Ac1406dE92f82C0563477240a3627057425DC was not independently confirmed; it remains a third-party Bubblemaps claim. Zero-value and tiny lookalike transfers were excluded as address-poisoning noise.

Untraced Remainder

Chain

Unresolved amount / path

Next step

Ethereum

Much of 34.75M USDT/USDC; hub downstream

Separate incident funds from prior activity

Arbitrum

~1,997 ETH + ~990 ETH; Across destinations

Trace destination chains

Avalanche

~620,999.99991 AVAX; router output

Resolve router recipients

BNB Chain

~9,719.45 BNB

Trace beyond shared routers

Conclusion

The evidence confirms coordinated cross-chain dispersal and a high-priority Circle recovery route, while leaving substantial balances and several bridge destinations unresolved. The urgent action is preservation and freeze outreach for the Circle-labeled path, followed by destination tracing for Across and deBridge.

Evidence note: wallet balances and labels reflect the SentinelTX investigation cutoff. Public statements, third-party labels and analytical inference are separated from transaction-confirmed facts.

post_like_sub0
post_total_comment_sub0

7 reads

0/500 bytes