# Bybit Breach Uncover : Tracing a $1.5 Billion Crypto Heist

<figure><img src="/files/HDvSW7jc953H73o0v7uh" alt=""><figcaption></figcaption></figure>

## Summary

On February 21, 2025, [Bybit](https://x.com/Bybit_Official), one of the leading cryptocurrency exchanges, suffered a massive security breach resulting in the loss of nearly $1.5 billion in Ethereum and various ERC20 tokens—including stETH, mETH, and cmETH—marking the largest digital heist in the crypto history. This unprecedented incident sent shockwaves throughout the digital asset landscape, raising concerns about the vulnerability of even the most established platforms.

Early investigations revealed that the exploit was initiated through sophisticated social engineering tactics. Cybercriminals launched targeted phishing attacks against cold wallet signers, deceiving them into approving malicious transactions that replaced the secure multi-signature wallet contract with a compromised version. This critical lapse enabled the unauthorized transfer of 401,346.7688 ETH, 8,000 mETH, 90,375.5479 stETH, and 15,000 cmETH tokens during what appeared to be a routine transaction, with these assets collectively valued at approximately $1.5 billion.

<figure><img src="/files/pPqqYVmH7c1rmxIPDhJa" alt=""><figcaption><p>Bybit's lost Assets</p></figcaption></figure>

Further analysis indicated potential state-sponsored involvement, with clear links to tactics commonly associated with DPRK-affiliated cybercriminals. Post attack investigations pointed to a targeted social engineering attack rather than a direct breach of Bybit’s systems. The exploit originated from a compromised developer machine at [Safe {Wallet}](https://x.com/safe), which was used to manipulate the wallet’s UI and deceive signers into approving unauthorized transactions.

Evidence shows that the addresses used in the Bybit hack are also common with those from previous incidents targeting other major exchanges such as [Phemex](https://x.com/Phemex_official), [Poloniex](https://x.com/Poloniex), and [BingX](https://x.com/BingXOfficial). These recurring connections underscore a coordinated pattern of cyber exploitation and sophisticated laundering methods that point toward a broader, state-linked operation.

In the aftermath of the breach, [CEO Ben Zhou](https://x.com/benbybit) went live to address the incident, outlining the immediate measures taken and reassuring the community of a robust recovery plan. The entire Bybit team demonstrated exceptional resilience and swift coordination in mitigating the damage, while the broader crypto industry united in support. Thanks to these collective efforts, [Bybit is now on track to achieve a 1:1 asset ratio,](https://x.com/benbybit/status/1893865556840775758) reflecting both the strength of its internal response and the solidarity of the global digital asset community.

### Key Addresses

**Bybit Cold Wallet**: 0x1db92e2eebc8e0c075a02bea49a2935bcd2dfcf4

**Bybit Main Exploiter**: 0x47666fab8bd0ac7003bce3f5c3585383f09486e2

## Decoding the Exploit

Preliminary forensic analysis indicates that the breach exploited a critical vulnerability in the transaction signing workflow of Bybit’s Ethereum multisig cold wallet. [According to Bybit's official communications](https://x.com/Bybit_Official/status/1892965292931702929), the compromise occurred during what was expected to be a routine transfer from cold to warm storage. [The signing interface was "musked"](https://x.com/benbybit/status/1892963530422505586)—displaying seemingly legitimate transaction details while the underlying signing payload was surreptitiously altered. This manipulation enabled an unauthorized reconfiguration of the wallet’s smart contract logic, allowing the attacker to redirect funds to an external, unidentified address.

<figure><img src="/files/ZGy8ciR9yrgdr5UFrDom" alt=""><figcaption><p>Flow chart showing the initiation of exploit</p></figcaption></figure>

Despite these initial insights, the definitive technical root cause remains undetermined. Bybit’s security team, in collaboration with leading blockchain forensic experts, is investigating whether the vulnerability arose from compromised signing devices, a server-side breach, or a combination of both. Notably, all signers observed an interface with a URL that appeared to originate from [Safe {Wallet}](https://x.com/safe), suggesting that the attacker exploited a subtle decoupling between the displayed UI and the actual transaction data—a critical flaw that compromises the integrity of multisig protocols.

In a separate update,[ Safe{Wallet} confirmed via social media that its codebase remains unmodified](https://x.com/safe/status/1893105625439093094), with no evidence of malicious dependencies or unauthorized infrastructure access, and that no additional Safe addresses have been affected. Similar exploit techniques have been observed in recent breaches at other major exchanges such as [Phemex](https://x.com/Phemex_official?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor),[ Poloniex](https://x.com/Poloniex), and [BingX](https://x.com/BingXOfficial), indicating a potential pattern linked to state-sponsored threat actors like the[ Lazarus Group](https://en.wikipedia.org/wiki/Lazarus_Group), which are known for employing sophisticated front-end manipulation methods.

<figure><img src="/files/unRUDlG1lh6GGaD8TYvZ" alt="" width="371"><figcaption><p><a href="https://x.com/safe/status/1893105625439093094">Tweet from Safe{Wallet} on 21 Feb</a></p></figcaption></figure>

In response to the breach, CEO Ben Zhou and the Bybit team have maintained transparent communication and executed rapid containment measures. While confirming that the compromised cold wallet was the sole affected asset, [Bybit has continued normal withdrawal operations—processing over 350,000 withdrawal requests—to ensure customer fund security.](https://x.com/benbybit/status/1893102137711960486)&#x20;

Forensic analysis suggests that the stolen ETH is being laundered into Bitcoin via platforms such as [Chainflip](https://x.com/Chainflip), [eXch](https://exch.cx/), and [THORChain](https://x.com/THORChain?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor); [Chainflip has pledged to assist](https://x.com/Chainflip/status/1893222347252875386), whereas eXch and THORChain have only echoed Bybit’s request for support. This laundering technique mirrors known state-sponsored strategies, wherein illicit funds are converted to ETH, bridged to BTC through mixers and cross-chain solutions like Tornado Cash, eXch, and routed through Asian exchanges.&#x20;

Further forensic analysis by investigation firms and on-chain researchers identified the actual cause of the breach: a malicious JavaScript injection into a resource served from Safe {Wallet}'s AWS S3 bucket. This exploit manipulated the UI, deceiving signers into authorizing altered transactions. [Safe later acknowledged the issue](https://x.com/safe/status/1894768522720350673), confirming the compromise and releasing an update on X detailing their findings and implemented security measures. However, their report leaves several critical questions unanswered, particularly regarding how the attacker gained access to the S3 bucket and whether similar vulnerabilities persist.

<figure><img src="/files/1ysvCjc5UtID1pwSJyTg" alt="" width="377"><figcaption><p><a href="https://x.com/safe/status/1894768522720350673">Safe{Wallet}'s tweet on 26 Feb</a></p></figcaption></figure>

[Bybit has launched a $150M bounty to aid fund recovery](https://x.com/Bybit_Official/status/1893322897243943330), with $2.17M USDT already paid to 11 contributors, including [Mantle](https://x.com/Mantle_Official), [Paraswap](https://x.com/paraswap), and [ZachXBT](https://x.com/zachxbt). As of March 4, nearly 500K ETH has been laundered to Bitcoin, where 77% of the stolen $1.4B remains traceable, 20% has gone dark, and 3% is frozen. The hacker converted 83% (\~$1B) to BTC via THORChain (72% traceable), while 16% (\~$180M) disappeared through eXch and 8% (\~$100M) moved through OKX Web3 Proxy, with $65M still untraceable.&#x20;

## Onchain Activity

Using **Blockscope's Tracer tool**, our analysis has uncovered a complex network of intermediary wallets designed to obscure the movement of the stolen funds. Initially, the exploiter partitioned the compromised assets by splitting the stolen ETH into multiple distinct wallets while consolidating all stolen ERC20 tokens—namely stETH, cmETH, and mETH—into just two primary addresses.

<figure><img src="/files/7fVE6vLoqJfE1ojUdu8f" alt=""><figcaption><p>Bybit Cold Wallet getting drained by Exploiter</p></figcaption></figure>

Subsequent on-chain tracking reveals that approximately 401,000 ETH was distributed among 40 intermediary wallets.&#x20;

<figure><img src="/files/Q7KZ8hKbhrR6ixMJxMsl" alt=""><figcaption><p>Cluster of Intermediary Wallets holding 10k ETH each</p></figcaption></figure>

The attacker then leveraged multiple DeFi protocols, including Paraswap, Uniswap, DODO, and Lido, to swap all the ERC20 tokens into ETH.&#x20;

<figure><img src="/files/DcmzSu82I9ILMnwDuHTS" alt=""><figcaption><p>Stolen ERC20 tokens getting converted to ETH</p></figcaption></figure>

Currently, the exploiters are executing multi-layered laundering which not only complicates asset tracing but also highlights the sophisticated techniques employed to disguise the fund flow and impede recovery efforts. Cross-chain bridges like Chainflip and protocols like eXch and Thorchain are being used to convert the stolen ETH to BTC.

<figure><img src="/files/Mpa950R1ElYWfmBhCco9" alt=""><figcaption><p>Web of Intermediatry wallets to launder funds</p></figcaption></figure>

<figure><img src="/files/RYHH7zwUoo4Vxijjku4x" alt=""><figcaption><p>Chainflip and eXch are being leveraged to launder Ethereum funds by bridging them into Bitcoin.</p></figcaption></figure>

## Breakdown and Timeline

### February 21, 2025, 14:16 UTC

The exploit began with the attacker’s primary wallet, 0x0fa09c3a328792253f8dee7116848723b72a6d2e, which initiated a transaction by calling Bybit's cold wallet at 0x1db92e2eebc8e0c075a02bea49a2935bcd2dfcf4 and transferring 401,346.7688 ETH. This transaction confirms that the attacker had already breached the cold wallet’s security, gaining unauthorized access and executing a direct fund transfer.

Tx. hash:0xb61413c495fdad6114a7aa863a00b2e3c28945979a10885b12b30316ea9f072c

<figure><img src="/files/HlRA2WJ2YaCzTHqrozTW" alt=""><figcaption><p>ETh getting drained from the cold wallet to the exploiter wallet</p></figcaption></figure>

### February 21, 2025; 14:41 - 15:12 UTC

In a few minutes, the exploiter drains 10000, 50000, and 30375.5479 stETH in three separate transactions, transferring them to its intermediary wallet 0xa4b2fd68593b6f34e51cb9edb66e71c1b4ab449e. Meanwhile, at 15:10 UTC, the exploiter also transferred 8000 mETH to the same wallet.

<figure><img src="/files/pt2I91bB0rRfLsEbTnPl" alt=""><figcaption><p>Exploiter draining stETH</p></figcaption></figure>

### February 21, 2025; 15:23 UTC

The exploit escalated when the attacker drained 15,000 cmETH—valued at approximately $43 million—and transferred it to the intermediary wallet 0x1542368a03ad1f03d96d51b414f4738961cf4443.

<div data-full-width="true"><figure><img src="/files/7TSUsbe5xQhArS7zuhSC" alt=""><figcaption><p>15000 cmETH being transferred</p></figcaption></figure></div>

### February 21, 2025; 14: 56 - 15:54 UTC

Following the breach, the attacker distributed the stolen ETH across approximately 40 distinct wallets, with roughly 10,000 ETH allocated to each.

<figure><img src="/files/GjLqF77Br5LKwurTr9BQ" alt=""><figcaption><p>Exploiter transferring ETH from main wallet to side wallets</p></figcaption></figure>

### February 21, 2025; 14:29 UTC

The attacker then converted all stolen stETH, mETH, and cmETH into ETH using various DeFi protocols—including Uniswap, Paraswap, DODO, and Lido—ultimately acquiring approximately 98,048.7948 ETH. This amount was subsequently distributed among multiple wallets, each receiving roughly 10,000 ETH.

<figure><img src="/files/944dg18Mlj65fxX4Rf0M" alt=""><figcaption><p>Exploiter burning cmETH to eventually convert it into ETH</p></figcaption></figure>

<figure><img src="/files/o5U1uXm3GsGztsBWBx7Z" alt=""><figcaption><p>stETH and mETH getting converted into ETH</p></figcaption></figure>

### Obfuscation and Laundering

At present, our on-chain analysis and watchtower indicate that the exploiters are actively laundering funds through [eXch](https://exch.cx/) and [THORChain](https://x.com/THORChain?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor), following a laundering pattern consistent with tactics historically associated with North Korean threat actors.&#x20;

Intermediary wallets holding approximately 10,000 ETH are systematically distributing funds to multiple addresses, while wallets with balances under 100 ETH are funneled through eXch and converted into Bitcoin, effectively obfuscating the illicit asset trail.

<div><figure><img src="/files/qsvvjLFalin3iIS7gtcQ" alt=""><figcaption><p>Split Stage1</p></figcaption></figure> <figure><img src="/files/9v4XHqHXVTP9iaUP9T6b" alt=""><figcaption><p>Split Stage 2</p></figcaption></figure> <figure><img src="/files/7NPioYq23FDUsUJoC12O" alt=""><figcaption><p>Split Stage 3 and launder</p></figcaption></figure></div>

As of February 26, all the stolen ETH is being laundered using [THORChain](https://x.com/THORChain?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor), which has successfully [processed over $260 million in illicit ETH transactions](https://www.coinspeaker.com/thorchain-dex-volume-soars-amid-bybit-hack-rune-jumps-22/).

<figure><img src="/files/g881zo6Tje1u5802yXhY" alt=""><figcaption><p>Exploiters are laundering funds through various intermediary wallets</p></figcaption></figure>

<figure><img src="/files/AebEdFh7zG9M4z6RiTtA" alt=""><figcaption><p>Thorchain has till now laundered more than $260M worth of assets</p></figcaption></figure>

In this critical period of industry consolidation, [THORChain](https://x.com/THORChain?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) stands as a key enabler of illicit activity, profiting significantly as its fee volume surges due to the heavy laundering operations linked to North Korean exploiters. With the platform facilitating the movement of stolen assets, continuous monitoring and enhanced oversight remain imperative to mitigate further exploitation.

<figure><img src="/files/lGUvpCh373RIgTFv9xST" alt=""><figcaption><p>Thorchain fees volume are sky rocketing as it generate more than $2 M in last few days.</p></figcaption></figure>

Between the day of hack and now, [THORChain saw an unprecedented $5.5+ billion in trading volume,](https://x.com/arkham/status/1896968970206634487) generating millions in fees, with nearly all activity tied to Bybit’s laundered funds. Since the exploit, North Korean attackers have successfully bridged and laundered most of the stolen assets, nearly 500,000 ETH to Bitcoin using THORChain and eXch. Now entering the second phase of laundering, they are obfuscating BTC origins through mixers like [Wasabi](https://wasabiwallet.io/) and [TornadoCash](https://x.com/tornadocash?lang=en)—a tactic they have historically relied on to erase financial trails. Initial tranches of stolen BTC have already begun flowing into these services, marking a critical moment in the laundering process.

## Monitoring

Since the day of the exploit, the Blockscope team has been actively monitoring the evolving situation on Bybit. By deploying our watchtower on key wallet addresses, we have identified several hundred addresses directly linked to the exploiter. To date, nearly half of these wallets have begun moving their funds, while the remaining half continues to hold approximately 10,000 ETH. Our ongoing surveillance remains crucial in tracking and mitigating further illicit activity. Link to the Bybit Watchtower: <https://www.blockscope.co/community/watchtowers/67b93f6aeaef17d752e70587>

<figure><img src="/files/jDovaxbNEGNziPHCqO3q" alt=""><figcaption><p>Bybit Community Watchtower</p></figcaption></figure>

### Tracing the North Korean Exploit Network

Our monitoring efforts have uncovered compelling evidence linking the current breach to broader state-sponsored activities. Notably, on-chain sleuth [ZackXBT](https://x.com/zachxbt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) highlighted similar exploit patterns and common addresses involved in major exchange exploits like [Phemex](https://x.com/Phemex_official), [BingX](https://x.com/BingXOfficial), and [Poloniex](https://x.com/Poloniex).&#x20;

Using our advanced Blockscope tools, we verified these claims and confirmed the presence of common intermediary wallets across these platforms. This convergence of wallet activity suggests a coordinated network of exploits that aligns with tactics historically attributed to North Korean threat actors, further underscoring the sophisticated nature of these operations.

**Common addresses found between the exploits:**

**BingX & Bybit-** 0xd555789b146256253cd4540da28dcff6e44f6e50

**Phemex & Bybit-** 0x33d057af74779925c4b2e720a820387cb89f8f65

**Poloniex & Bybit-** 0x15ec300a4895a86322f1a27dd9ba0b9f8297e65d

<figure><img src="/files/Q0NkxGvc70QPENB1feND" alt=""><figcaption><p>Tracing Bybit, Phemex, and BingX exploits revealed common addresses, indicating that the same actors are behind these exploi</p></figcaption></figure>

<figure><img src="/files/pubgR4meQHdfGumnm9Z9" alt=""><figcaption><p>TA common address was identified linking Bybit and Poloniex, suggesting the same actors are involved.</p></figcaption></figure>

## Conclusion

The Bybit breach stands as the largest crypto heist to date, with clear evidence linking the exploit to North Korean state-sponsored operations. The sophisticated attack exploited vulnerabilities in Bybit’s multi-sig cold wallet signing process, triggering an intricate laundering scheme that dispersed stolen funds across numerous intermediary wallets. The [FBI has further reinforced these findings in a public announcement](https://x.com/Cointelegraph/status/1894912646845210833), officially attributing the exploit to North Korean actors.

<figure><img src="/files/OxuWQFSM4FSfjgPb0Vgs" alt="" width="375"><figcaption><p>FBI Public Service Announcement</p></figcaption></figure>

[While Bybit has since stabilized its operations](https://x.com/Bybit_Official/status/1893928666117382325), this incident serves as a stark reminder of the inherent vulnerabilities in the digital asset ecosystem and the evolving threats that challenge even the most robust security measures. Stay updated on [**Lazarusbounty.com**](http://Lazarusbounty.com)—Bybit’s dedicated bounty site—where new findings on hacker addresses, cross-chain asset tracking, and ranked wallet balances are posted.

[Blockscope](https://x.com/BlockscopeCo) has been at the forefront of this investigation from the very first alarm. By deploying the tracer tool and establishing a dedicated watchtower on key wallet addresses, our team has identified hundreds of addresses directly linked to the exploiter. The transparency of blockchain technology—where every transaction is publicly recorded—enables cybersecurity professionals and authorities to trace illicit activities in real-time.

The swift response from Bybit and robust collaboration across the crypto community underscores our collective commitment to fortifying defenses against sophisticated cyber threats.

**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>**

<figure><img src="/files/hWIOH967M0whynPTP68A" alt=""><figcaption></figcaption></figure>

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 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://research.blockscope.co/bybit-breach/bybit-breach-uncover-tracing-a-usd1.5-billion-crypto-heist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
