BigONE Hack

TOTAL LOST $28.0M
High #177 All-Time Access Control

Summarize with AI

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

Incident Overview

On July 16, 2025, BigONE exchange suffered a security incident involving unauthorized access to their hot wallet, resulting in approximately $28 million in stolen cryptocurrency across multiple blockchains. The exchange confirmed that all user assets remain safe and that BigONE will fully bear all losses from the incident.

The attacker gained unauthorized access to BigONE's hot wallet infrastructure and drained funds across four major blockchains. The distribution of stolen assets includes $14 million in Bitcoin, $7 million in various cryptocurrencies on Ethereum and BNB Chain (with funds consolidated via cross-chain bridge to Ethereum), $7 million in TRX on Tron, and $500,000 in SOL on Solana. The attack appears to be a traditional hot wallet compromise rather than a smart contract exploit, with the attacker systematically draining funds from multiple blockchain networks.

BigONE has temporarily suspended trading and deposits, with withdrawals to resume after security upgrades are implemented.

Bitcoin Address:

bc1qwxm53zya6cuflxhcxy84t4c4wrmgrwqzd07jxm

Tron Address:

TCAfB8jHbJ56xwmfwKwWEs8HLRjbC2GfHG

Ethereum Address:

0x0a360bd6…305f4f

Incident Report

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

Protocol Information

Protocol Type CEX
Official Website big.one/
Protocol Twitter/X @BigONEexchange
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Memes Polygon 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 BigONE'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 BigONE, these are the critical security checks that could have prevented this incident (July 2025).

  • 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 BigONE

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