Governance tokens are supposed to give you a vote, not hand someone the keys to the vault.
The Summary
- An attacker seized control of X100's governance, drained 4.85 million USDT from treasury and liquidity positions via two transactions, then converted 4.75M USDT to ETH and split proceeds across four 400-ETH wallets
- Blockaid flagged the attack as ongoing while it was happening, but the damage was already done
- This wasn't a smart contract bug. It was a governance design failure that gave one actor enough voting power to empty the treasury.
The Signal
The exploit unfolded in two clean transactions. Treasury tokens went out first, then liquidity positions were unwound. Both converted to USDT. The attacker didn't need to find a reentrancy bug or exploit a price oracle. They just voted themselves the money.
After extracting 4.85M USDT, the first exploiter swapped roughly 4.75 million into ETH, then distributed it across four wallets holding about 400 ETH each. A distribution wallet retained another 423 ETH. This is standard obfuscation, but not particularly sophisticated. The attacker is either confident law enforcement won't pursue this scale of theft, or they're planning more mixing later.
"Blockaid warned that the Ethereum attack was ongoing."
The timing matters here. Blockaid's alert came while the attack was active, meaning monitoring systems caught it in real time. But there's no mechanism in most governance protocols to halt a malicious proposal mid-execution. Once the votes are in and the timelock expires, the transaction executes. Doesn't matter if everyone watching knows it's a heist.
This raises three uncomfortable truths about DeFi governance:
- Token distribution determines security, not code audits
- Real-time threat detection is useless without real-time intervention mechanisms
- Most DAOs have no procedure for emergency governance override, even during active theft
The X100 protocol likely had concentrated token holdings, either from a botched launch, low participation, or tokens sitting idle in wallets that never voted. The attacker acquired or controlled enough tokens to pass a proposal, waited out the timelock if there was one, and executed. This is governance working exactly as designed. The design was just bad.
The Implication
If you're holding governance tokens in a small or mid-cap protocol, check the distribution. If the top 10 holders control more than 50% of voting power, you're one acquisition away from this exact scenario. Token-weighted voting without safeguards, timelocks long enough for community response, or emergency multisigs is a feature, not a bug, until someone uses it against you.
For builders: governance isn't about decentralization theater. It's about threat modeling. Ask who could buy enough tokens to pass a malicious proposal, and what stops them. If the answer is "well, nobody would do that," you're designing for a world that doesn't exist.