According to SlowMist monitoring, the AIDC Token on BSC was attacked, resulting in a loss of 220.12 WBNB, about $120,900. SlowMist said the root cause is that AIDCToken’s _sellTransfer() accumulates a 30% burn amount but does not deduct it from the seller; subsequently, any arbitrary non-Pair transfer triggers _executeAccumulatedBurn(), which incorrectly burns tokens from the uniswapPair balance rather than the seller’s balance, and calls sync(), artificially lowering the AIDC reserves in the AMM, allowing the attacker to withdraw WBNB.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 4
  • Repost
  • Share
Comment
Add a comment
Add a comment
StarsInTheGlassDome
· 06-29 07:23
SlowMist's analysis this time is clear, but didn't the project team run tests themselves before launch?
View OriginalReply0
KiteStringQuant
· 06-29 04:55
120K USD is not big for the BSC ecosystem, but this basic math error is quite ridiculous.
View OriginalReply0
GovernanceVoting
· 06-29 04:40
_sellTransfer doesn’t deduct money from the seller, yet it keeps accumulating and destroying—who wrote this code…
View OriginalReply0
DepegDaydream
· 06-29 04:32
Another smart contract logic vulnerability - the burn mechanism is reversed. How did it pass the audit?
View OriginalReply0
  • Pinned