Cosmos Hub resumed block production on Sept. 23 after validators coordinated a software patch that transferred 1,227,121 ATOM from an attacker-controlled address into a community-controlled multisignature wallet, ending a roughly 25-hour halt triggered by an earlier governance attack on Neutron.
The chain had stopped at block height 33,086,740 after more than one-third of Cosmos Hub’s validator voting power went offline. Under the Hub’s CometBFT consensus system, more than two-thirds of voting power must participate to commit new blocks. Once the offline share crossed one-third, the network could no longer finalize transactions, leaving ATOM transfers and other on-chain activity pending.
Validators restarted the network at 12:00 UTC on Sept. 23 after more than 67% of voting power had installed Gaia v28.3.0, the emergency patch prepared for the recovery. Block production returned about six minutes later, and the one-time state modification was executed in block 33,086,741.
The intervention moved the remaining 1,227,121 ATOM from the address linked to the attacker into a 4-of-6 multisignature wallet. The six entities named for the wallet were Nansen, Keplr, Enigma, Silknodes, Kiln and Polkachu.
A governance attack on Neutron triggered the response
The chain halt followed an attack on Neutron, a Cosmos ecosystem network, where a proposal called “AIATO: AI Agent Takeover” passed through governance. The proposal was used to invoke privileged wasmd commands, altering contract administrator permissions for applications including Astroport and Drop.
Smart-contract administrator rights can allow an authorized address to upgrade a contract, change its configuration or redirect control over associated functions. In this case, the permissions were reportedly switched to addresses controlled by the attacker, allowing the incident to spread beyond a single governance vote.
Before Neutron ceased operating, the attacker moved assets through several networks. About 1.7 million ATOM was bridged into Cosmos Hub and began moving through cross-chain liquidity routes for swaps, according to the incident account circulated by Hub validators.
A subset of Cosmos Hub validators then shut down their nodes to limit additional movement of the bridged ATOM. By about 19:18 SGT on Sept. 22, the inactive validators represented more than one-third of the chain’s voting power, placing the Hub into a deliberate liveness failure: the network remained secure against blocks being finalized without sufficient validator agreement, but it could not process any new blocks.
That decision created a difficult trade-off. Halting validator participation prevented ordinary transaction processing, but it also gave the network time to develop a coordinated response before more of the assets could move through external liquidity pools.
Emergency patch changed the chain state
About four hours after block production stopped, validators began circulating a recovery plan built around a targeted state change at the stalled block height. Gaia v28.3.0 was designed to execute that change once, then allow the Hub to return to normal consensus operations.
The patch did not establish an ongoing mechanism for redirecting balances. Its stated purpose was limited to the recovery height and the specified attacker-linked address. After the transfer at block 33,086,741, Cosmos Hub resumed regular block production and pending transfers could begin confirming again.
The use of a coordinated software release to alter a balance places the event among the more consequential crisis interventions in public blockchain history. Such actions depend on validator coordination rather than a unilateral change by a foundation or development team, but they also show that token balances can become subject to emergency collective decisions when enough validator voting power adopts altered software.
The incident differs from a routine outage because it combined two separate failures: an attacker’s use of governance and contract-administration controls on Neutron, followed by a Cosmos Hub response that intentionally paused transaction settlement while validators prepared a recovery patch.
Exposure extended beyond the recovered ATOM
Security groups involved in tracking the incident put total financial exposure across the affected applications at about $9.3 million. The provided incident figures indicate that roughly 500,000 bridged tokens could no longer be recovered after being traded through external market pools.
Another 168,991 tokens reportedly reached a separate chain after a partial trade returned funds to the malicious wallet. Those movements illustrate a recurring problem in cross-chain incidents: recovery options narrow sharply once assets have been exchanged, bridged again or dispersed among liquidity pools outside the chain coordinating the response.
A subsequent on-chain proposal seeking to refund the attacker was rejected by network voters, with 69.3 million veto votes recorded against it. The result reinforced the community’s opposition to compensating the address associated with the exploit, while leaving the multisignature wallet responsible for custody of the recovered ATOM.
Fast governance votes face renewed scrutiny
The attacker reportedly spent 20,199 stablecoins to acquire enough voting weight shortly before the fast governance poll closed. The episode has put renewed focus on expedited voting periods, especially where a temporary token purchase can carry enough weight to approve operationally sensitive proposals.
Governance systems often control parameters, treasury decisions and software upgrades. Where they can also activate privileged contract commands or affect administrator permissions, governance proposals effectively become part of a network’s security perimeter.
Cosmos Hub’s halt also demonstrates the practical limits of Byzantine fault-tolerant consensus. CometBFT’s two-thirds threshold prevented active validators from simply continuing without the offline minority, but that same safeguard enabled a coordinated group representing more than one-third of voting power to stop the chain. In this case, validators used that leverage to contain assets linked to an attack, then restarted after agreeing on a narrowly scoped recovery change.
Want deeper context on Cosmos and ATOM? Explore our guide What is Cosmos (ATOM) to understand the network’s design.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
