What happened to BonkDAO in July 2026?

On July 6, 2026, an attacker spent about $4 million buying BONK, then used that voting power to pass a malicious governance proposal, BIP #76 on Solana's Realms platform, that sent roughly 4.4 trillion BONK, near $20 million, from the BonkDAO treasury to their own wallet. It was a governance takeover using token-weighted voting rules, not a smart-contract hack. The official Bonk account confirmed the treasury was drained.

How much was drained from the BonkDAO treasury?

The proposal moved 4,426,104,450,305 BONK, about 4.4 trillion tokens, worth close to $20 million at the price at the time and equal to roughly 5% of BONK's total supply of about 88 trillion. The official Bonk statement put the figure at an estimated $20 million.

Was BonkDAO hacked, or was this a governance exploit?

It was a governance exploit, not a code hack. No smart contract was broken. The attacker exploited the rules of token-weighted voting: they bought enough BONK to control about 99.878% of the votes, tabled a proposal, waited out a roughly six-day window in which only 7 wallets voted, then passed it. With no timelock or multisig on the treasury, the funds moved automatically once the vote passed.

Can the drained BONK be recovered?

It is uncertain and time-sensitive. On-chain, the funds were already moved out of the attacker's wallet toward exchanges within about ten hours. The Bonk team says it has identified the exchange wallets used, notified law enforcement, and is working with the Solana Foundation, exchanges and bridges to freeze and recover the tokens. Upbit paused BONK deposits and withdrawals, and Kraken reportedly did too, to block cashing out.

How can DAOs prevent governance attacks like this?

With standard safeguards that BonkDAO lacked: a quorum requirement so a proposal cannot pass on near-zero turnout, a timelock that delays fund movement after a vote passes so the community can react, a multisig on the treasury, and active voter participation. Token-weighted voting means governance is effectively for sale to whoever holds the most tokens, so these guardrails are essential.

A Hacker Spent $4M to Legally Vote $20M Out of BonkDAO. Here Is the On-Chain Trail

July 7, 2026 — By Tony Rabbit in News

An attacker spent roughly $4M on BONK to control a DAO vote, then passed a proposal that drained about 4.4 trillion BONK, near $20M, from the BonkDAO treasury. We read the chain: the funds hit the attacker's wallet and were gone within hours.

This is the funniest and most alarming crypto story of the week, and it is entirely real. Someone spent about $4 million buying BONK, used it to pass a governance proposal that almost no one voted on, and legally voted roughly $20 million of BONK out of the token's own treasury and into their wallet. No code was hacked. The attacker simply played the rules of token-weighted voting to their logical, brutal conclusion. The official BonkDAO account confirmed it, and we traced the money on-chain. Here is exactly how the takeover worked, and where the funds are now.

~$4M

spent buying BONK to acquire the votes

~$20M

in BONK drained from the treasury

99.878%

of the vote the attacker controlled

7 wallets

total turnout over about six days

How the governance takeover worked

BonkDAO is the governance body of BONK, the large Solana memecoin, and it runs on Solana's Realms platform, standard on-chain voting where one token equals one vote. That design is the entire vulnerability. On July 6, 2026, an attacker who had accumulated a huge BONK position tabled a proposal, BIP #76, titled "Sowellian BonkDAO," full of grand language about installing new members, rebuilding "from the ashes," and making "all YES voters eligible to receive tokens." Buried in the proposal was the real payload: send roughly 4.4 trillion BONK from the treasury to a specific wallet.

How the governance takeover worked

Buy the votes

The attacker spent about $4M on BONK, enough to control roughly 99.878% of the active voting power.

Table a proposal

They created BIP #76 on Solana's Realms platform, worded so that YES voters would receive treasury tokens.

Wait out the clock

The proposal sat live for about six days. Only 7 wallets ever voted, and no one raised the alarm.

Vote YES, and drain

With their own votes it passed, and with no timelock or multisig to stop it, roughly 4.4 trillion BONK left the treasury.

