Bitquery finds $14.35 million USDT drained from 79AU pool on PancakeSwap despite burned liquidity receipts
Bitquery investigation reveals a $14.35 million USDT drain from the 79AU pool on PancakeSwap on October 7, exploiting a token permission that bypassed burned liquidity receipts.
Why it matters
The incident shows that burning liquidity receipts does not secure a pool if the token contract itself contains permissions allowing unauthorized token transfers. This highlights a smart-contract design risk for DeFi protocols relying solely on LP token burns for security.
Key facts
Bitquery traced a $14.35 million USDT drain from the 79AU pool on PancakeSwap on October 7.
14,350,000 USDReported by CryptoSlate
79% of the pool's liquidity-provider receipts had been burned before the drain.
79 %Reported by CryptoSlate
A permission in the 79AU token contract allowed tokens to leave the pool without payment, bypassing LP receipt redemption.
Reported by CryptoSlate
The drained tokens were sold back for USDT through swap operations that do not consume liquidity receipts.
Reported by CryptoSlate
Read-only tests conducted by Bitquery moved no funds.
Reported by CryptoSlate
What happened
CryptoSlate reported that Bitquery traced a $14.35 million USDT drain from 79AU's PancakeSwap V2 pool on October 7. Although 79% of liquidity-provider receipts had been burned — which normally prevents redemption — a separate permission in the 79AU token contract allowed tokens to exit the pool without payment. Those tokens were then sold back for USDT. Bitquery's October 8 snapshot showed two addresses retained pull rights, though read-only tests moved no funds. The exploit bypassed standard LP redemption by using swap operations that do not consume liquidity receipts.
How the story developed
- Update
Drain occurs on PancakeSwap 79AU pool
$14.35 million USDT drained through two selling wallets
- Update
Bitquery publishes investigation findings
Analysis reveals burned LP receipts did not prevent the exploit due to token contract permission
- First report
First report by CryptoSlate
Locked liquidity did not stop this $14 million crypto pool drain
- Update
CryptoSlate reports on Bitquery investigation
Article published detailing the exploit mechanism and findings
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| CryptoSlate Crypto media | Locked liquidity did not stop this $14 million crypto pool drain | Original |