AIDC token hack — June 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | June 29, 2026 |
| Target type | Token contract |
| Loss | $121,767Price at time of incident |
| Method | Contract logic errorAIDC let ordinary transfers burn accumulated sell-side amounts directly from its AIDC/WBNB pair and sync it, so the attacker deflated the pair's AIDC reserve and drained its WBNB |
| Chains | BNB Chain |
| Outcome | Unresolved |
What happened
AIDC, a token on BNB Chain, lost the WBNB side of its AIDC/WBNB pool on 28 June 2026, in a transaction at 19:35:53 UTC. TenArmor flagged it the next day, putting the loss at about $121,100.
According to a DeFiHackLabs reconstruction, AIDC let ordinary transfers burn accumulated sell-side amounts directly from the pair and then sync it. The attacker made repeated sales from fresh helper contracts to build up the amount to burn, triggered the burns through router transfers so that the pair was synced at a deflated AIDC reserve, and sold into it.
This registry read the receipt: the pair lost 221.23 WBNB, about $121,800 at that hour's BNB price, and the attacker's address received 220.13 WBNB. The pair's loss is recorded, with the attacker's take as the lower end.
Sources
- TenArmor on XSecondary · retrieved 2026-10-06
- DeFiHackLabs exploit reconstructionSecondary · retrieved 2026-10-06
- BNB Chain transaction receipt, read by this registryOn-chain · retrieved 2026-10-06
Changes to this entry
- Recorded on 6 October 2026 in a backfill of 2026 incidents that this registry had missed, found through DeFiHackLabs' reproduction list. The amount was checked against the transaction receipt, read by this registry from a public node.
Cite this
This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.
iTokenly Hack Registry, "AIDC token hack — June 2026", iTokenly, accessed 2026-10-06, https://itokenly.com/hacks/aidc-token-bsc-june-2026https://itokenly.com/hacks/aidc-token-bsc-june-2026Permalinks never change. If an entry is renamed, the old address keeps working.
Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.