DeFi hacks in 2026: what broke and why

This page lists major DeFi hacks of 2026. For each one: when it happened, how much was lost, what broke, and what kind of bug it was.

Last updated: 2026-10-21. We add new entries every week.

Sources are public only: rekt.news, official post-mortems and security-firm reviews. Losses are what the linked source reported. Where sources disagree, we say so.

Guides for the smart contract vulnerabilities named in these rows are on a separate index.

Summary

Summary table of DeFi hacks in 2026

DeFi hacks of 2026 with date, chain, reported loss, root cause, bug class, and source
Jan 8 Truebit Ethereum $26.2M (Defimon: $26.4M) Integer overflow in a five-year-old contract Arithmetic Yes rekt.news
Jan 19–20 Makina Finance Ethereum $4.13M (other outlets: ~$5.1M) Flash-loan manipulation of pool prices used for share price Oracle manipulation, flash loan Yes rekt.news
Feb 15 Moonwell Base $1.78M Oracle priced cbETH with the cbETH/ETH ratio, not a USD price Oracle misconfiguration Yes rekt.news
Mar 5 Solv Protocol Not stated by source $2.73M Callback fired before balances were updated, tokens minted twice Reentrancy Yes rekt.news
Mar 2026 Resolv Labs Not stated by source $24.5–25M Compromised GitHub credential led to stolen signing credentials and unlimited minting Off-chain: key / supply chain No rekt.news
Apr 13 Dango Dango chain $1.9M (most recovered) Contract did not check donation amounts were positive Input validation Yes Halborn
Apr 23 GiddyDeFi Ethereum $1.3M Signed transaction replayed with parameters the signature did not cover Signature / authorization Yes Halborn
Sep 17 Nostra Starknet ~$3.5M Thin-pool price blended into an oracle price Oracle manipulation Yes rekt.news
Apr 1 Drift Solana $285M Social engineering of signers, privileged keys compromised Off-chain No rekt.news
Apr 18 KelpDAO Ethereum and Arbitrum (LayerZero bridge) ~$290–292M Single verifier fed false data via compromised RPC nodes Off-chain No rekt.news
Oct 14 UNCX Vesting V2 Ethereum, BNB Chain, Base, Robinhood Chain About $807,609 (UNCX report; Blockaid tally: about $1.49M) Cancel reused an old share record after a release, so the pool counted too few shares Logic error, accounting Yes UNCX incident report
Oct 17 BiFi Lending ( pre-hack replay ) Ethereum $165.6K drained, about $6.5K not returned Interest grew with idle time multiplied by a rate that a flash loan could raise Logic error, flash loan Yes Olympix
Oct 17-18 Qubic Qubic About $1.3M (Cointelegraph: about $1.4M) Wallet seeds were made with weak randomness, so an attacker could guess them Off-chain: wallet key generation No (wallet app, not contracts) 0xCERT
Oct 18-19 AlpsCon AI Trade Hub BNB Chain 152,809 USDC A new deposit received rewards paid out before it existed. The access gate trusted a test account with a public private key. Logic error, access control Yes Tozvan

Biggest of 2026

Biggest DeFi hacks of 2026

The ten largest DeFi hacks of 2026 so far, ranked by the loss reported on the rekt.news leaderboard.

1 Liquid Network $320M (about 3,400 of roughly 4,000 BTC came back a day later) Sep 6 Node software bug: range-proof check cache rekt.news
2 KelpDAO About $290M Apr 18 Off-chain: infrastructure rekt.news
3 Drift Protocol $285M Apr 1 Off-chain: social engineering of signers rekt.news
4 Tectonic $120.4M ($111.2M reversed by a Cronos rollback) Aug 30 Oracle manipulation: thin-pool collateral price rekt.news
5 Nesa About $50M (Bubblemaps estimate) Aug 24 Chain software bug: Cosmos EVM balance accounting rekt.news
6 Humanity Protocol $36.4M Jun 8 Off-chain: multisig keys rekt.news
7 Step Finance $27.3M Jan 31 Off-chain: compromised team devices rekt.news
8 Truebit $26.2M Jan 8 Arithmetic: integer overflow rekt.news
9 Resolv Labs $25M Mar 22 Off-chain: supply chain rekt.news
10 AFX Trade $24.15M Jul 22 Off-chain: bridge validator keys rekt.news

