AROS token hack — May 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | June 1, 2026 |
| Target type | Token contract |
| Loss | $295,314Price at time of incident |
| Method | Other or undisclosedUndisclosed: a flash-loan transaction drained the USDT side of the AROS/USDT pool; no root cause has been published |
| Chains | BNB Chain |
| Outcome | Unresolved |
What happened
AROS, a token on BNB Chain, lost about $295,000 from its AROS/USDT pool on 30 May 2026, in a transaction at 18:24:07 UTC. TenArmor flagged it on 1 June, putting the loss at about $295,300.
The attack used flash loans from Uniswap V3-style pools, and DeFiHackLabs has reproduced it, but no root cause has been published, so the vector is recorded as undisclosed.
This registry read the receipt: the pool lost 301,279.55 USDT, of which the attacker's address received 295,314.04 USDT; about 5,966 USDT went to roughly twenty other addresses in small amounts that look like the token's fee and reward payouts. The attacker's take is recorded, with the pool's loss as the upper end. No statement from the project has been found.
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, "AROS token hack — May 2026", iTokenly, accessed 2026-10-06, https://itokenly.com/hacks/aros-token-bsc-may-2026https://itokenly.com/hacks/aros-token-bsc-may-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.