Binance's security team caught a malicious DAO governance proposal aimed at an unnamed project, then moved fast to shut down deposit channels and rally other exchanges. The coordinated effort blocked a vote that would have let attackers walk off with roughly $1.2 million in treasury tokens. The whole thing was over in less than 48 hours, with Binance sharing the details on August 18.
How the threat surfaced
The proposal was designed to exploit the project's voting mechanism, a common weakness in decentralized governance. Binance's security team spotted it before it could do real damage. They didn't just flag it internally — they contacted the project directly and warned them about what was coming.
That warning set off a chain reaction. Binance coordinated with other exchanges to close deposits for the affected tokens, cutting off the flow of funds that could have been used to sway the vote. It was a quiet, behind-the-scenes move, but it mattered.
A vote that saved the treasury
The critical moment came when the project's community voted. That vote blocked access to the $1.2 million sitting in the treasury. The attack never got the funds. Binance's involvement didn't stop at detection — the exchange's warnings gave the project the time it needed to organize a response.
What made this work was the speed. Under 48 hours from detection to resolution. That's tight for any security incident, let alone one involving multiple exchanges and a governance vote.
What Binance shared
Binance didn't name the project or the exchanges that helped. The details released on August 18 focus on the sequence of events: the detection, the warning, the coordinated deposit closures, and the vote that stopped the attack. No names, no dollar figures beyond the $1.2 million at risk.
The takeaway is clear. Malicious governance proposals are a real threat, and they're not always caught by the projects themselves. Sometimes it takes an exchange like Binance to spot the problem and pull together a response.
What's still unknown is whether the attackers will try again, or if the unnamed project will tighten its governance rules. Binance hasn't said if it plans to share more details, but the incident is a reminder that DAO security isn't just about code — it's about coordination.