Two larger thefts in 2026 were not DeFi hacks, so they are not in this table. The Bitget exchange lost $387.5M on Sep 24 (rekt.news). A Coldcard hardware wallet firmware bug led to about $130M in thefts, per Galaxy Research (rekt.news).

All time

Biggest DeFi hacks of all time

The ten largest hacks of DeFi protocols, bridges and chains, ranked by the loss reported on the rekt.news leaderboard.

1 Ronin Network $624M Mar 23, 2022 Off-chain: 5 of 9 bridge validator keys rekt.news
2 Poly Network $611M Aug 10, 2021 Access control: a cross-chain message called a privileged function rekt.news
3 BNB Bridge $586M Oct 6, 2022 Proof verification: forged IAVL proof rekt.news
4 Wormhole $326M Feb 2, 2022 Signature verification bypass rekt.news
5 Liquid Network $320M Sep 6, 2026 Node software bug: range-proof check cache rekt.news
6 KelpDAO $290M Apr 18, 2026 Off-chain: infrastructure rekt.news
7 Drift Protocol $285M Apr 1, 2026 Off-chain: social engineering of signers rekt.news
8 Cetus $223M May 22, 2025 Arithmetic: overflow check missed a path rekt.news
9 Euler Finance (pre-hack replay) $197M Mar 13, 2023 Logic error: donation skipped the liquidity check rekt.news
10 Nomad Bridge $190M Aug 1, 2022 Initialization: the zero root was trusted, so forged messages passed rekt.news

The rekt.news leaderboard also ranks exchange and custody thefts, such as ByBit at about $1.4B in 2025 (rekt.news). They are not DeFi hacks, so this table leaves them out.

We ran Guardix on Euler Finance's code from before the 2023 hack. What it flagged and what the run does not show: Euler Finance pre-hack replay.

The pattern

The pattern in 2026: most money was lost off-chain

By value, most 2026 losses did not come from contract bugs. Halborn's H1 2026 report says off-chain causes (compromised keys, signing infrastructure, social engineering) drove 96% of H1 2026 losses (Halborn).

Rekt makes the same point about Drift and KelpDAO: roughly $577M lost in under three weeks, with the code never the target (rekt.news: Wrong Attack Surface).

We'll be plain about what that means. A code audit does not cover keys, signers or infrastructure. That includes ours. Contract bugs still lose real money, and they are what the sections below cover.

Code bugs

Code-level DeFi hacks of 2026 by bug class

Oracle manipulation

An oracle gives a contract a price. If an attacker can move that price, or the contract reads the wrong number, the contract mis-values collateral. Oracle manipulation is OWASP Smart Contract Top 10 (2025) SC02. Checklist: oracles and price inputs. How Guardix checks price reads: DeFi oracle and price-manipulation checks

Makina Finance - January 19–20, 2026

Loss:
$4.13M per rekt.news; other outlets report ~$5.1M
Chain:
Ethereum
Root cause:
A share-price value was derived from Curve pool states. An attacker moved those states with a flash loan inside one transaction. Per rekt, this attack type was listed as out of scope in one of the audits.
Bug class:
Oracle manipulation, flash loan (OWASP SC02, SC07)
Code bug?
Yes
How a pre-audit check relates:
Oracle manipulation and flash-loan price movement are classes Guardix checks for in a pre-audit.

Moonwell - February 15, 2026

Loss:
$1.78M in bad debt (as reported by rekt.news)
Chain:
Base
Root cause:
A governance upgrade enabled a new oracle. It treated the cbETH/ETH ratio (about 1.12) as a dollar price and skipped the ETH/USD multiplication. Liquidators then seized cbETH collateral at a fraction of its value.
Bug class:
Oracle misconfiguration (OWASP SC02)
Code bug?
Yes (a configuration and pricing error)
How a pre-audit check relates:
Oracle and price-input errors are a class Guardix checks for in a pre-audit.
Sources:
rekt.news