Because votes are weighted by tokens held, and the attacker had spent around $4 million to hold the most, they controlled the outcome from the start. The proposal did the rest of the work by simply existing quietly.

The vote nobody showed up for

The proposal sat live for about six days. In that entire window, only 7 wallets voted, a turnout of roughly 2.9%, and the attacker's own holdings made up about 99.878% of the votes cast. When the timer ran out, the attacker voted YES, the proposal passed, and because there was no timelock or multisignature step between a passed vote and the treasury acting, the funds moved automatically. A $20 million decision was made by almost nobody.

Bar chart of the BonkDAO BIP-76 vote July 2026: the attacker controlled about 99.878 percent of the votes versus 0.122 percent for everyone else, with only 7 wallets voting over six days — The vote that drained a $20M treasury: the attacker had bought almost all the voting power, and almost no one else showed up.

What the chain shows now

We pulled the destination wallet on Solana. The exact figure in the proposal was 4,426,104,450,305 BONK, about 4.4 trillion tokens, worth close to $20 million at the current price and equal to roughly 5% of BONK's entire 88 trillion supply. The wallet has made just 7 transactions, all on July 6. The BONK arrived and was then moved onward within about ten hours, hopping toward exchanges through a second address. As of our check, the attacker wallet holds 0 BONK and only about 1.46 SOL left for gas. In other words, the loot was already on the move before most people had read the headline, which is exactly why recovery is a race.

Bonk's response and the recovery race

The official Bonk account did not hide from it. Its statement: "BonkDAO was the target of a malicious governance proposal resulting in an estimated $20M worth of BONK tokens being drained from the BonkDAO treasury." The team says it has identified the exchange wallets used to buy the BONK before the vote, notified law enforcement, and is working with the Solana Foundation, exchanges and bridges to try to freeze and recover the funds. Upbit paused BONK deposits and withdrawals, and Kraken reportedly did the same, standard moves to block an attacker from cashing out. BONK's price fell roughly 9 to 10% on the news.

The real lesson: governance is an attack surface

It is tempting to laugh at a DAO that let one wallet vote away its own treasury, but the mechanism is a genuine, recurring risk across DeFi, and it is a design failure, not a coding one. Token-weighted voting means governance is for sale to whoever buys the most tokens, and when turnout is near zero and there are no safety rails, a well-funded attacker can pass almost anything. The defenses are known: quorum requirements, a timelock between a vote passing and funds moving, a multisig on the treasury, and active voter participation. To understand how voting power and control risk actually work, read our guide to DAO quorum and whale voting, learn what BONK is in our BONK ecosystem explainer, and screen any token you hold with the Token Safety Checker. We will update this piece as the funds move or are recovered.

What the chain confirms

about 4.4 trillion BONK, near $20M and roughly 5% of supply, left the treasury
the destination wallet made just 7 transactions, all on July 6
the BONK arrived and was fully moved onward within about 10 hours; the wallet now holds 0 BONK and 1.46 SOL

Why it worked

token-weighted voting: whoever holds the most tokens decides, and the attacker bought the most
near-zero turnout: only 7 wallets voted over about six days, so nobody objected
no safety rails: no timelock or multisig sat between a passed vote and the treasury moving funds

Methodology and disclaimer: the drained amount (4,426,104,450,305 BONK), the destination wallet's balance and its 7 transactions were read on-chain from Solana on July 7, 2026; BONK price and supply (about $0.0000043 and ~88 trillion) are from CoinGecko, putting the drain near $20 million. The proposal details, the 99.878% vote share, about six-day window, roughly $4M spend, and the exchange pauses are as reported by the official BonkDAO account and outlets including CoinDesk, The Block and crypto.news; the Kraken pause is reported by a single source. This was a governance exploit of token-weighted voting, not a smart-contract code bug. The attacker is referenced by wallet address only. This article is for information only and is not financial advice.