# Cetus Protocol Exploit Analysis

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FxnrBu5emR2GHFM9BtrYD%2FStablecoin.png?alt=media&#x26;token=5811d854-826e-4145-8a9f-2a012a104554" alt=""><figcaption></figcaption></figure>

## Summary

On May 22, 2025, Cetus Protocol, the largest decentralized exchange (DEX) on the Sui Network, was exploited, resulting in approximately $223 million in losses due to a mathematical flaw. By using a single SCA (Single Collateral Asset) token and carefully selected tick ranges, the attacker drained liquidity pools. While $162 million was quickly frozen by Sui validators, over $60 million was bridged to Ethereum and subsequently converted into approximately 21,000 ETH.

[Cetus Protocol](https://x.com/CetusProtocol?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) is a leading DEX on the Sui Network, known for providing high-performance, cost-effective token trading, leveraging advanced automated market-making (AMM) mechanics tailored for Sui’s scalable infrastructure.

However, on Thursday morning, the protocol was nearly left empty of its entire TVL across all pools, as an exploiter drained the protocol and dumped SUI tokens for USDC. [The Sui ecosystem and Cetus team swiftly confirmed and publicly acknowledged the exploit](https://x.com/CetusProtocol/status/1925515668394582323). Sui validators implemented urgent mitigation measures, successfully [freezing around $162 million on Sui](https://x.com/SuiNetwork/status/1925572334054002774), while approximately $60 million was bridged to Ethereum in batches of roughly $1 million each, mostly in USDC.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FE2nubVCUO2PxYYRpJYbm%2FScreenshot%202025-05-27%20121458.png?alt=media&#x26;token=4f01892b-83d5-48e9-bc1a-5d30c9338de7" alt=""><figcaption><p><a href="https://x.com/SuiNetwork/status/1925572334054002774">Sui validators identified the exploiter’s address and actively ignored its transactions.</a></p></figcaption></figure>

Following the attack, Cetus, along with [Inca Digital](https://x.com/inca_digital?lang=en), announced a $6 million bounty proposal to the exploiter, offering no legal action if the funds were returned. As of now, the exploiter has not responded, and Cetus is working closely with SUI and various law enforcement agencies to retrieve funds.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FYVR5gskQrxgKME2dVZeK%2FScreenshot%202025-05-27%20121817.png?alt=media&#x26;token=1ad25fb7-afa5-4eb2-973c-ca6469834cf9" alt=""><figcaption><p>Transaction Decoder revealing the on-chain communication initiated by Cetus Protocol with the exploiter.                                                                Tx. hash: <code>0xae4c0e656fcd893c3213a6dc28513153fc02df2ae14b7241e9029503fe90ccd0</code></p></figcaption></figure>

### Relevant Addresses

Cetus SUI Exploiter: `0xe28b50cef1d633ea43d3296a3f6b67ff0312a5f1a99f0af753c85b8b5de8ff06` &#x20;

Cetus ETH Exploiter 1: `0x89012a55cd6b88e407c9d4ae9b3425f55924919b`

Cetus ETH Exploiter 2: `0x0251536bfcf144b88e1afa8fe60184ffdb4caf16` &#x20;

## Decoding the Exploit

The Cetus Protocol exploit occurred due to a vulnerability within its CLMM (Concentrated Liquidity Market Maker) contract, stemming from an unchecked overflow in the open-source integer\_mate package (a math library commonly used in DeFi protocols to perform precision arithmetic operations). The attacker first executed a flash swap, temporarily suppressing pool prices. They then strategically opened a liquidity position spanning 200 ticks (price intervals within the liquidity range). By using just a single SCA (Single Collateral Asset) token, they manipulated the concentrated liquidity system to devastating effect.

Specifically, the flawed `get_liquidity_from_a` function allowed the attacker to inject enormous liquidity using only a minimal amount of tokens. Although an overflow check existed, it only verified the numerator. When the tick range is narrow, the denominator approaches zero, effectively allowing near-infinite amplification (dividing by nearly zero). As a result, one SCA token was able to generate an astronomical 10,365,647,984,364,446,732,462,244,378,333,008 units of liquidity.

The attacker took a flash loan of approximately 56,700 SUI, exploited the overflow to mint massive liquidity, withdrew the inflated liquidity, repaid the flash loan, and drained all illicitly generated profits — ultimately extracting $223 million.

In the next section, we will decode the on-chain activity using Blockscope forensic tools.

## On-Chain Activity

After draining the Cetus Protocol, the Cetus SUI Exploiter started to convert the stolen SUI into USDC to access deeper liquidity and enable cross-chain transfers. Approximately $60 million in USDC was bridged from Sui to Ethereum using Wormhole and Circle, where it was then systematically swapped into ETH through various DeFi protocols. Our Tracer tool has visualized this movement on a graph, mapping the systematic flow of bridged funds on Ethereum and their conversion into ETH.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FByCJj0NFUjCceiMTpooV%2FScreenshot%202025-05-27%20011438.png?alt=media&#x26;token=7f3a08cc-1818-4cf4-bad0-778e6a4a6663" alt=""><figcaption><p>Blockscope Tracer shows the movement of bridged funds on Ethereum</p></figcaption></figure>

Backtracing revealed that Circle’s CCTP was likely used to transfer USDC to Ethereum. Contract `0x8656d3703ecbc5f36a9668a4859a7f1138bab0b3` possibly acted as a shim, emitting messages and providing gas to Cetus Exploiter 1. While its exact identity remains unknown, it is likely tied to a third-party DeFi relay. Tracer analysis shows that its creator and funder were funded by Coinbase's hot wallets.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2Foj2te2mSGNQcmIaydUn6%2FScreenshot%202025-05-27%20011942.png?alt=media&#x26;token=2e19df6c-da26-40e9-9bbd-fa12583e5bae" alt=""><figcaption><p>Blockscope Tracer graphs Relayer/Shim contract and it's associates.</p></figcaption></figure>

## Breakdown and Timeline

### **May 22, 2025 at 10:30 UTC**

The exploit began with the CLMM contract being exploited, draining liquidity reserves. Approximately $223 million worth of tokens were compromised.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FGK2rCmy9HTgAFth2FYcs%2FScreenshot%202025-05-27%20115419.png?alt=media&#x26;token=f3f3018d-e642-40ce-8192-890c536a7f0a" alt=""><figcaption><p>SuiVision shows Cetus protocol multiple AMMs were drained by Cetus SUI Exploiter.</p></figcaption></figure>

### **May 22, 2025 at 10:47 UTC**

Over $60 million was systematically bridged to Ethereum in multiple batches of a million each via Circle and Wormhole.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FMD0YqDpzwIgiE6FE8NeD%2FScreenshot%202025-05-27%20115543.png?alt=media&#x26;token=d497cfc2-ebf6-4a34-97f1-d4dc6018d53d" alt=""><figcaption><p>SuiVision shows bridging of funds to Ethereum.</p></figcaption></figure>

### May 22, 2025 at 10:48 UTC

Funds were received by Cetus ETH Exploiter 1, who converted the bridged USDC into approximately 21,000 ETH through various DeFi protocols like Cowswap and Paraswap.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FwUScmVr69IHQu05SYOwl%2FScreenshot%202025-05-27%20115829.png?alt=media&#x26;token=29384dcc-7a96-406a-b049-d062afedfba1" alt=""><figcaption><p>Wallet Profiler shows token transfers of the Cetus ETH Exploiter 1.</p></figcaption></figure>

### May 22, 2025 at 12:31 UTC

ETH Exploiter 1 transferred a significant portion, approximately 20,000 ETH, to Cetus ETH Exploiter 2, which is currently holding the assets, valued at roughly $60–61 million.

Tx. hash: `0xcf5500862c1bf696e5a7acc29559e2a549497846280b8d8a5349a74941bc921a`

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2F5FPVcQSgYFcsexaWaBT6%2FScreenshot%202025-05-27%20120042.png?alt=media&#x26;token=23e48cc6-e6ce-4d9d-9bbe-630550aa8c95" alt=""><figcaption><p>Entity Interaction tool shows a single transfer of 20,000 ETH from Cetus ETH Exploiter 1 to Cetus ETH Exploiter 2.</p></figcaption></figure>

### May 22, 2025 12:50 UTC

Sui validators started voting on refusing to serve transactions signed by attacker’s addresses and effectively “froze” those addresses. Swiftly, the validators froze approximately $162 million to prevent further losses.&#x20;

Frozen Address 1: `0xcd8962dad278d8b50fa0f9eb0186bfa4cbdecc6d59377214c88d0286a0ac9562`

Frozen Address 2: `0xe28b50cef1d633ea43d3296a3f6b67ff0312a5f1a99f0af753c85b8b5de8ff06`

## Monitoring via Watchtower

Blockscope has activated its watchtower and is doing real-time monitoring of the two Ethereum exploiter addresses to track any subsequent movements or transactions made by Exploiter.

Link: <https://www.blockscope.co/community/watchtowers/683537673593a981b24f78de>

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FfpJhDFFh41NmY1qOm4uY%2FScreenshot%202025-05-27%20120302.png?alt=media&#x26;token=792736a6-e019-4282-9dc3-faf4a030f872" alt=""><figcaption></figcaption></figure>

## Shim/Relayer Contract Tracing

An intermediary shim/relayer contract `0x8656d3703ecbc5f36a9668a4859a7f1138bab0b3` funded the exploiter address with some gas and transmitted a message to mint USDC. Although benign in historical operations, including minor ETH gas funding and USDC minting, no direct malicious or definitive association with the exploiter or any specific DeFi protocol could be verified. This contract is likely a third-party bridging or routing service, potentially associated with Mayan Finance or another relay network, as nothing has been discovered that directly links it to Circle, but it appears to function as a message relayer for Circle CCTP and gas drop.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FM4kj8njSqNaxa3WYJc2N%2FScreenshot%202025-05-24%20124256.png?alt=media&#x26;token=9868784a-0e7e-48a3-9286-29dd9763bcd9" alt=""><figcaption><p>Cluster Analysis of the Ehereum addresses of Cetus Protocol Exploit </p></figcaption></figure>

## Conclusion

As of now, there have been no movements from the ETH exploiter addresses. Cetus Protocol is actively collaborating with law enforcement agencies and the Sui Network to pursue recovery efforts. The team initially offered a $6 million whitehat bounty to the exploiter for the safe return of funds, but after receiving no communication or response, [the bounty has been converted into a $5 million open reward for anyone](https://x.com/CetusProtocol/status/1925914205745459433) who can provide valuable information or assist in fund recovery.

This comprehensive investigation provides critical insights into the mechanics of the May 22 Cetus Protocol exploit and the subsequent cross-chain fund movements. Continued monitoring, forensic tracking, and close collaboration with security partners are essential to trace, contain, and potentially recover the remaining stolen assets.

The impact of this exploit has rippled beyond Cetus itself, affecting other decentralized exchanges (DEXs) on the Sui Network like [Bluefin](https://x.com/bluefinapp/status/1925621980532781117), [Turboas Finance](https://x.com/Turbos_finance/status/1925626231900291477), and[ FLowX Finance](https://x.com/FlowX_finance/status/1925685575568224431), some of which were forced to halt operations or initiate emergency audits. Furthermore, many ecosystem tokens saw their values plummet by over 75% following the attack, underscoring the widespread market disruption it caused.

<figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2Fncn9g2vna4QAIkh4iThV%2FScreenshot%202025-05-27%20123759.png?alt=media&#x26;token=7a34b904-ba73-4414-9547-f6146b701e68" alt=""><figcaption><p>FlowX Finance is temporarily halting services to ensure user fund safety.</p></figcaption></figure>

Notably, [Cetus Protocol had undergone multiple rounds of audits](https://x.com/CetusProtocol/status/1915620102873243716), including one as recently as April by [Zellic](https://x.com/zellic_io), yet the vulnerability still slipped through — a stark reminder that even well-audited protocols are not immune to sophisticated attacks. Moving forward, the Cetus team remains committed to strengthening its security posture and working alongside the broader community to restore trust and resilience in the ecosystem.

**Investigation by**: [Tushar Tiwari](https://in.linkedin.com/in/tushar-tiwari-1380271b7), Analyst @ Blockscope

For more information, please reach out to us at **<hello@blockscope.tech>**

<div data-full-width="false"><figure><img src="https://3202772446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkYvqF0gRZOFn5wvaOHMl%2Fuploads%2FEk9EqlyJRVT5ES0DHX0L%2FGreen%20Black.png?alt=media&#x26;token=c0853e1c-cf52-41ce-a062-a527eeaac8c5" alt="" width="563"><figcaption></figcaption></figure></div>

Disclaimer: Best Effort Investigation

This investigation and its findings represent our best effort based on the information available at the time. However, please be aware of the following limitations:

* The data used in this investigation may contain inaccuracies, omissions, or errors.
* Information sources may be incomplete or subject to change.&#x20;
* New evidence may emerge that could alter the conclusions.&#x20;
* Analysis and interpretations are based on current understanding and may evolve.

We have made every reasonable attempt to ensure accuracy, but we cannot guarantee that all information is entirely correct or complete. This report should be considered a snapshot of our current knowledge and understanding, subject to revision as new information becomes available.