# DxSale Liquidity Lockers Drained in $7.3M BNB Chain Exploit

**Published:** 2026-05-29T10:42:38.000Z  
**Topic:** Web3  
**Sentiment:** bearish  
**Publisher:** TrendWatcher — https://www.trendwatcher.in/article/22f93227-d6e9-4a81-9cbd-cf014df68507

Attackers drained $7.3 million from DxSale liquidity lockers on the BNB Chain, impacting 1,400 providers through a vulnerability in legacy contract designs.

The decentralized finance platform DxSale suffered a security breach resulting in the loss of approximately $7.3 million in assets from its BNB Chain liquidity locker contracts [1]. The exploit, which affected roughly 1,400 liquidity providers, targeted older infrastructure that had been utilized by token projects since the 2021 BNB Chain market expansion [2].

**Key takeaways**
* Approximately $7.3 million was drained from DxSale liquidity lockers, impacting about 1,400 liquidity providers [1].
* Security analysts identified a "backdoor" in the deployer contract that allowed for the manipulation of locked balances [1].
* The exploit involved a series of ownership transfers and obfuscation transactions before the final withdrawal of BNB tokens [1].
* The incident highlights significant risks associated with legacy DeFi infrastructure that remains active long after initial deployment [2].

## Mechanics of the Liquidity Locker Breach
According to the Web3 security firm Coinsult, the vulnerability stemmed from a combination of a privileged "setFee" function and a backdated lock mechanism [1]. This design flaw effectively allowed the attacker to convert previously "locked" deposits into withdrawable balances [1]. On-chain analyst Tahax reported that the DxSale deployer had transferred ownership of the locker contract to a new wallet 269 days prior to the incident, alleging that this was done without an official public announcement [1].

Following this ownership change, the attacker reportedly executed approximately 80 transactions to obfuscate the path of the funds before the contract ownership was moved to a final wallet, identified as ‘0xC45,’ which initiated the mass withdrawal of BNB [1]. PeckShield data indicates that the attacker subsequently moved portions of the stolen funds through infrastructure designed to complicate on-chain tracing [1]. While the platform has been approached for comment regarding the final number of affected parties, the incident remains a subject of ongoing analysis by security firms [1].

## Why it matters
The DxSale exploit serves as a stark reminder that "locked" liquidity is not a universal guarantee of safety, as the security of these assets is entirely dependent on the underlying smart contract design and administrative permissions [2]. Because legacy contracts often remain operational for years, they can become attractive targets for attackers if they contain hidden backdoors or forgotten admin keys [2]. 

For participants in the DeFi ecosystem, the incident underscores the necessity of looking beyond simple "liquidity locked" badges. Experts suggest that users should conduct deeper due diligence by verifying contract ownership, checking for potential minting or blacklist functions, and reviewing the history of the specific locker contract before interacting with new assets [2]. As the total value lost to crypto exploits continues to climb—with DefiLlama tracking over $17 billion in historical losses—the DxSale case highlights the persistent risk posed by aging, unmonitored DeFi infrastructure [1].

## Sources
1. Cointelegraph — [DxSale drained for $7.3M in BNB Chain liquidity exploit](https://cointelegraph.com/news/memecoin-platform-dxsale-drained-73m-1400-lps)
2. Guardarian — [Hack Explained: $7.3M BNB Chain Exploit](https://guardarian.com/blog/dxsale-hack-bnb-chain-exploit)
3. Cryptotimes — [Hackers Drain $7.3M From DxSale’s Old BNB Chain Liquidity Lockers](https://www.cryptotimes.io/2026/05/29/hackers-drain-7-3m-from-dxsales-old-bnb-chain-liquidity-lockers/)

---
Cite as: TrendWatcher, "DxSale Liquidity Lockers Drained in $7.3M BNB Chain Exploit", https://www.trendwatcher.in/article/22f93227-d6e9-4a81-9cbd-cf014df68507