Hack history / 2026 / Hack or exploit
SAS Token
Hack or exploit on Apr 2, 2026 · Smart Contract Vulnerability
ONE SOURCE · 1 SOURCE
Lost
$12K
dollars at the time
Returned
none listed
as the sources state it
Rank
#2,222
among thefts by dollars lost
What happened
The SAS Token on BNB Chain was exploited via a flawed custom transfer logic (Deferred Burn Exploit). The token’s custom transfer logic had a flaw: sending SAS to the LP pool only incremented a global sellBurn counter, while any subsequent ordinary transfer could burn SAS directly from the pool and call sync() to rewrite reserves, bypassing the AMM’s swap logic. The attacker accumulated sellBurn credit through sells, triggered an unrelated ordinary transfer to burn SAS from the pool down to ~1 wei, and then reverse-swapped to extract profit.
Details
- Date
- Apr 2, 2026
- Kind
- Hack or exploit
- Method
- Smart Contract Vulnerability
- How in
- Smart contract bug
- Target
- not stated
- Chains
- BNB Chain
Reported by
Related incidents
RsETHSafeModule 2026 · Hack or exploit · $7.7M
Third-party Gnosis Safe Module (SquidRouterModule) 2026 · Hack or exploit · $3.2M
Haedal Vault 2026 · Hack or exploit · $915K
NEM（NemTokenV2） 2026 · Hack or exploit · $822K
Butter Bridge 2026 · Hack or exploit · $180K
Third-party Gnosis Safe Module (SquidRouterModule) 2026 · Hack or exploit · $3.2M
Haedal Vault 2026 · Hack or exploit · $915K
NEM（NemTokenV2） 2026 · Hack or exploit · $822K
Butter Bridge 2026 · Hack or exploit · $180K
Cite this page
SwanBluechip, "SAS Token hack, Apr 2, 2026: $12K lost", Crypto hack history, https://swan-hack-tracker.pages.dev/history/i/ht5eada11afa/ (data as of 2026-11-01).