GateHub Hack

TOTAL LOST $10.0M
High Access Control

Summarize with AI

Affected Chain 2019 Incident surface
Recovered - No recovery reported
All-Time Rank #304 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

GateHub's XRP Ledger wallets were compromised, resulting in a loss of approximately 23,200,000 XRP (nearly $9.5 million).

GateHub was alerted by its customers and community members about the theft of funds from their wallets. The company initiated an investigation and discovered increased API calls from a few IP addresses, which could be the method the hacker used to access encrypted secret keys. The hack was first noticed when a theft of 201,000 XRP was reported.

The offending account had stolen substantial amounts from several other XRP accounts, likely managed through GateHub. As of June 5, approximately 23,200,000 XRP was stolen from 80–90 victims, of which around 13,100,000 XRP had already been laundered through exchanges and mixer services.

The offending account's address:

https://xrpscan.com/account/r9do2Ar8k64NxgLD6oJoywaxQhUS57Ck8k

Incident Report

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

Protocol Information

Protocol Type Exploit/Access control
Official Website gatehub.net/
Protocol Twitter/X @GateHub
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Klaytn 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 GateHub'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 GateHub, these are the critical security checks that could have prevented this incident (June 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

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 GateHub

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