How much was lost in the Bitget hack?

The Bitget hack resulted in $100M in losses on April 20, 2025.

What attack technique was used in the Bitget exploit?

The Bitget exploit utilized Market-Making Bot Exploit. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

Bitget Hack

TOTAL LOST $100M

Critical #77 All-Time Apr 20, 2025 Market-Making Bot Exploit

Affected Chain 2025 Incident surface

Recovered - No recovery reported

All-Time Rank #77 By amount stolen

Protocol Type CEX Target category

Incident Overview

Bitget is the leading crypto exchange platform for crypto derivatives trading.

Incident Report

Protocol / Project Bitget

Date of Incident April 20, 2025

Attack Technique Market-Making Bot Exploit

Classification Infrastructure

Primary Source View Post-Mortem

Protocol Information

Protocol Type CEX

Official Website www.bitget.com

Protocol Twitter/X @bitget

Market Context at Time of Hack

Token Categories

Ethereum Ecosystem Solana Ecosystem BNB Chain Ecosystem Bitgert Ecosystem

Protocol Links

GitHub Discord

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of market-making bot exploit and Solidity and EVM internals

Capital Required Seed capital to cover gas and initial position setup

On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract

Protocol Analysis Identification of the exploitable vulnerability in Bitget's contract logic - root cause: infrastructure

Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block

Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Market-Making Bot Exploit audit checklist and test coverage

If you're auditing a protocol with similar architecture to Bitget, these are the critical security checks that could have prevented this incident (April 2025).

Verify all logic paths related to Market-Making Bot Exploit are guarded by proper access controls and input validation
Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Sources & References

01
Source 1 https://x.com/0xDamix/status/1913918706985623945

Threat Assessment

Severity Level

CRITICAL

Attack Vector Market-Making Bot Exploit
Root Cause Infrastructure
Year 2025

Learn to Prevent the Next Bitget

The Bitget hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Start Free Trial Browse Attack Library