LAXO token hack — February 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | February 22, 2026 |
| Target type | Token contract |
| Loss | $190,540Price at time of incident |
| Method | Contract logic errorSelling LAXO into its PancakeSwap pool burned most of the transferred tokens and synced the reserves before the pool priced the trade, so the remainder sold at an inflated price |
| Chains | BNB Chain |
| Outcome | Unresolved |
What happened
LAXO, a token on BNB Chain, lost about $190,500 from its PancakeSwap LAXO/USDT pool on 22 February 2026, in four transactions by three addresses between 15:32 and 15:46 UTC. CertiK analysed it together with the SOF exploit of 14 February, which used the same class of flaw.
According to CertiK, when LAXO was sent to the pool the token contract took a sell fee, burned the rest of the transferred amount and synced the pool before the pool worked out the USDT owed. The first attacker borrowed 350,000 USDT, bought about 43.2m LAXO, routed them back to itself through an add-and-remove-liquidity step that avoided the fee, then sold into the pool: 41.1m LAXO were burned, the pool's LAXO fell from about 54m to 13m, and the sale was priced against the depleted reserve. Two other addresses repeated the attack within 13 minutes.
By CertiK's count the attackers kept 190,540 USDT: 137,320 and 45,061 USDT from the first attacker's two transactions, 6,974 USDT for the second and 1,185 USDT for the third. This registry read the first transaction: the pool paid out a net 263,903.60 USDT, of which 137,320.18 went to the attacker's contract and 126,408.42 was sold out of the pool by the token's own fee mechanism and sent to two fee wallets. The attackers' 190,540 USDT is recorded, with the pool's net outflow across the four transactions, about 354,336 USDT, as the upper end.
Sources
- CertiKSecondary · retrieved 2026-10-06
- CertiK Alert 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, "LAXO token hack — February 2026", iTokenly, accessed 2026-10-06, https://itokenly.com/hacks/laxo-token-bsc-february-2026https://itokenly.com/hacks/laxo-token-bsc-february-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.