Binance said it helped prevent a governance attack aimed at an unnamed decentralized autonomous organization, or DAO, before the proposal could be executed. According to the exchange, the effort stopped access to roughly $1.2 million in treasury tokens.

The company said its monitoring team identified a malicious on-chain proposal with less than 48 hours remaining before execution, alerted the project involved, and worked with centralized exchanges that listed the token to close deposits while the threat was being addressed.

Threat detected before execution

Binance said the attack did not rely on a smart contract exploit, but on the governance process itself. The proposal was described as malicious and designed to influence treasury management through token-based voting.

After Binance raised the alarm, the project held a vote and rejected the proposal before it could take effect. Binance did not disclose the name of the DAO or the token involved in the incident.

How the response unfolded

The exchange said the response took place under significant time pressure because fewer than 48 hours remained before the proposal's execution window. Binance said it contacted the project directly and also coordinated with other centralized exchanges that listed the token so deposits could be suspended.

According to the company, those steps helped contain the immediate risk while the governance vote played out. Binance characterized the sequence as an example of cross-platform coordination to limit possible losses beyond a single exchange.

Binance frames case as ecosystem security issue

Binance Chief Security Officer Jimmy Su said the episode showed how security work can extend beyond a company's own platform. He said Binance's team and internal systems identified a threat that, according to the company, had not been flagged by any outside security provider, and then acted proactively to protect users across the broader ecosystem.

The company presented the case as evidence that exchange monitoring can play a role in detecting risks that emerge from governance design rather than from flaws in code execution.

Why governance design became the weak point

Binance said the conditions for the attack were created by governance rules that allowed on-chain proposals to be submitted with low barriers. It added that some systems may also lack adequate review periods, creating opportunities for a malicious actor to push treasury-related actions through token voting.

The case highlights a recurring problem in crypto governance: users and treasuries can be exposed even when no direct code exploit is involved. In this instance, the proposal was stopped before execution, but Binance said the episode showed how quickly governance weaknesses can become a practical security threat.

What is confirmed next

The confirmed outcome is that the proposal was voted down and the DAO's treasury tokens, valued by Binance at about $1.2 million, were not accessed through the attempted attack. Binance has not released additional identifying details about the project, and no further public information was provided in the report about the actor behind the proposal.

The exchange said it has expanded its monitoring, compliance, and recovery operations as part of broader efforts to deter and respond to similar threats. Based on the information disclosed, the immediate next confirmed step was the governance vote that blocked execution of the proposal.

Source: news.bitcoin.com