1inch Hack

TOTAL LOST $720K
Low Private Key Compromised (Supply Chain Attack) avalanche

Summarize with AI

Affected Chain avalanche Incident surface
Recovered - No recovery reported
All-Time Rank #890 By amount stolen
Auditors 1 Prior security audit

Incident Overview

1inch is the DeFi ecosystem building financial freedom for everyone

Incident Report

Protocol / Project 1inch
Date of Incident
Affected Chain(s) avalanche
Attack Technique Private Key Compromised (Supply Chain Attack)
Classification Ecosystem
Primary Source View Post-Mortem

Protocol Information

Protocol Type DEX Aggregator
Official Website 1inch.com
Protocol Twitter/X @1inch

Market Context at Time of Hack

Token Categories
Decentralized Exchange (DEX) Token DeFi Wallet Ethereum Ecosystem AMM YZi Labs Portfolio Avalanche Ecosystem Solana 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 1inch'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 $720K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Private Key Compromised (Supply Chain Attack) 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 1inch

The 1inch 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