BuildFinance Hack

TOTAL LOST $470K
Low Access Control

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1001 By amount stolen
Protocol Type Yield Aggregator Target category

Incident Overview

The exploiter's address:

https://etherscan.io/address/0xdcc8a38a…952c28

The Build Finance DAO has been the victim of a hostile governance takeover in which a malicious actor proposed and was successful in gaining control of the Build token contract.

The proposal was made by a wallet named Suho.eth but it was failed.

However, it appears that the exploiter transferred their governance tokens to another wallet and attempted again. This idea, however, was not picked up by the bot on the Discord server. This idea seemed to go ignored until it was passed on February 10th.

The attacker exploited their newly acquired access over the DAO and its token minting capabilities to generate 1.1 million BUILD tokens for himself. They drained the liquidity pools on two decentralized exchanges, Balancer and Uniswap. Following that, they removed 130,000 METRIC tokens from the project's treasury, sold them, and minted 1 billion BUILD tokens additionally.

After, the exploiter deposited stolen funds into the Tornado Cash mixer

Incident Report

Protocol / Project BuildFinance
Date of Incident
Attack Technique Access Control
Classification Yield Aggregator

Protocol Information

Protocol Type Yield Aggregator
Affected Token BUILD
Official Website build.finance/
Protocol Twitter/X @finance_build
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
BNB Chain 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 BuildFinance'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 BuildFinance, these are the critical security checks that could have prevented this incident (February 2022).

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

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