Liquid Network has temporarily halted its sidechain after actors identifying themselves as white hat hackers withdrew nearly 4,000 bitcoins, valued at about $320 million, from the Federation's wallet. As of this edition's close, those responsible have left the bitcoins practically untouched and are using the blockchain itself to communicate with Liquid and state that they will return them once the flaw is fixed.
The scale of the operation has forced, in addition to temporarily halting the network, a request to exchanges to suspend LBTC deposits and withdrawals. Liquid says that the withdrawal was carried out through the SideSwap PAK (Peg-out Authorization Key), but maintains that this key was not compromised, nor were the other keys.
This raises the question of how it was possible to move some 4,000 BTC without compromising the keys that should protect the exit mechanism. Liquid has not yet explained, in the information provided, the technical nature of the vulnerability.
We are whitehats
Those behind the operation present themselves as white hat hackers and have turned the Bitcoin blockchain into their communication channel with Liquid. On September 6 they left a message via OP_RETURN: We are whitehats. Contact us on-chain. The message appears in a transaction linked to the consolidation of 3,998.49748445 BTC, according to the Mempool data provided.
Self-identifying as whitehats does not allow the conclusion that they actually are. But the following operations add an unusual element for an incident of this magnitude: the perpetrators say they want to return the bitcoins. Hours later another message appeared asking that the bug first be fixed and all nodes patched. Only afterwards, they say, will they return the money once they have verified that the problem is solved.
The corresponding transaction shows 3,998.49849036 BTC still concentrated in the address used by those responsible. This introduces an important difference from a conventional theft: in the data provided, the funds do not appear dispersed across a multitude of addresses.
4,000 Bitcoin visible onchain
An amount close to 4,000 bitcoin remains concentrated and visible onchain. Shortly afterwards another message appeared: I am sending most of it back to the address, is that okay? The operation keeps about 3,998.49848550 BTC in the address from which the funds are being managed.
If the intention expressed in these messages is confirmed, the incident could end with the return of practically all the bitcoins. In the early hours of September 7, however, that full return cannot yet be considered completed based on the sources provided.
The scale of the withdrawal is especially visible in the Mempool data. The address flagged by Liquid to track the incident shows, as of this edition's close, a confirmed balance of 197.47 BTC, with 79 confirmed UTXOs. Its history reflects a sharp drop from more than 4,000 BTC to the current level.
Among the unspent outputs remaining in the address are amounts of 43.28 BTC, 40.96 BTC, 27.24 BTC, 17.29 BTC and 8.16 BTC, in addition to numerous smaller amounts. The transactions also allow observation of the process that preceded the concentration of the funds. One operation records an input of 3,995.99999857 BTC, to which other movements are added before reaching approximately 3,998.5 BTC.
Earlier operations show numerous movements identified as Liquid Peg Out, some of considerable size. Among them are outflows of 89.80 BTC, 14.57 BTC, 8.46 BTC and 7.80 BTC. The onchain information allows the movements to be verified, but does not by itself explain what vulnerability made the operation possible.
A problem for Liquid that goes beyond recovering the $320 million
Liquid's reaction has been to temporarily halt the infrastructure. The bridge nodes have been deactivated, so no new transactions can be sent. In practice, Liquid acknowledges that the sidechain remains paused while Federation members work to resolve the incident. Exchanges have been notified and have paused, or are about to pause, LBTC deposits and withdrawals.
Liquid says that other assets on the network, such as USDT, DePix and RWA, are not affected by the security incident, although the halting of the network has operational consequences for its users and wallets. The incident affects Liquid Network, not the Bitcoin protocol. In fact, Bitcoin is in this case functioning as a public record both of the fund movements and of the peculiar conversation between the parties.
The possible return of the bitcoins could prevent the incident from ending up as a loss of some $320 million, but it would not solve the main problem the episode leaves behind. Liquid will have to explain what allowed nearly 4,000 BTC to be withdrawn through the SideSwap PAK if, as it claims, that key was not compromised.
Those responsible themselves maintain that a bug exists and demand that all nodes be patched before returning the funds. Liquid, for its part, acknowledges the incident and has chosen to halt the network, but in the information available it still does not offer a technical explanation of the flaw.
It is not only a question of knowing whether the bitcoins will return. An infrastructure designed to custody and move BTC between Bitcoin and Liquid has had to be halted after someone managed to withdraw around 4,000 BTC without, according to Liquid, the keys having been compromised.




