Bithumb Hack

TOTAL LOST $19.2M
High Access Control

Summarize with AI

Affected Chain 2019 Incident surface
Recovered $14.0M 72.9% returned
All-Time Rank #235 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Bithumb suffered an insider attack leading to abnormal withdrawals but managed to recover approximately $14m.

Bithumb detected unusual withdrawals through their monitoring system. The incident was an "accident involving insiders." The exchange's EOS hot wallet began sending EOS to the attacker's address. The company realized the attack was ongoing and started to move the funds to the cold storage wallet, which was not compromised.

Bithumb admitted that it had only focused on protection from outside attacks and did not verify its staff.

The attacker's address:

https://bloks.io/account/ifguz3chmamg

The exchange hot wallet:

https://bloks.io/account/g4ydomrxhege

Bithumb's claim about $14m recovery:

https://www.econotimes.com/Bithumb-claims-recovery-of-14M-in-hacked-cryptocurrencies-1396613

Incident Report

Protocol / Project Bithumb
Date of Incident
Attack Technique Access Control
Classification CeFi

Protocol Information

Protocol Type Exploit/Access control
Official Website www.bithumb.com/
Protocol Twitter/X @BithumbOfficial
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Collectibles & NFTs Gaming DAO Solana Ecosystem Metaverse Elrond Ecosystem MultiversX Ecosystem

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Bithumb's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Access Control audit checklist and test coverage

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

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • 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

Funds Recovery

72.9%

Recovered

$14.0M

Net Loss

5203199

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Bithumb

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

Recreate exploit patterns safely Free Trial