skip to content

đź’§ Looting of Liquid Sidechain Underscores Emerging Cyber Threat to Bitcoin

Bitcoin-14 Blue-3

This article originally appeared in Galaxy Research's weekly newsletter. Subscribe to get timely insights delivered to your inbox every Friday morning.

Liquid Network, a Bitcoin sidechain, had 4,000 BTC stolen by self-described “white hat” hackers, but the attackers have only returned 85% of funds.

On Sunday, hackers siphoned 4,000 BTC (~$320m) from the Liquid Federation, the entities that produce blocks on the federated sidechain and which control peg-in and peg-out to move BTC to and from the sidechain (essentially a bridge in broader crypto lingo). After receiving the 4,000 BTC from federation member and peg-out service Sideswap, the hackers consolidated the funds into their holding address and included a line of text in the OP_RETURN field that said “we are whitehats. contact us on chain.”

Eventually, the main developer behind the Liquid Network codebase, Blockstream, began communicating with the hackers onchain, also via the OP_RETURN field. After some back and forth, the hackers returned 3,400 BTC (85%) to the Liquid Federation.

liquid sankey

Blockstream and the hackers began communicating via encrypted text in the OP_RETURN fields, with Blockstream encrypting its messages to the hackers’ bitcoin address and the hackers encrypting their responses using Blockstream’s publicly published PGP key. However, the remaining 15% (600 BTC) still sits in the hackers’ address and by midweek it appeared that negotiations had broken down, with the hackers sending this message in plaintext on Sep. 9 (directed at Blockstream):

Your dereliction of duty is obvious that you allocated $1.5M (maybe even 0) to secure $5B of assets. This is a flagrant neglect of security and a sign of complete mismanagement. You SHALL pay 10% using your own money as bug bounty or you will cause all your holders a 15% loss for your irresponsibility and stinginess. Even companies that participate in bug bounty programs cannot guarantee complete security, let alone one like yours that remains delusional, greedy, and arrogant to this very day. Anyway we are going to publish the privatekey [sic] to decrypt our conversations afterwards.

Blockstream and the hackers have sent a total of 28 messages in four days. With so many eyes on the hacker address, dozens of other messages have been sent to the hacker, ranging from pleas to return funds, to offers of legal representation, to memecoin advertisements, general spam and vulgarity. The hackers’ address received more human-readable OP_RETURN posts in 1 day than Satoshi’s Genesis Block has received in 10 years.

The original theft was conducted by exploiting a vulnerability in the sidechain node code which allowed the hackers to artificially create 4,000 L-BTC (the Liquid version of wrapped BTC). They were then able to request a valid peg-out from the sidechain back onto the main Bitcoin blockchain. Even though withdraw addresses must be whitelisted, Liquid Federation member SideSwap had been offering an auto-forward service where any entity could withdraw to SideSwap’s own whitelisted address and then it would automatically forward the funds to the withdraw requestor.

Our take

If you take funds and refuse to return them, you are a not a “white hat.” Indeed, the proper method to perform white hat activities is to responsibly and securely disclose the vulnerability to developers. The only time it makes sense to proactively conduct a hack and then attempt to return funds is if the risk of discovery is so high that a black hat could steal them first. Whether or not that was the case with Liquid, the vulnerability was one that could have been disclosed to and patched by Blockstream, unlike the Coldcard vulnerability, which could not be remotely patched. (Real white hats have announced they were able to "steal" 50 BTC from Coldcard victims, have placed the assets in a Wyoming trust, and are looking to return all funds to their rightful owners.) Holding 15% of the stolen funds ransom while you negotiate to keep them is effectively extortion (a crime), not white hat behavior.

White cowboy hat from Calgary
If you take funds and refuse to return them, you are a not a “white hat.”

The self-described white hats’ Sept. 9 message shows their frustration with Blockstream (we can’t see the content of Blockstream’s messages because they are all encrypted to the hackers’ key) and explicitly demands Blockstream pay a 10% bounty (340 BTC, worth ~$26m) from its own funds; if Blockstream doesn’t pay, the hackers suggest they’ll keep the 15% remaining of the Liquid Network’s funds (coins that presumably belong to Liquid Network users). Whether the hackers are frustrated with Blockstream solely from their back-and-forth, or harbored animosity to the firm prior to the exploit, is a matter of conjecture.

While the Coldcard exploit was particularly devastating primarily because of the victim demographic (long-term believers stacking into cold storage), Liquid itself isn’t systemically important to the Bitcoin ecosystem. That said, it is the latest in several high profile BTC thefts – Coldcard, BTCPay Server, now Liquid – that have the Bitcoin community dealing with cyber thefts that usually happen on other, more expressive blockchains. The simplicity of Bitcoin’s coding language and limited programmability have historically helped limit its onchain attack surface when compared to general-purpose smart-contract blockchains like Ethereum and Solana.

Many speculate, of course, that the hackers identified and exploited the vulnerability with assistance from AI. The urgency to harden codebases across Bitcoin and crypto is only rising as the clanker wars continue.

You are leaving Galaxy.com

You are leaving the Galaxy website and being directed to an external third-party website that we think might be of interest to you. Third-party websites are not under the control of Galaxy, and Galaxy is not responsible for the accuracy or completeness of the contents or the proper operation of any linked site. Please note the security and privacy policies on third-party websites differ from Galaxy policies, please read third-party privacy and security policies closely. If you do not wish to continue to the third-party site, click “Cancel”. The inclusion of any linked website does not imply Galaxy’s endorsement or adoption of the statements therein and is only provided for your convenience.