A post by @Phalcon_xyz on X.
Our system detected an attack on the TENDRIL/USDT liquidity pool on #BNB Chain hours ago, resulting in ~$556K in losses. The root cause was unsafe sell-tax logic that allowed the pool’s TENDRIL balance to be burned and its reserves…
@Phalcon_xyz on X
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
The exploit stemmed from unsafe sell-tax logic: a sale triggered TENDRIL's 30% tax, and the tax-handling contract's call to controlburn() and sync() reduced the pool's recorded TENDRIL reserve to near zero before the seller's remaining tokens entered the pair. The attacker used about 30.64 million USDT in flash-loan funds to buy TENDRIL and manipulate pool price and reserves, then extracted virtually the entire 4.42 million USDT reserve in a subsequent swap and repaid the loan within the same transaction. The incident highlights how token-level tax mechanics can corrupt pool accounting on BNB Chain and drain reserves even without a direct contract exploit. Watch for TENDRIL team remediation of the tax-handling logic and any compensation or migration plans for liquidity providers.
Muhabbit's AI wrote this summary of @Phalcon_xyz's post in its own words. It can get details wrong, so read the post on X.
Named in this story
TENDRIL, USDT, BNB Chain (BNB), BlockSec Phalcon
A linked name opens that asset's sentiment page.