Understanding Bybit Hack
A overview of the Bybit hack that happened in March 2025.
Originally published on March 30, 2025 on my previous blog.
Introduction
Last month, we witnessed one of the biggest Crypto exchange till date, Bybit, where the hackers exploited the wallet's UI and stole $1.5 million worth of crypto. Bybit, one of the largest cryptocurrency exchanges, recently fell victim to a sophisticated cyberattack resulting in the theft of approximately 400,000 ETH (worth $1.5 billion). This breach, attributed to the infamous Lazarus Group, underscores the evolving threats in the crypto space and the critical need for robust security measures. In this blog, we analyze how the hack occurred, its implications, and what security engineers can learn from it.
How the Bybit Hack Happened
1. How Bybit and Safe Work Together
Bybit relied on Safe{Wallet}, a third-party multi-signature wallet service, to manage its cold and hot wallet infrastructure. Safe provides smart contract-based wallet security, ensuring transactions require multiple approvals before execution. Bybit used this system to sign transactions securely, but this reliance also introduced a vulnerability that was exploited in the attack.
2. Involvement of Cold Wallets
Unlike many past exchange hacks that targeted hot wallets, this attack extended to Bybit’s cold wallet infrastructure. Since cold wallets store large amounts of funds offline, they are considered more secure. However, the breach occurred because Bybit’s security team unknowingly signed malicious transactions, effectively moving assets from cold storage into hacker-controlled wallets.
3. Exploiting a Third-Party Wallet Service
The attack originated from a compromise in Bybit’s multi-signature wallet system, which relied on Safe. The attackers managed to infiltrate Safe’s infrastructure by hacking into a Safe developer’s computer.
4. Malicious UI Injection and Improper Message Verification
Once inside, the hackers injected malicious JavaScript into the Safe frontend used by Bybit’s security team. This attack vector enabled them to manipulate the transaction approval process.
A critical mistake that led to the breach was the failure to properly check the messages being signed. The attackers disguised their transactions to appear as legitimate fund transfers. Bybit’s team, relying on Safe’s frontend, signed these transactions without detecting the fraudulent intent, leading to the unauthorized movement of funds.
5. Blockchain Laundering Techniques
After successfully transferring the stolen ETH, the hackers employed sophisticated obfuscation techniques:
- Bridging assets across multiple blockchains to break traceability
- Mixing services to conceal ownership
- Thousands of microtransactions to fragment stolen assets
Resources for Further Reading
I will suggest you to read the following articles:
To understand the technical details of the hack: Technical Analysis of the hack
To check how the assets were laundered: Crystal Intelligence
And here are some from the Bybit team:
Attribution: Who Was Behind It?
According to the FBI and Chainalysis, the attack was orchestrated by North Korea’s Lazarus Group. The group is notorious for targeting crypto exchanges to fund illicit activities, including weapons development. They quickly converted portions of the stolen ETH into Bitcoin and privacy-focused cryptocurrencies to evade tracking.
Bybit’s Response
Despite the massive loss, Bybit swiftly took the following actions:
- Emergency Reserve Funding: Bybit replenished its reserves within 72 hours, securing 447,000 ETH from firms like Galaxy Digital, FalconX, and Wintermute.
- 1:1 Asset Backing Assurance: Bybit confirmed that user funds remained unaffected, as all assets were backed 1:1. This ensured that no users experienced financial loss despite the scale of the breach.
- Bounty Offer: A $140 million bounty was announced for information leading to the tracking and freezing of stolen assets.
- Security Upgrades: Strengthened multi-signature controls, revised third-party security policies, and implemented stricter internal transaction approval mechanisms.
Lessons for Security Engineers
This hack highlights crucial security lessons for crypto exchanges and security engineers:
1. Limit Third-Party Dependencies
- Conduct deep security audits before integrating external wallet services.
- Ensure strict endpoint monitoring for supply-chain risks.
2. Enhance Transaction Approval Processes
- Implement multi-factor authentication (MFA) for all critical transactions.
- Use hardware security modules (HSMs) instead of relying solely on software-based approvals.
3. Strengthen Insider Threat Detection
- Continuously monitor developer activities and access logs.
- Deploy behavioral analytics to flag anomalies in transaction signing processes.
4. Proactive Blockchain Forensics
- Maintain on-chain monitoring tools to detect unusual fund movements in real-time.
- Establish partnerships with firms like Chainalysis and TRM Labs to track and recover stolen assets.
Conclusion
The Bybit hack serves as a wake-up call for crypto exchanges and security engineers alike. As attackers employ more sophisticated techniques, the industry must continuously evolve security frameworks to protect user funds. By applying the lessons from this breach, organizations can better safeguard their assets against future threats.
Comments
Join the discussionNo comments yet. Be the first to comment.