DMi Hack

TOTAL LOST $124K
Low Other

Summarize with AI

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

Incident Overview

Quick Summary

On December 8, 2025, the DMi token on BSC Chain suffered an AMM reserve-manipulation exploit, resulting in the theft of approximately 138.68 WBNB (~$124,400 USD).

Details of the Exploit

The vulnerability originated from a critical asymmetry in the DMi token's transfer implementation: when tokens were sent to the PancakeSwap liquidity pair using transfer(), the contract silently redirected 100% of the tokens to a fee/burn address instead of delivering them to the pair, while transferFrom() delivered tokens normally. This behavior violated the AMM's fundamental assumption that token transfers to the pair would actually increase its balance, causing the pair's ERC-20 balance to diverge from its reserve variables. The attacker exploited this by obtaining a flash loan of 102.7 WBNB, then alternating between transfer() and transferFrom() calls to intentionally create reserve desynchronization, where the AMM believed the pair held a large quantity of DMi tokens while those tokens were actually redirected or never deposited, ultimately triggering a final swap that overpaid WBNB far beyond normal trade amounts.

Block Data Reference

Exploit tx:

https://bscscan.com/tx/0x2330a8cf…3b9b6a

Incident Report

Protocol / Project DMi
Date of Incident
Attack Technique Other
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Other
Affected Token DMi
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 DMi's contract logic - root cause: token
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 DMi, these are the critical security checks that could have prevented this incident (December 2025).

  • 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

Browse all hacks

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

DeFiTuna $570K
Other
Cascade $1.3M
Other
Lumi Finance $264K
Other
Hinkal $820K
Other
AIDCToken $121K
Other
Polymarket $3.0M
Other

Learn to Prevent the Next DMi

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