{"id":13741,"date":"2026-09-26T02:50:57","date_gmt":"2026-09-26T02:50:57","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=13741"},"modified":"2026-09-26T02:50:57","modified_gmt":"2026-09-26T02:50:57","slug":"swiss-bank-shields-bitget-institutions-while-retail-funds-freeze","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=13741","title":{"rendered":"Swiss bank shields Bitget institutions while retail funds freeze"},"content":{"rendered":"

<\/p>\n

\n

Bitget says about $387.5 million in assets was transferred to attacker-controlled addresses during a Sept. 24 wallet breach. Its withdrawals remained suspended in notices issued through Sept. 25, even as deposits and trading continued.<\/p>\n

On the day of the breach, Sygnum announced that Bitget’s institutional clients could trade against collateral held at the Swiss bank instead of placing that collateral in Bitget’s wallets.<\/p>\n

The juxtaposition puts a question behind the promise of off-exchange custody: which assets sit beyond an exchange wallet breach, and what still depends on the exchange when trading or withdrawals are disrupted?<\/p>\n

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.<\/p>\n

A breach alongside a new custody route<\/h2>\n

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.<\/p>\n

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.<\/p>\n

The exchange said it identified and remediated the underlying vulnerability and contained the incident. Mandiant and SlowMist were assisting its investigation, according to Bitget.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n