Hacker Returns 15,000 BNB to 79thVault in Rare Crypto Recovery
79thVault disclosed an incident tied to its 79AU pool on BNB Chain after tokens were drained and the proceeds were moved in BNB. The project later said its operator’s private key was compromised, and afterward 15,000 BNB was returned to a hot wallet, while one account of the attack still left the total proceeds unsettled.
What this rests on
What it means
Each sentence links inside to the piece that supports it.
Users and holders of the 79AU pool are the ones most likely to notice this first, because funds were drained from the pool and later 15,000 BNB was sent back to a hot wallet. In practical terms, the event touched the pool’s assets and then partially reversed that movement, so anyone watching the protocol would see both the drain and the return on-chain.
Before this, the pool had burn activity tied to 79% of its liquidity-provider receipts, but that did not stop the drain, and residual transfer permissions were still present in the token contract. What changed in practice is that the incident exposed a permission path that remained usable even after the burn activity, while the later return of funds did not erase the fact that the attack had already occurred.
Market reaction
How the story was built
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 4.3 years ago | Uniswap incident | $12.9M |
| 12 months ago | Berachain incident | $12.8M |
| 5.9 years ago | Compounder Finance · Admin Drain incident | $12.5M |
| 1.7 years ago | Ionic incident | $12.3M |
| 1.4 years ago | Corkprotocol incident | $12M |
4197 incidents stored · 279 were as large as this one or larger ($12.5M)