On this page
Key takeaways
- PeckShield counted $766.49 million lost to crypto hacks in September 2026, and the Bitget and Liquid Network incidents made up roughly 92% of it.
- Neither attack depended on stealing a customer's password or private key: Liquid was hit through a validation bug in its node software, and Bitget through zero-day flaws in third-party security products.
- As of November 3, 2026, the Liquid Federation says full BTC backing is restored, but direct federation peg-outs remain restricted; SideSwap conversions are open and may queue.
- For users, the lessons are about custody: limit what you leave on any platform, understand what backs wrapped or bridged assets, and expect fake 'recovery' offers after big hacks.
September 2026 saw heavy crypto theft, with two incidents accounting for most of the reported losses. A bug let attackers drain nearly all the bitcoin backing Blockstream's Liquid Network, and a zero-day breach emptied part of Bitget's hot wallets. Neither depended on a user making a mistake, which is exactly why they are worth understanding.
The numbers
Security firm PeckShield counted 55 major hacks in September with $766.49 million in losses, up about 462% from August's $136.3 million, according to Incrypted's summary of the data. Bitget (about $388 million) and Liquid (about $320 million) together accounted for more than 90% of the month's total.
Liquid Network: a bug in the rules, not a stolen key
What happened
Liquid is a Bitcoin sidechain developed by Blockstream. Exchanges and active traders use it to move bitcoin quickly while keeping transaction amounts hidden from the public. You lock BTC with a federation of member firms and receive L-BTC on Liquid. To get BTC back, you burn L-BTC and the federation releases coins from its reserve after an 11-of-15 multisig approval, as TRM Labs explains.
Liquid hides transaction amounts, so each confidential output carries a cryptographic "range proof" showing its value is within valid bounds, one of the checks that prevents creating spendable value from nothing. Checking these proofs is expensive, so the Elements software caches results. Chainalysis describes the cache flaw (opens in a new tab). The attacker first had a genuine proof checked and remembered, then sent a fake one that the software mistook for the same entry, so nodes let it through without a new check.
On September 6 the attacker minted about 4,000 unbacked L-BTC, requested a withdrawal through an approved operator, and received roughly 3,996 BTC from the reserve. TRM reports the whole sequence took 36 minutes. Because the network software accepted the fake L-BTC as valid, the federation's signers approved the payout. Blockstream said no signing keys were compromised.
The initial partial recovery
Hours later, the attackers posted an on-chain message calling themselves "whitehats" and offered to return funds once the bug was patched. After the fix was deployed, about 3,400 BTC came back, roughly 85% of the total. In its September 8 account, TRM put the amount still held by the attackers at about 598.5 BTC, then worth around $47 million, and described their apparent bounty claim. That was not confirmation of an agreed bounty. Blockstream reported that Liquid later resumed transactions (opens in a new tab) while direct federation peg-outs, the release of BTC from the reserve, stayed restricted. The November 3 update above distinguishes those restrictions from available SideSwap conversions and restored backing.
Bitget: compromised through its own security tools
What happened
Bitget says its systems detected unauthorized transfers from some hot wallets at 19:05 UTC on September 24. Hot wallets are online wallets an exchange uses to process withdrawals quickly. Bitget initially estimated losses at $351.6 million and said its cold wallets were untouched; later counts that included Zcash and TRON transfers put the figure near $387.5 million. Withdrawals were paused while deposits and trading continued, then reopened in stages from September 28, beginning with bitcoin.
Two independent investigations, by SlowMist and Google Cloud's Mandiant, found the entry point was two third-party security appliances. SlowMist traced the earliest malicious activity to August 31, more than three weeks before any money moved, when a zero-day flaw was used on one product. Mandiant described the attacker planting a web shell on one appliance, then moving to Bitget's production wallet server and deploying malicious packages, as BleepingComputer reported.
Chainalysis attributes the theft to North Korea-linked actors. It says the $387 million left in 23 transfers within about three hours, split across Ethereum, XRP Ledger, Zcash and Tron. Stolen XRP was routed through a cross-chain liquidity protocol and came out as bitcoin.
How customers were treated
Bitget said customer balances were not affected because the loss fell within its User Protection Fund, which held more than $464 million before the hack. CEO Gracy Chen told CNBC that the company had restored the fund to over $300 million from its own capital. Only about $1.1 million had been frozen, and she was "not expecting to recover a lot." Bitget also published a self-reported proof-of-reserves ratio of 131% from a September 29 snapshot.
What this means for regular users
Both attacks went after infrastructure rather than individual accounts. Customer passwords and two-factor login do not address the infrastructure flaws described here. Bitget says attackers stole internal access credentials (opens in a new tab); that is distinct from compromising a customer account. What you control is how much of your money sits on infrastructure you cannot inspect.
- Keep exchange balances to what you actively use. Bitget says its customers' balances were untouched because it had a large reserve fund and chose to use it. Not every platform can or will. A wallet you control removes exchange-custody risk but introduces key-management risk; compare options in our hardware wallet comparisons.
- Know what backs a wrapped token. L-BTC, like any bridged or wrapped asset, is only as good as the reserve and the software guarding it. After Liquid's reserve was drained, on-chain negotiations preceded the initial partial return. Later reserve replenishment restored full backing, but the federation announcement does not establish that the attacker returned the rest. Before you use a wrapped version of bitcoin or any other asset, ask who holds the underlying coins and how redemptions are approved.
- Read proof-of-reserves claims carefully. A self-reported reserve ratio is useful, but it is a snapshot the company prepares itself. Look for independent verification and for whether liabilities are included.
- Expect withdrawal pauses. Pausing withdrawals is a normal emergency step. Do not keep money you might urgently need on a single platform.
- Watch for follow-on scams. Large hacks are often followed by fake "compensation" sites and people offering to recover stolen funds for a fee. See our guide to recovery scams.
The bigger picture
In its September 8 account, TRM Labs noted that 2026 had seen a record number of hack incidents, with smaller typical losses than past years, punctuated by occasional very large thefts. September fits that pattern. It also shows two infrastructure risks: attacks on supply-chain components, such as a vendor's security appliance, and on the verification logic of layers built on top of major blockchains.
What to watch next
- Liquid's direct federation peg-outs. Watch for their reopening, separately from SideSwap conversions that are already available. Full backing has been restored; the source of replacement bitcoin and recovery of the coins withheld in September are separate, unresolved questions in these announcements.
- Bitget's vendor disclosures. The original October account left open whether the third-party vendors would be named so other firms using the same products could patch. This update does not establish their current disclosure status.
- Laundering trails. Analytics firms are labeling addresses tied to both incidents, which can lead exchanges to freeze funds when they surface.
For a full overview of common threats and defenses, visit our security and scams hub and our guide to crypto risk management. The original incident account is as of October 2026; Liquid's recovery status was updated November 3, 2026. For Bitget, this update corrects the detection time and distinguishes internal credential theft from customer-account compromise; it is not a full current audit of the incident.
Frequently asked questions
Was Bitcoin itself hacked in the Liquid incident?
No. The flaw was in Elements, the software that runs the Liquid sidechain. The attacker created unbacked L-BTC on Liquid and redeemed it for real BTC held in the federation's reserve; the Bitcoin network worked normally.
Did Bitget customers lose money?
Bitget says user balances were not affected because it covered the loss from its User Protection Fund, which it later topped back up to more than $300 million with company capital.
Is Liquid fully backed again, and can I withdraw?
As of November 3, 2026, the Liquid Federation says its reserves again fully back L-BTC at 1:1. SideSwap says BTC/L-BTC conversions are open, with L-BTC-to-BTC payouts available since October 20 at 1:1 less a 0.1% fee, but queues are possible and direct federation peg-outs remain restricted.
Should I move my crypto off exchanges?
Many people keep only what they actively trade on an exchange and hold long-term savings in a wallet they control. That shifts the risk to your own key management, so set up backups carefully first.
Sources
- 2026's Biggest Hack To Date: Attackers Drained USD 319 Million in Bitcoin From Liquid Network, Then Returned 85% of Funds (opens in a new tab) — TRM Labs
- Liquid Federation: bitcoin reserves fully restored (opens in a new tab) — Liquid Federation
- [SECURITY NOTICE] Bitget exchange hot wallets Incident — September 24, 2026 (opens in a new tab) — Bitget
- The Liquid peg is back to one to one (opens in a new tab) — SideSwap
- Bitget hacked via zero-day in third-party security products (opens in a new tab) — BleepingComputer
- Bitget 'not expecting to recover a lot' from $388 million hack, CEO tells CNBC (opens in a new tab) — CNBC
- How AI Helped Chainalysis Investigators Trace the $387 Million North Korea Stole from Bitget (opens in a new tab) — Chainalysis
- Losses From Cryptocurrency Hacks Hit $766M in September — PeckShield (opens in a new tab) — Incrypted
Published October 4, 2026 by Dave McNaught. Educational content, not financial, legal or tax advice. Spot an error? Request a correction.
