Sygnum’s route is for eligible institutional clients who onboard with its bank. The companies have not disclosed how many Bitget clients use it or whether any Sygnum-held collateral was connected to this incident.
A breach alongside a new custody route
Bitget said its systems detected unauthorized transfers at 18:31 UTC on Sept. 24. Its initial notice placed the affected funds at about $351.6 million and said the breach reached portions of its hot and warm wallet layers, while cold wallets remained secure.
In a Sept. 25 update, Bitget raised the estimated assets transferred to attacker-controlled addresses to about $387.5 million after including Zcash and TRON transfers in a fuller accounting. It said the revision did not represent a fresh wave of unauthorized transfers.
The exchange said it identified and remediated the underlying vulnerability and contained the incident. Mandiant and SlowMist were assisting its investigation, according to Bitget.
Bitget’s withdrawal notice said withdrawals were temporarily unavailable while deposits and trading stayed operational. The exchange promised to announce a withdrawal plan or status by Sept. 26 at 04:00 UTC.
For a customer with an ordinary Bitget balance, a displayed balance and the ability to trade do not by themselves provide an exit while withdrawals are paused.
Sygnum said Bitget’s institutional clients can use its Protect service for spot and derivatives trading while pledged collateral remains in Sygnum custody in Switzerland. Bitget mirrors the balance as trading margin.
The bank lists Bitcoin, Ethereum, stablecoins and US Treasuries among the eligible collateral. Its published process requires a client to onboard with Sygnum, sign a contractual framework, open a Protect portfolio, and pledge assets before receiving exchange margin.
Under Sygnum’s description, the collateral is held in segregated accounts off the bank’s balance sheet and is bankruptcy remote under Swiss banking law. Keeping the pledged assets at the bank reduces direct custody exposure to Bitget’s own wallets.
It also addresses the concern that if an exchange faces financial distress, the collateral is intended to remain outside its estate. These are features of the arrangement as Sygnum describes it.
The announcement is dated Sept. 24 but does not state when Bitget client access became operational, nor that the integration preceded the 18:31 UTC breach or arose in response to it, nor does it identify any Bitget client who had completed onboarding, give a Bitget-specific collateral balance, or say whether Sygnum-held assets were involved in the incident.
Figures in the release for Protect’s total assets and the trading-volume share of all its integrated exchanges do not measure Bitget client uptake.
Related Reading
Bitget’s $351.6 million hack pushes September crypto losses to 2026 high
The limits of custody and a separate backstop
Protect’s public page advertises flexible collateral top-ups and withdrawals. It does not publish the Bitget-specific contract that would determine when pledged assets can be released, how positions are settled, or what happens to margin if Bitget pauses its withdrawal service.
A trading balance mirrored at an exchange is also not the same thing as an ordinary customer’s withdrawable exchange balance.
Trading still depends on the exchange’s order, margin, and settlement processes even when the pledged assets are held elsewhere. Segregated custody can reduce exposure to theft from Bitget-held wallets and to Bitget insolvency, as Sygnum describes.
The public materials do not establish that a Protect client can instantly reclaim pledged collateral during an exchange disruption, or that an exchange’s operational problems could never delay settlement. They equally do not show that any Sygnum client is blocked from its collateral in this incident.
The arrangement creates an optional boundary between institutional collateral and Bitget wallet custody.
For users holding assets on Bitget, the exchange pointed to its User Protection Fund. In its initial Sept. 24 notice, Bitget said the fund was worth more than $464 million and that the then-estimated $351.6 million incident fell within its coverage.
Its public fund page lists 5,500 $BTC and says users may claim for qualifying losses from platform-wide events beyond their own actions or trading behavior. Bitget reserves the right to assess and investigate claims.
The dollar value of a Bitcoin-denominated fund moves with Bitcoin’s price. Bitget’s report for August put the fund’s monthly average at $382 million and its month-end value near $432 million on the same 5,500 $BTC holding.
Bitget also said it froze some affected assets through work with industry partners, but its Sept. 25 update did not quantify the frozen or recovered amount. The next measurable tests are a confirmed withdrawal timetable, a firmer loss and recovery accounting, and the terms of any fund disbursement.
For the custody comparison, the missing facts are Bitget-specific Protect uptake and the contract governing collateral release and settlement when the exchange is under strain.
