TRM Labs says software flaw let attackers take nearly 4,000 BTC from Liquid's reserve
TRM Labs says attackers used a software flaw to mint unbacked L-BTC and redeem almost 4,000 Bitcoin from Liquid's reserve on Sept. 6 without stealing any private keys.
Why it matters
The loss came from a software fault rather than a key compromise, so keeping keys offline did not stop it. Whether insurers cover the shortfall, and whether reimbursement denominated in dollars or Bitcoin, decides how much of the roughly 4,000 BTC customers get back.
Key facts
Almost 4,000 Bitcoin left Liquid's reserve on Sept. 6 in a withdrawal the network approved.
4,000 BTCReported by CryptoSlate
The private keys used to authorize the withdrawals were not stolen.
Reported by CryptoSlate
TRM Labs reconstructed the attack and attributes it to attackers exploiting a software flaw.
Reported by CryptoSlate
Attackers created L-BTC without putting in the Bitcoin to back it, then exchanged those tokens for real coins.
Reported by CryptoSlate
Software accepted a withdrawal that should never have qualified.
Reported by CryptoSlate
Crypto insurance can cover losses without guaranteeing customers receive full reimbursement.
Reported by CryptoSlate
Repayment calculated in dollars can leave customers short when holdings are measured in Bitcoin.
Reported by CryptoSlate
What happened
Almost 4,000 Bitcoin left Liquid's reserve on Sept. 6 through a withdrawal the network approved, according to both CryptoSlate and Crypto News, which published the same account. TRM Labs reconstructed the attack and attributes it to a software flaw that let attackers create L-BTC without depositing the Bitcoin to back it, then redeem those tokens for real coins from the reserve. Neither report says the private keys authorizing the withdrawals were stolen; CryptoSlate's account says software approved a withdrawal that should never have qualified, and the operators responsible for approving withdrawals trusted incorrect information. CryptoSlate adds a detail the later piece omits, describing a multi-party approval process where several signers relied on the same wrong account balance. On repayment, CryptoSlate reports that crypto insurance may cover some losses without guaranteeing full reimbursement, and that compensation calculated in dollars can leave customers short in Bitcoin terms. The only independent account of the mechanism comes from TRM Labs, which both outlets cite rather than reporting directly, and no Liquid response appears in the evidence.
How the story developed
- First report
First report by CryptoSlate
Why keeping your private keys safe won’t always stop crypto theft
- Update
TRM Labs traces the loss to a software flaw rather than stolen keys
TRM Labs' reconstruction says attackers minted L-BTC without backing it and redeemed the tokens for real coins, while the keys authorizing the withdrawal stayed in place.
- Update
Sept. 6 withdrawal of nearly 4,000 BTC from Liquid's reserve
Almost 4,000 Bitcoin left the reserve in a withdrawal the network approved, with the private keys never stolen.
- Update
CryptoSlate raises repayment and insurance questions
Only the earlier report discusses insurance coverage and the risk of dollar-denominated compensation leaving customers short in Bitcoin terms; the later piece covers the same ground without those specifics.
How coverage built up
Independent sources over time, counted the way the consensus panel counts them: a republication of a wire story does not move the line.
- 20 Sept 2026, 20:30 UTC: CryptoSlate — 1 independent source, 1 reports
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| CryptoSlate Crypto media | Why keeping your private keys safe won’t always stop crypto theft | Original | |
| Crypto News (CryptoNews.net) Aggregator | Why keeping your private keys safe won’t always stop crypto theft | Syndicated |