Morning Edition · Friday, October 2, 2026Published at 2:09 AM EDT · New York
Two incidents, Bitget and the Liquid Network, accounted for roughly 92 percent of the month's $768 million in reported losses, and neither started with a smart-contract bug.

Bitget has restored its $300 million protection fund after absorbing the $387.5 million loss it suffered in late September, and is reopening withdrawals in phases. The exchange says the fund sits separate from customer reserves, and that claims remain subject to its own assessment.
The attack did not begin on-chain. Researchers describe a zero-day exploit against two third-party security appliances in Bitget's own infrastructure, where the intruder obtained privileged access, installed a web shell and opened a command-and-control channel before draining hot and warm wallets across seven networks in a window of about three hours. Earliest malicious activity has been dated to 31 August. Bitget chief executive Gracy Chen has said cold wallets and private keys were never compromised. CoinDesk reported that roughly $83 million of stolen XRP was moved into a form Ripple cannot freeze.
September's aggregate numbers follow from that single event plus one more. French-language crypto channel Goku Crypto News put the month at about $768 million lost across 30 days, with two attacks above 90 percent of the damage. Security firms differ at the margin, with CertiK counting 97 incidents and about $768.4 million and PeckShield counting 55 incidents and $766.5 million. The second large loss was the Liquid Network, a Bitcoin sidechain, at roughly $320 million, of which more than $270 million was later returned. Rekt News has logged both Bitget and Liquid Network among its incident write-ups.
For the year, CryptoSlate reports nearly $2.7 billion in losses across 658 incidents through September on CertiK's count, with about $420.4 million frozen or returned and North Korea-linked thefts above $1 billion.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
Bitget converts a solvency question into an operational one by announcing a refilled backstop, vendors of the exploited appliances avoid being named, and exchanges that publish infrastructure audits gain a competitive argument.
The intrusion path through third-party security appliances is corroborated by BleepingComputer and incident reconstructions that count 21 transfers across eight chains, not seven, while the $300 million fund restoration and the chief executive's attribution of the theft to North Korea rest on the exchange's word without third-party attestation.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
The exposure sits with centralized exchange depositors and with the vendors selling security appliances, because the failure path ran through privileged operational infrastructure rather than contract code that an audit or bug bounty would cover. Bitget wants to convert a solvency question into an operational one, and a refilled $300 million backstop plus phased withdrawals is the cheapest way to do that, though a discretionary claims process keeps the residual risk with users. The precedent is the February 2025 Bybit theft, where an exchange with ample reserves survived a nine-figure loss and kept operating while the industry's loss total for the year was permanently reset upward. The likelier outcome over the next two quarters is more of the same shape: a small number of infrastructure and key-handling compromises, not contract exploits, driving the bulk of reported losses, which strengthens the case for exchanges publishing third-party infrastructure audits. That read weakens if the next large incident traces back to an on-chain logic bug in a major protocol.
What to watch
Observations to monitor, not financial advice.
Synthesized from: CryptoSlate · CryptoSlate (2026 losses) · Rekt News · Polylog editors · BleepingComputer
Comments
0No comments yet.