Phishing, ataques e privacidade
BonkDAO: an operational failure rather than a chain exploit
Here is a summary of what appears to have happened with #BonkDAO. So you can verify it yourself, here is everything I found:
Original publication · 7 Jul 2026. Figures, claims and opinions reflect the original publication date.
As publicações originais estão em inglês. A navegação está disponível em sete idiomas.
...just another day in crypto.
Bitter, but somehow funny.
Here is a summary of what appears to have happened with #BonkDAO. So you can verify it yourself, here is everything I found:
This was not a smart contract hack, not a Solana exploit, and not some mysterious zero-day.
It is more embarrassing than that: a governance raid executed through the official DAO voting system.
The attacker bought enough $BONK voting power, pushed BIP #76 through Realms, and used the DAO’s own rules to move roughly $20M worth of BONK out of the treasury.
BonkDAO itself confirmed a malicious governance proposal drained an estimated $20M and said it had identified exchange wallets used to buy BONK before the proposal.
➡️The proposal was BIP # 76, titled “Sowellian BonkDAO.” The Realms proposal page shows the key instruction plainly:
send 4,426,104,450,305 BONK to:
9bxWkNf3BtJ6iehq9KbX9uCWMjem4TFiPZ19T2sYJHvQ
➡️Known core wallets and objects:
BonkDAO treasury:
AGkGWK1R669KDT4FCqgDgK7PgahGJPjD4J9xmVjuL9kn
Attacker recipient wallet:
9bxWkNf3BtJ6iehq9KbX9uCWMjem4TFiPZ19T2sYJHvQ
Voter / accumulation wallet:
CyEE7oHVDaFJ5xZLbXY3h2Z2uk1VwhTkdy72kPUEtypQ
Realms DAO:
84pGFuy1Y27ApK67ApethaPvexeDWA66zNV8gm38TVeQ
Realms proposal:
6wR1jdhhJ31bbdRNXva8MxqsgsNLKTxargcdAyZ7FcRj
BONK token mint:
DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263
➡️Post-drain holding wallet:
EXaJnm...eh42
➡️The attacker reportedly spent around $4.4M buying 882.285B BONK from #Binance and #Bybit, just enough to clear the roughly 879.95B BONK approval requirement.
Token-weighted voting with weak parameters guarding a treasury large enough to make the attack profitable.
Spend around $4.4M, control the vote, move around $21.2M !!
....an open bounty with a voting UI attached to it ;-)
➡️Known txs:
Main treasury drain:
5tPU1srcRcnmibB7KJi2WQ7cK4zuq5iKTMrSCLjq7hvGjuK4KUTmaHfwicixkJa5jZJmp3y98T7r2qecKV5mWw8P
Follow-up movement:
prjzkS5Rs5TStG2BdLjqLC2DGPvF5ZN3CfR6ZA1t7LePmpjd53F5mboNNBcQepJMKNfdw8uzv7GTmGFMEFuoUDN
The initial 4.4T BONK moved from the DAO treasury to the wallet ending in JHvQ.
Later, around 40B BONK, roughly $188K to $190K, was reportedly deposited to #OKX, while the remaining 4.386T BONK was moved to or held in a wallet:
EXaJnmrLf7RAKLfn1hehoKX94keKYmvZm5H5zuYVeh42
The important part is that the system worked exactly as designed, and that is the problem.
If a DAO treasury can be drained because 1 actor can buy enough voting power on exchanges, wait for low participation, pass a proposal, and execute immediately, then the treasury was never seriously protected.
It was just sitting behind a participation illusion.
This is the same rot we keep seeing in token governance: low turnout, lazy quorum design, no meaningful timelock, no emergency brake on treasury movements, and communities that only discover governance exists after the funds are gone.
The attacker did not need to break the contract. They only needed to price the weakness correctly.
A treasury with token-weighted voting and no serious execution delay is a market-priced attack surface.
I am a bit busy right now, but I put together as much as I could in a short amount of time.
DYOR, verify the wallets and transactions yourself, and learn from it.
Thanks to everyone who supports my work.


I obviously cannot prove it, but it is absolutely possible that this was organised internally or with internal help...



