Dynamic Hack

TOTAL LOST $22K
Low Reentrancy

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1875 By amount stolen
Protocol Type Exploit/Reentrancy Target category

Incident Overview

Quick Summary

Dynamic Finance suffered a reentrancy bug attack on February 22, 2023, resulting in a loss of 73 BNB, approximately $22,400.

Details of the Exploit

The attacker used a reentrancy bug that tricked the deposit tracking system of the StakingDYNA contract. By taking out a large flash loan to borrow $DYNA and depositing it before redeeming the deposit, the attacker was able to earn rewards and pay back the flash loan, resulting in a profit. After withdrawing funds from one address, the attacker transferred the funds to the next address for the same operation, allowing them to profit multiple times.

Block Data Reference

Attacker:

https://bscscan.com/address/0x0c925a25…410094

This is classified as a Reentrancy . Compare similar hacks →

Incident Report

Protocol / Project Dynamic
Date of Incident
Attack Technique Reentrancy
Classification Yield Aggregator
Primary Source View Post-Mortem #1 View Post-Mortem #2 View Post-Mortem #3

Protocol Information

Protocol Type Exploit/Reentrancy
Affected Token DYNA
Official Website www.torque.fi/
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 reentrancy 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 Dynamic's contract logic - root cause: yield aggregator
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? Yes — skilled auditors routinely flag Reentrancy vulnerabilities in code review

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

  • Verify all logic paths related to Reentrancy are guarded by proper access controls and input validation - see the Reentrancy attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • 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 Reentrancy examples →

Reentrancy

Sources & References

Browse all hacks

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

1Inch $2.6M
Reentrancy
StepHeroNFTs $90K
Reentrancy
Clober Liquidity Vault $500K
Reentrancy
Clober $500K
Reentrancy
Penpie $27.0M
Reentrancy
PolyNetwork $5.0M
Reentrancy

Learn to Prevent the Next Dynamic

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