Skip to content

News · Security

Cosmos Hub restarted and moved 1,227,121 ATOM. That is a validator choice, not finality.

A Neutron governance proposal handed an attacker admin rights. Hub validators halted, then wrote the remaining ATOM to a recovery multisig. The attacker did not sign.

ECGBy EasyCryptoGuides · Editor · Published · Updated · 3 min read

Rows of illuminated servers in a data centre
Photo on Unsplash
In this article

On 22 September 2026 an attacker used Neutron governance to take admin control of contracts on that chain, drained protocol funds, and moved a portion — held in ATOM — back to the Cosmos Hub over IBC in order to sell it. Hub validators halted the chain. On 23 September they restarted on Gaia v28.3.0. The patched binary applied a one-time state change at the halted height, 33,086,741, before any further transactions. It moved 1,227,121 ATOM, the full balance still at the attacker’s address, to a recovery multisig. The Hub’s weekly update the next day is explicit: the binary touched exactly one account. No other balances, delegations, or user funds were rewritten. The attacker did not sign the transfer.

The chain resumed producing blocks at 12:00 UTC on 23 September. The Hub says its own chain was not breached. Neutron was. A restart that edits one balance is still a human override. It is the same family as Cronos rolling back Tectonic: a sufficient set of validators chose a history. It is not Bitcoin finality, and it is not Ethereum.

What happened

Neutron proposal 9 was filed on 19 September on an expedited track, pitched as research into letting AI agents run a test network. It passed. Public reconstructions say the votes cost on the order of $20,199, much of it from pools the attacker drained afterwards, and that the proposal made the attacker admin of Astroport and Drop contracts — eight Astroport, two Drop, with the Astroport treasury left. Custom code went in and the contracts were emptied in minutes. That is a governance design: if bonded stake is cheap relative to the contracts it can admin, the vote is the bug. We will not write how to buy a proposal.

Once ATOM was on the Hub and moving toward cross-chain liquidity, validators stopped the chain at height 33,086,740. The recovery address is a 4-of-6 multisig. The Hub named the signers as validators at Nansen, Keplr, Enigma, Silknodes, Kiln, and Polkachu. Any four must sign before those coins move again. The attacker’s address is a different account. Readers do not need to paste either bech32 string into a wallet. Phishing will.

Do not mash this into Nomic’s nBTC vouchers or Liquid’s unbacked L-BTC. Those were bridges printing paper bitcoin. This was a Cosmos app chain whose own governance handed over admin keys, plus a hub that can halt and patch state. A bridge is extra software, not a tunnel. A governance proposal is also software, with a shorter comment period than a statute.

Why it matters

If you held ATOM on the Hub and you were not that address, the Hub says your balance was not the account they edited. If you held funds in the Astroport or Drop contracts on Neutron, you had a claim on those contracts, then on whatever the attacker had not yet sold, then on a multisig run by six validator businesses. That is not a wallet you hold. If you staked ATOM, you were part of the set that socialised this decision. Delegators did not each sign the halt. Their validators did.

“Code is law” does not survive a coordinated upgrade. Cronos discarded about two hours for everyone on that chain. Here the edit was narrower — one account — and still a choice. Both are operations meetings. See DeFi is software with rules you cannot call support about. The support, when it comes, is the validator set.

What happens next

As of the 24 September Hub note, the ATOM sat on the recovery multisig. Sending it back to Neutron, and from there to the contracts people actually used, required further governance. Exchanges re-enabled Hub deposits and withdrawals after the restart. That is a company switch. It is not restitution.

Update, 16 October. Cosmos Hub Proposal 1058 passed on 12 October, with about 60 percent of bonded ATOM voting and 99.7 percent of non-abstaining votes in favour. On 14 October the Hub multisig sent 1,227,121.22 ATOM over IBC to a Neutron recovery multisig. The Hub called its part closed. Neutron proposal 10, to return recovered funds to the original contracts, was still in the voting period through 22 October. Watch the Hub forum and Neutron’s own proposal, not a claim site. A multisig transfer is not the same as a user withdrawal.

Not a recommendation to stake, unstake, bridge, buy, or sell ATOM. Not an instruction to sign a “recovery” transaction a stranger sends you.

Topics

This article is for information only and is not financial advice. Cryptoassets are volatile and you can lose money. See our disclaimer.

Comments

Keep it civil. First comments wait for an editor. This is not financial advice, and we remove spam or “DM me for signals” posts.

No comments yet. Be the first — keep it civil, and skip the tips.

Sign in to comment. Reading never requires an account.

Back to top

Continue reading

Stay a little clearer on crypto

Guides, reviews, and the news that actually matters. Unsubscribe anytime.

By subscribing you agree to our privacy policy.

More news

View all