Garden Hack

TOTAL LOST $10.8M
High Private Key Compromised arbitrum base ethereum solana

Summarize with AI

Affected Chain arbitrum 4 chains affected
Recovered - No recovery reported
All-Time Rank #299 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Garden is the fastest Bitcoin bridge, enabling cross-chain Bitcoin swaps in as little as 30 seconds. It is built using an intents-based architecture with trustless settlements, ensuring zero custody risk for the users.

Incident Report

Protocol / Project Garden
Date of Incident
Affected Chain(s) arbitrum base ethereum solana
Attack Technique Private Key Compromised
Classification Protocol Logic
Primary Source View Post-Mortem

Protocol Information

Protocol Type Cross Chain Bridge
Official Website app.garden.finance/
Protocol Twitter/X @gardenfi

Market Context at Time of Hack

Token Price at Hack $0.5291
Market Cap at Hack $6.8M
% of Market Cap Stolen 100.00%
Token Categories
Decentralized Exchange (DEX) Exchange-based Tokens Decentralized Finance (DeFi) Arbitrum Ecosystem Ethereum Ecosystem BTCfi Protocol

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 Solana network fees while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised stake accounts and treasury wallets, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Garden'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
Audited by Audit Report 1 β€” still lost $10.8M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Private Key Compromised 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

Security Audit History

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 Garden

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