Nostra - September 17, 2026

Loss:
About $3.5M borrowed against inflated collateral (as reported by rekt.news, confirmed by Nostra)
Chain:
Starknet
Root cause:
An attacker-seeded, thin-liquidity pool produced a distorted price for the NSTR token. Per rekt, the oracle blended that quote with a clean one instead of rejecting the gap. One account borrowed against the inflated collateral.
Bug class:
Oracle manipulation (OWASP SC02)
Code bug?
Yes (oracle design). The rekt piece says there was no flash loan and no reentrancy bug.
How a pre-audit check relates:
Oracle manipulation is one of the classes Guardix checks for in a pre-audit.
Sources:
rekt.news

Arithmetic

Arithmetic bugs happen when a number goes past its limit or a calculation is wrong. This is OWASP SC08 and SWC-101. Checklist: arithmetic

Truebit - January 8, 2026

Loss:
$26.2M, 8,535 ETH (as reported by rekt.news). Defimon reports $26.4M.
Chain:
Ethereum
Root cause:
An unchecked integer overflow in a contract deployed about five years earlier. The attacker minted over 240 million TRU, burned them for ETH, and repeated it.
Bug class:
Arithmetic (OWASP SC08, SWC-101)
Code bug?
Yes
How a pre-audit check relates:
Arithmetic errors are a class Guardix checks for in a pre-audit.

Reentrancy

Reentrancy means a contract calls out, and the callee calls back in before the first call finishes. OWASP SC05, SWC-107. Checklist: reentrancy

Solv Protocol - March 5, 2026

