DBXen
- Funds lost
- $150K
- Attack type
- Access Control
- Network
- Ethereum, BNB Chain
- Category
- Token
Summary
On March 11, 2026, DBXen suffered a $150K exploit across Ethereum and BSC when an attacker exploited an inconsistent sender identity vulnerability in ERC2771 meta-transactions, where burnBatch() used _msgSender() (actual user) while the callback onTokenBurned() used msg.sender() (forwarder), breaking reward accounting logic and allowing excess fund withdrawal.
Details of the Exploit
The vulnerability stemmed from inconsistent sender identity handling in DBXen's meta-transaction implementation. In the burnBatch() function, the gasWrapper() modifier updated state using _msgSender() which correctly identified the actual user, but the subsequent onTokenBurned() callback used msg.sender() which identified the forwarder contract instead. This caused accCycleBatchesBurned to be recorded for the user while lastActiveCycle was incorrectly updated for the forwarder.
When claimFees() and claimRewards() executed updateStats() for the user, the contract detected that accCycleBatchesBurned[user] had increased but lastActiveCycle[user] had not, incorrectly assuming unprocessed burned batches existed. This state inconsistency caused the contract to miscalculate rewards and fees, allowing the attacker to withdraw significantly more funds than entitled. The attack was executed across both Ethereum and BSC chains.
Blockchain Data Reference Exploit txs: https://etherscan.io/tx/0x914a5af790e55b8ea140a79da931fc037cb4c4457704d184ad21f54fb808bc37 https://bscscan.com/tx/0xe66e54586827d6a9e1c75bd1ea42fa60891ad341909d29ec896253ee2365d366
Source: De.Fi REKT Database. Data as of November 19, 2026.