🕑 Estimated reading time: 4 minutes | Last updated: May 29, 2026
On 22 May 2025, an attacker exploited a flaw in an overflow check in a maths library used by Cetus, the leading decentralised exchange on the Sui blockchain, to drain about $223 million from liquidity pools using minimal deposits. Sui validators quickly froze roughly $162 million of the stolen assets, and the community later voted to return them to victims. The case shows the value of audits that cover dependencies, invariant testing, pause mechanisms and rapid response, and it raised hard questions about how decentralised a chain is if funds can be frozen.

Decentralised finance promises markets that run on code, without banks or brokers. When the code fails, the consequences can be immediate and enormous. The Cetus exploit of May 2025 was one of the year’s largest DeFi hacks, but its aftermath was even more interesting than the attack, because it forced a blockchain community to decide whether, and how, to intervene.
Table of Contents
What Happened
Cetus was the largest decentralised exchange on the Sui blockchain, using a concentrated-liquidity design similar to Uniswap v3. On 22 May 2025, an attacker exploited a flaw in an overflow check within a shared mathematics library used to calculate liquidity. By crafting positions with extreme parameters, the attacker tricked the protocol into crediting enormous liquidity for a tiny deposit, then withdrew real assets from pools. Around $223 million was drained within a short time.
Some of the funds were quickly bridged to Ethereum. But a large portion remained on Sui, and validators, the operators who run the network, coordinated to stop transactions from the attacker’s addresses, effectively freezing about $162 million. After a community governance vote, those funds were returned to a trust for affected users, and Cetus relaunched with compensation plans.
Technical Lessons
1. Audit your dependencies, not just your code
The vulnerable check sat in a library, not Cetus’s core logic. Libraries handling maths, signatures or token standards deserve the same scrutiny as the main contracts, because one bug can affect every protocol that relies on them.
2. Test invariants with extreme values
Fuzzing and invariant testing, which feed huge numbers of random and boundary inputs to check that core rules always hold, are particularly good at catching overflow and precision errors that human reviewers miss.
3. Build circuit breakers
Pause functions, withdrawal limits and anomaly-triggered halts give teams time to respond. They must be protected by multi-signature controls and used transparently to avoid abuse.
4. Monitor in real time
On-chain monitoring that alerts on unusual liquidity changes or large outflows can turn a total loss into a partial one.
5. Prepare an incident plan
Know in advance who can pause contracts, how to contact validators, exchanges, bridges and stablecoin issuers, and how to communicate with users.
The Freezing Debate
The validators’ intervention saved users a great deal of money, and many praised it. Critics, however, argued that if a small group of validators can freeze funds, the network is less decentralised and censorship-resistant than it claims. Similar debates followed Ethereum’s 2016 DAO hard fork and other chain-level interventions.
There is no simple answer. Users increasingly expect protection from theft, and regulators expect stolen funds to be recoverable where possible. But the power to freeze funds is also the power to block lawful transactions. Transparent governance, clear rules on when intervention is allowed and community accountability are essential if networks choose to keep such powers.
What It Means for Users
- Audits reduce but do not remove risk; even well-known protocols can be exploited.
- Diversify across protocols and do not put more into DeFi than you can afford to lose.
- Understand the governance of the chain and protocol you use, including whether funds can be paused or frozen.
- Follow official channels during incidents and beware of fake “refund” sites that appear after hacks.
Signs of a Maturing Industry
Chainalysis’s data suggests DeFi losses in 2025 were lower than in the peak years of 2021 and 2022, despite more value locked. Better tooling, bug bounties, monitoring and faster coordinated responses are part of the reason. Incidents like Cetus show both how far the industry has come and how much remains to be done.
Test edge cases before contracts go live
The Cetus exploit was a reminder that one unchecked edge case in shared code can put hundreds of millions of dollars at risk. Its aftermath showed the value of rapid coordination, and the trade-offs that come with it. For DeFi builders, the lesson is to invest as much in testing, monitoring and response planning as in shipping new features.
Frequently Asked Questions
How much was stolen from Cetus?
About $223 million, of which roughly $162 million was frozen on the Sui network and later returned for victims.
Was the Sui blockchain itself hacked?
No. The flaw was in code used by the Cetus protocol, not in Sui’s core consensus.
Is freezing stolen funds a good idea?
It can protect victims but raises concerns about centralisation; communities need clear, transparent rules.