Fetch.ai Hack

TOTAL LOST $2.6M
Medium Access Control

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2021 Incident surface
Recovered - No recovery reported
All-Time Rank #573 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Artificial intelligence research lab Fetch.ai has been granted a request to have major cryptocurrency exchange Binance identify individuals behind a $2.6 million hack.

According to a Friday Reuters report, the Royal Courts of Justice in London has ordered Binance to identify the hackers and seize the stolen assets. Fetch.ai reportedly claimed that hackers stole $2.6 million worth of cryptocurrency from its Binance account on June 6 and resold the tokens for a significantly reduced price.

This is classified as a Access Control Attacks . Compare similar hacks →

Incident Report

Protocol / Project Fetch.ai
Date of Incident
Attack Technique Access Control
Classification Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Affected Token FET
Official Website fetch.ai/
Protocol Twitter/X @Fetch_ai
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Mineable
Protocol Links

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 Fetch.ai'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 Fetch.ai, these are the critical security checks that could have prevented this incident (August 2021).

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

Access Control Attacks

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

Token of Power $472K
Access Control
Humanity Protocol $31.0M
Access Control
Tessera DAO $2.4M
Access Control
Gravity Bridge $5.4M
Access Control
Stake DAO $91K
Access Control
Third-party SquidRouterModule $3.2M
Access Control

Learn to Prevent the Next Fetch.ai

The Fetch.ai 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.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial