The AIDC token, operating on the BNB Chain, was exploited on June 29 for approximately $121,000. According to security analysis, the incident stemmed from a vulnerability in the project’s smart contract logic, specifically related to how the protocol handled token burning and liquidity reserves.
The attacker leveraged a flaw in the burn function to manipulate the price of AIDC relative to its liquidity pool on PancakeSwap. By incorrectly updating the internal accounting of the token reserves during a burn event, the contract allowed the exploiter to drain roughly 220.12 WBNB from the decentralized exchange venue.
🚨SlowMist TI Alert🚨
AIDC token on BSC has been exploited.
💸 Loss: 220.12 WBNB (~$120929.35)
🔍 Root Cause: AIDCToken's `_sellTransfer()` accumulates a 30% burn amount without deducting it from the seller. Subsequently, any non-Pair transfer triggers… pic.twitter.com/EnutUjxcBY
— SlowMist (@SlowMist_Team) June 29, 2026
Impact on Infrastructure and Liquidity
Analysis from security firms SlowMist and TenArmor indicated that the exploit sequence involved the manipulation of the token’s reserve figures. In standard DeFi operations, token burns should proportionally adjust the remaining supply without creating an imbalance that can be harvested for profit. In this instance, the flawed logic enabled the attacker to force an artificial price discrepancy.
The incident follows a pattern of liquidity pool drains on the BNB Chain where non-standard token mechanics interact poorly with automated market maker (AMM) infrastructures. While the AIDC project is smaller in scale compared to major DeFi protocols, the exploit highlights ongoing risks for users providing liquidity to tokens with complex, custom supply-adjustment features.
Operational Status
Security trackers noted that the stolen funds, initially held in WBNB, were moved through the attacker’s wallet addresses following the drain. The AIDC project has not yet published an official response or a comprehensive remediation plan.
For users and liquidity providers on the BNB Chain, the event serves as a practical reminder of the operational constraints inherent in “burn” and “tax” tokens. When these features are improperly integrated into smart contracts, they can create unintended attack vectors that directly impact the solvency of associated trading pools. Additional confirmation regarding any potential recovery efforts remains pending.