Loss:
$2.73M, 38 SolvBTC (as reported by rekt.news, from Solv's statement)
Chain:
Not stated by source
Root cause:
A token callback fired during a mint before the books were balanced. 135 BRO went in and 567 million came out, looped 22 times. Rekt describes it as a self-reentrancy attack and says a checks-effects pattern or a reentrancy guard on the mint would have closed the window.
Bug class:
Reentrancy (OWASP SC05, SWC-107)
Code bug?
Yes
How a pre-audit check relates:
Reentrancy is one of the classes Guardix checks for in a pre-audit.

Input validation

A contract trusts a value it never checked: zero, negative, too large, wrong length. OWASP SC04. Checklist: input validation

Dango - April 13, 2026

Loss:
$1.9M. About $410,000 was cashed out (later returned) and $1.49M was stuck on the platform and recovered (as reported by Halborn).
Chain:
Dango chain
Root cause:
The contracts did not verify that donation amounts were positive.
Bug class:
Input validation (OWASP SC04)
Code bug?
Yes
How a pre-audit check relates:
Input validation is one of the classes Guardix checks for in a pre-audit.

Signatures and authorization

A signature must cover everything that matters, and must not work twice. OWASP SC01 (access control), SWC-121, SWC-122. Checklist: signatures

GiddyDeFi - April 23, 2026

Loss:
$1.3M (as reported by Halborn)
Chain:
Ethereum
Root cause:
The attacker replayed a legitimate transaction and changed parameters that the signature did not cover.
Bug class:
Signature / authorization (SWC-121, SWC-122)
Code bug?
Yes
How a pre-audit check relates:
Signature and authorization flaws are a class Guardix checks for in a pre-audit.

Logic errors in accounting and rewards

A contract keeps its own records of shares, interest or rewards. If one function updates a record and another reads an old copy, the numbers stop matching the tokens the contract holds. An attacker then withdraws the difference. This is OWASP SC03 (logic errors). Checklist: business logic

UNCX Vesting V2, October 14, 2026

Loss:
About $807,609 in realized or routed value, per UNCX's incident report. Blockaid's running tally was about $1.49M. Later transactions returned 82.14M X tokens and about 23.87 ETH.
Chain:
Ethereum, BNB Chain, Base and Robinhood Chain
Root cause:
Releasing a vested position removed its shares from the pool total but kept the old deposit record. The attacker then sent tokens in without new shares and topped the position up. Cancel reused the old record and removed too many shares from the total. A small position left in the pool could then withdraw tokens that belonged to other projects' vesting schedules. UNCX says the exploit calls did not use admin functions.
Bug class:
Logic error, share accounting (OWASP SC03)
Code bug?
Yes
How a pre-audit check relates:
Accounting and logic bugs are a class Guardix checks for in a pre-audit.

BiFi Lending, October 17, 2026

Loss:
165,575 USDT drained. 159,103.65 USDC came back on October 18, so about $6.5K was not returned (as reported by Olympix).
Chain:
Ethereum
Root cause:
BiFi counted deposit interest as the number of blocks since the market's last action times the current interest rate. The USDT market had been idle for about 36 days. A flash loan of 40.5M USDT raised the utilization, and with it the rate, inside the same transaction. An MEV operator copied the attack and ran it before the original attacker's contract was called.
Bug class:
Logic error, flash loan (OWASP SC03, SC07)
Code bug?
Yes
How a pre-audit check relates:
Accounting and logic bugs are a class Guardix checks for in a pre-audit.

AlpsCon AI Trade Hub, October 18-19, 2026

Loss:
152,809 USDC (as reported by Tozvan, citing ExVul). Tozvan dates the report October 19. Telem says the attack came about five hours before the team removed the test account on October 18.
Chain:
BNB Chain
Root cause:
Two faults worked together. The reward contracts let a fresh deposit claim rewards paid out before that deposit existed. The deposit gate trusted a whitelisted wallet that was the default Hardhat test account, whose private key is public. The attacker used EIP-7702 to run code as that account and a flash loan of about 1.03M USDC to buy ALPS tokens and make the deposit.
Bug class:
Logic error, access control (OWASP SC03, SC01)
Code bug?
Yes, plus a configuration error in the whitelist
How a pre-audit check relates:
Accounting, logic and access-control bugs are classes Guardix checks for in a pre-audit. A pre-audit reads code, so it does not see which wallets a team adds to a whitelist after deployment.
Sources:
Tozvan · Telem

Off-chain

Off-chain DeFi hacks of 2026: keys, signers and infrastructure

These are not code bugs. An audit of the contracts does not cover them.

Drift Protocol - April 1, 2026

Loss:
$285M (as reported by rekt.news and Halborn)
Chain:
Solana
Root cause:
Attackers got pre-signed authority from Drift's Security Council by social engineering, then used it to add a worthless token as collateral and withdraw funds. Halborn attributes it to the Lazarus Group.
Bug class:
Off-chain: key / signer
Code bug?
No
How a pre-audit check relates:
Not a code bug. A code audit, ours included, does not cover key or signer security.

KelpDAO rsETH bridge - April 18, 2026

Loss:
About $290M per rekt.news; $292M per Halborn. 116,500 rsETH.
Chain:
Ethereum and Arbitrum (a LayerZero cross-chain bridge). Per rekt, about $178M was drained on Ethereum and $72M on Arbitrum.
Root cause:
A single verifier was fed false data through compromised RPC nodes, and the bridge released funds on what looked like a valid message. LayerZero blamed KelpDAO's single-verifier setup. KelpDAO said it was LayerZero's documented default. Both are per rekt.
Bug class:
Off-chain: infrastructure
Code bug?
No
How a pre-audit check relates:
Not a code bug. A code audit, ours included, does not cover key, signer or infrastructure security.

Resolv Labs - March 2026 (per Defimon; rekt published Apr 8)

Loss:
$24.5–25M in ETH (rekt.news says about $25M; rekt's "Wrong Attack Surface" piece says $24.5M)
Chain:
Not stated by source
Root cause:
A supply-chain attack. A compromised GitHub credential led to a malicious CI/CD workflow that exfiltrated signing credentials. A key in Resolv's cloud infrastructure then gave the attacker unlimited minting.
Bug class:
Off-chain: key / supply chain
Code bug?
No
How a pre-audit check relates:
Not a code bug. A code audit, ours included, does not cover key, signer or infrastructure security.

Qubic, October 17-18, 2026

Loss:
About 2.94 trillion QU, about $1.3M, from 1,404 wallets (as reported by 0xCERT, from Qubic's statement). Cointelegraph reports about $1.4M. Qubic says 87.1% of the stolen QU stayed on the halted network, and MEXC froze the account that received the rest.
Chain:
Qubic
Root cause:
The Qubic wallet made seeds with weak randomness, so an attacker could work out the seeds and the private keys. Qubic says the fault was in seed generation, not in the Qubic protocol. Seeds made in iPhone and iPad browsers, in Safari on a Mac, or in the iOS app before July 2025 were affected. Wallet version 4.26.4 fixes new seeds.
Bug class:
Off-chain: wallet key generation
Code bug?
Yes, in the wallet app. It was not a smart contract bug.
How a pre-audit check relates:
Not a contract bug. A code audit of contracts, ours included, does not cover wallet apps or key generation.

Check your code

Check your own code for these classes

Most entries above are bug classes you can check before you ship. Guardix checks Solidity repos for classes like these in a pre-audit: one repo, one commit, $200 flat, results in 2 to 10 hours, depending on code size. See how much a smart contract audit costs.

How our checks score on known bugs: 104 of 117 on EVMBench.

Pre-attack replay: We ran Guardix on Euler Finance's code from before the $197M hack.

Pre-attack replay: We ran Guardix on BiFi Lending's code from before the $165K drain.

Guardix did not run on any codebase listed here.

Methodology

Methodology, sources and update log

Method. We include a hack when a public source gives its date, loss and cause. We take the loss from the source and link it. If sources differ, we give the range. We don't add a hack on a single social post.

What we leave out. The rankings count DeFi protocols, bridges and chains. Exchange, custody and hardware wallet thefts are named but not ranked. We also leave out events with no attacker, such as the Aave wstETH liquidations of March 10, 2026, which rekt.news lists at $27.78M (rekt.news). We add a hack only when a public source names its cause.

Sources used on this page:

Update log

  • 2026-10-21: added "Biggest DeFi hacks of 2026" and "Biggest DeFi hacks of all time". Added UNCX Vesting V2, BiFi Lending, AlpsCon AI Trade Hub and Qubic, and a new section on logic errors in accounting and rewards. Added the year to section headings. Updated the FAQ answer on the biggest DeFi hack of 2026 and linked the Euler Finance pre-hack replay.
  • 2026-10-15: first version.

FAQ

FAQ about DeFi hacks in 2026

What was the biggest DeFi hack of 2026?
By reported loss, Liquid Network, at $320M on September 6. About 3,400 of the roughly 4,000 BTC came back a day later (rekt.news). KelpDAO is second, at about $290M on April 18. Neither was a smart contract bug. Liquid's cause was a bug in node software, and KelpDAO's was a single verifier fed false data through compromised RPC nodes. See Biggest DeFi hacks of 2026.
What was the biggest crypto hack of 2026?
The Bitget exchange theft of $387.5M on September 24 (rekt.news). It was an exchange breach, not a DeFi hack, so it is not in our DeFi rankings.
What is the biggest DeFi hack of all time?
Ronin Network, at $624M on March 23, 2022, per the rekt.news leaderboard. The attacker controlled 5 of the 9 validator keys that approved bridge withdrawals (rekt.news). See Biggest DeFi hacks of all time.
How do most DeFi hacks happen in 2026?
By value, mostly through keys, signers and infrastructure. Halborn says off-chain causes drove 96% of H1 2026 losses. Contract bugs still cause losses, as the code-level entries above show.
What is an oracle manipulation attack?
A contract reads a price from an oracle. The attacker moves that price, often with a thin pool or a flash loan, then borrows or withdraws against the false value. Makina and Nostra above are examples. See oracles and price inputs in the checklist.
Can an audit prevent DeFi hacks?
An audit can reduce code risk. It does not cover keys, signers or infrastructure, and no audit guarantees a contract is safe. See Drift and KelpDAO above.
How often is this page updated?
Weekly. New hacks are added as entries, and the update log shows what changed.