Term Labs Hack

TOTAL LOST $8.5M
Medium Other
Affected Chain 2026 Incident surface
Recovered - No recovery reported
All-Time Rank #376 By amount stolen
Protocol Type Exploit/Other Target category

Incident Overview

On August 23, 2026, fixed-rate lending provider Term Labs suffered a governance exploit affecting its Term Vaults (built on Yearn v3 vault infrastructure), resulting in the loss of approximately $8.5 million in digital assets (~2,843 ETH and ~1.68M USDC).

The incident occurred not through a code bug or reentrancy flaw, but through the manipulation of vault governance rules enabled by low voter participation and float. The attacker initially funded with 2 ETH routed through Tornado Cash acquired sufficient voting influence to pass parameter changes as designed by the protocol's governance architecture. Once vault control was secured, the attacker executed a structured sequence of transactions that unraveled integrated positions across external lending protocols (including Aave and Morpho), unwinding staked ETH positions and draining approximately 2,843 ETH alongside 1.68 million USDC.

The attacker subsequently swapped the stolen USDC for roughly 1.6 million DAI and consolidated the funds in wallet 0xD5183d8B…8FFc13.

Key Attacker Address: 0xD5183d8B…8FFc13

Incident Report

Protocol / Project Term Labs
Date of Incident
Attack Technique Other
Classification Borrowing and Lending

Protocol Information

Protocol Type Exploit/Other
Official Website app.term.finance/
Protocol Twitter/X @term_labs
Team Anonymous
Source Code Unverified

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 Deep understanding of other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Term Labs's contract logic - root cause: borrowing and lending
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
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 Other audit checklist and test coverage

If you're auditing a protocol with similar architecture to Term Labs, these are the critical security checks that could have prevented this incident (August 2026).

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • 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

Sources & References

Learn to Prevent the Next Term Labs

The Term Labs 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