Gate Hack

TOTAL LOST $235M
Critical #42 All-Time Private Key Compromised (Unknown Method) / Access Control

Summarize with AI

Affected Chain 2018 Incident surface
Recovered - No recovery reported
All-Time Rank #42 By amount stolen
Protocol Type CEX Target category

Incident Overview

Gate.io crypto exchange's cold wallets were exploited via access control. The previous hacker address on the 2015 exploit was involved in this one too. The stolen amount reached roughly 230,000,000 $USD.

Gate.io is a centralized crypto exchange. The exchange's cold wallet's private keys were compromised. There is an address involved in the previous 14 February 2015 hack.

The total stolen funds were valued at 234,337,668 $USD at the moment of the accident, which contains 10,777 $BTC, 218,790 $ETH, 175,866 $ETC, 3,043,268 $XRP, 11,000 $LTC, 3,783 $ZEC, and 99,999,000 $DOGE.

Compromised address:

https://www.blockchain.com/btc/address/1M2bv6sypZSp6uAEC9U4Gzvgp6jd29F87e

Major transactions:

https://www.blockchain.com/btc/tx/086f9d27f574c7a1b9179fc7524c2a5227a095ca7c3b096d93ed6fbf8e92af16

https://www.blockchain.com/btc/tx/d08acac36311373f81f45179de3aa72174cb665122eb2aadefc74738fc6cbcd5

Incident Report

Protocol / Project Gate
Date of Incident
Attack Technique Private Key Compromised (Unknown Method) / Access Control
Classification Infrastructure / CeFi
Primary Source View Post-Mortem

Protocol Information

Protocol Type CEX
Affected Token GT
Official Website www.gate.io/
Protocol Twitter/X @gate_io
Team Public / Doxxed
Source Code Unverified

Market Context at Time of Hack

Token Categories
Decentralized Exchange (DEX) Token DeFi Privacy Zero Knowledge Proofs Ethereum Ecosystem DEX

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 Gate'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? Hard to catch — private key / OpSec failures are outside smart contract audit scope

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

  • Verify all logic paths related to Private Key Compromised (Unknown Method) / 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

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 Gate

The Gate 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