
Liquid Network Paused After Hacker Returns 3,400 BTC, 598 BTC Still Missing
A hacker returned 3,400 BTC to Liquid's federation wallet on September 7, reducing the theft to approximately 598 BTC still outstanding from an estimated $47 million total breach. The network remains paused as Blockstream conducts security work before restart.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
Partial Recovery and Continued Outage
Liquid's federation wallet received 3,400 BTC on September 7, according to CryptoSlate, though the network remains paused the following day despite the partial recovery. According to 99Bitcoins, 598 BTC is still outstanding from the initial theft, suggesting the hacker retained a portion of the stolen funds while returning the majority.
Blockstream listed a public bridge outage the morning after the recovery, indicating security work is ongoing before the network can resume normal operations. The hacker's return of most of the stolen funds, coupled with their message asking "is that ok?," suggests possible negotiation or a shift in the attacker's intent, though their motives remain unclear.
Magnitude and Next Steps
The recovered amount represents the bulk of what CryptoSlate valued at approximately $47 million in Bitcoin taken in the initial breach. No public timeline has been announced for Liquid's restart, and the network's operators have not disclosed the nature of the security vulnerabilities being addressed before the bridge reopens.
Why It Matters
For Traders
Liquid remains inaccessible; any positions locked on the network cannot be moved or closed until Blockstream completes its security audit and restarts the bridge.
For Investors
A major Layer 2 bridge outage raises questions about Blockstream's operational security posture and the resilience of federated sidechain architectures under attack.
For Builders
The incident and resulting pause underscores the operational complexity of custodial bridge federation models and the time required to audit and patch after a live breach.
This article is for information only and is not financial advice. Read the full disclaimer.




