Solana

Million

Bonk

<p>There was no code exploit. No compromised private key. No phishing link. And yet BonkDAO says attackers stole about $20 million in BONK through a malicious governance proposal targeting its Solana treasury.&nbsp;</p>
<p><strong>The attacker didn't break the rules — they bought them.</strong></p>
<h2 id="what-happened-to-bonk-dao">What happened to BONK DAO?</h2>
<p>$BONK is a Solana-based memecoin, and BONK DAO is the community body that governs it. Token holders vote on proposals, and if a vote passes, it executes automatically on-chain. That design is exactly what got weaponized.</p>
<p>The sequence began on June 30, when an anonymous wallet submitted a proposal to transfer the treasury's holdings to a wallet it controlled. That proposal was titled "BIP #76 – Sowellian BonkDAO," and it read more like a pitch than a heist: it sought to "implement Sowellian governance, install new members and council, rebuild from the ashes, monetize holdings, and stop the bleeding," and dangled a reward promising all "yes" voters would be eligible to receive BONK tokens.&nbsp;</p>
<p>Buried underneath the marketing language sat the only line that mattered — an instruction to transfer roughly 4.4 trillion BONK straight to the attacker's wallet.</p>
<h2 id="how-did-the-attacker-pass-a-fake-proposal">How did the attacker pass a fake proposal?</h2>
<p>This is the part that should keep every DAO up at night. The proposal needed "yes" votes equal to 1% of BONK's supply to hit quorum. So the attacker simply went and bought it. Over July 4 and 5, a separate wallet acquired exactly that much, spending about $4.4 million to buy BONK on the <a href="https://cryptoticker.io/en/comparison/exchange-comparison/" rel="noopener noreferrer nofollow">exchanges</a> Bybit and Binance.&nbsp;</p>
<p>By the time voting closed, the numbers were almost surgically precise. The proposal passed with just seven wallets voting, against more than 18,000 members who did not — a turnout of 2.9%. It cleared quorum by the narrowest margin, 882.38 billion BONK in favor against an 879.95 billion threshold, almost exactly the stake the attacker had spent days assembling.</p>
<p>The result? The 99.9% "yes" result was effectively a single voter agreeing with itself. The DAO then did what it was built to do — it executed the transfer automatically, and about $20 million in BONK moved out of the treasury into the attacker's wallet.&nbsp;</p>
<h2 id="bonk-dao-attack-where-did-the-money-go">Bonk DAO Attack: Where did the money go?</h2>
<p>The stolen <a href="https://cryptoticker.io/en/token/" rel="noopener noreferrer nofollow">tokens</a> didn't stick around. More than 4.4 trillion BONK — valued at approximately $19.3 million at the time of transfer — moved out of the treasury to an address ending in "JHvQ," identified via Solscan as having been funded through a Bybit account. By 3:30 p.m. ET the same day, the tokens had been moved again, this time to a different Solana address ending in "eh42."</p>
<p>The promised voter rewards never materialized. The tokens were never distributed — instead they were shuffled to a second address hours later, a pattern consistent with an attacker trying to obscure the trail rather than honor any community commitment. Security firm PeckShield later flagged that roughly $148,000 worth of stolen BONK has already moved to OKX.</p>
<h2 id="was-bonk-dao-hacked">Was Bonk DAO Hacked?</h2>
<p>Technically, no — and that's the uncomfortable part. The attacker didn't exploit a bug in any smart contract. The root issue was governance design, not code. Every single step was a valid, authorized on-chain transaction.</p>
<p>With no timelock, quorum minimum, or multisig check in place to catch an anomalous proposal before it executed, a well-funded attacker was able to turn a $4 million token purchase into control over a $20 million treasury. A timelock would have forced a delay between approval and execution, giving the community a window to spot the drain. A multisig override could have frozen it in an emergency. BONK DAO had neither.</p>
<p>This has reopened an old debate. Because every step was a valid transaction, some on-chain observers argued the attacker simply exploited a weak governance design rather than breaking in. The lesson stands either way: a treasury that can be drained by whoever assembles a temporary voting majority is only as secure as the cost of buying that majority — and here, that cost was a fraction of the prize.</p>
<h2 id="what-is-bonk-dao-doing-about-it">What is BONK DAO doing about it?</h2>
<p>BonkDAO has notified law enforcement and is working with the Solana Foundation, centralized exchanges, and network bridges to recover funds. It said it had identified the exchange wallets used to buy tokens ahead of the vote — and the involvement of law enforcement makes clear the DAO is treating this as an attack, not a clever loophole.</p>
<p>Recovery, though, is an uphill battle. Governance attacks are notoriously hard to reverse precisely because they run through the protocol's own legitimate machinery.</p>
<h2 id="how-did-bonk-s-price-react">How did BONK's price react?</h2>
<p>The market response was surprisingly contained given the scale. BONK prices are down about 7% in the past 24 hours in the aftermath of the attack. Exchanges moved fast — South Korean exchange Upbit and American exchange Kraken both paused deposits and withdrawals of the BONK token, with Upbit citing "user protection measures following the circumstances of a security incident."</p>

BONK DAO Lost $20 Million Without a Hack — Here's How a Governance Attack Drained the Treasury

Table of Contents

CryptoTicker ENG

Other articles published on Jul 7, 2026

Join our free newsletter for daily crypto updates!