On-chain trackers flag $176 million in outflows from Bitget wallets as users report withdrawal blocks

• Arkham data shows roughly $176 million moving from Bitget-labelled wallets within about a 20-minute window.
• A single address, 0x770b…63Ee, repeatedly received ETH, AVAX, BNB, USDT, USDC and XAUT from the wallets.
• Bitget has not confirmed a breach, even as users report withdrawal failures on the platform.

• $176M value moved from Bitget-linked wallets
• 20 min window in which multiple large transfers were executed in sequence
• 6 distinct asset types swept into a single receiving address

Bitget users began reporting withdrawal problems Thursday (September 24, 2026), the same day on-chain monitors spotted the outflow. According to a report by BeInCrypto, the transfers originated from several Bitget-labelled hot wallets and at least one cold wallet, a combination that typically signals either an emergency sweep or a coordinated theft rather than routine settlement.

Arkham Flags $176 Million Leaving Bitget Wallets in 20 Minutes

Arkham Intelligence data cited in the report shows a series of large transfers executed in rapid succession, all within roughly 20 minutes. The funds came from multiple wallets the platform labels as its own, including at least one cold storage address.

BeInCrypto first flagged the activity in a post on X Thursday, noting more than $100 million had already left a Bitget cold wallet at the time of posting. That figure climbed as additional wallet movements were tracked, reaching the roughly $176 million total.

Address 0x770b…63Ee Collects Six Asset Types From Multiple Wallets

The receiving address, 0x770b…63Ee, appears repeatedly across the transfers, pulling in ETH, AVAX, BNB, USDT, USDC and XAUT from separate Bitget-linked wallets in a short span.

Several wallets sending different assets into one address within minutes is the pattern security researchers associate with exchange compromises, though exchanges do occasionally consolidate holdings during custody changes or wallet maintenance.

Some social media accounts claim a portion of the swept assets was converted into ETH, but that detail does not appear in the underlying data and remains unverified.

Bitget’s Silence Leaves Withdrawal Freeze Unexplained

Bitget has issued no statement confirming or denying a breach as of publication, even as user reports of blocked withdrawals continue to accumulate.

The gap between a 20-minute fund movement and an unexplained multi-hour withdrawal freeze is the detail institutional risk desks will watch most closely. Without proof-of-reserves confirmation or a wallet-by-wallet accounting from Bitget, counterparties have no independent way to size their exposure.

The CCS read. We read this as a custody-concentration problem more than a single exploit story. Any exchange whose hot and cold wallets can be drained through one receiving address within 20 minutes is signaling weaker segregation controls than institutional counterparties typically require, regardless of whether this specific incident turns out to be a hack or an internal transfer gone wrong.

Bitget’s next move is the open question: a confirmed breach disclosure, a proof-of-reserves statement, or continued silence while withdrawals remain frozen. Until the exchange addresses the $176 million in tracked transfers directly, institutional desks are likely to treat the platform as an elevated counterparty risk.