Skip to content

Invest1 publisher3 min readPublished

Cosmos Hub validators rewrite chain state to pull 1.23 million ATOM from Neutron's exploiter

Cosmos Hub validators moved 1,227,121 ATOM, about $2.1 million, from the Neutron exploiter's wallet at restart with no signature from its owner. Anyone treating a Hub balance as settled now relies on the validators as well as the key.

The Investor · Invest desk

Illustration accompanying Cosmos Hub validators rewrite chain state to pull 1.23 million ATOM from Neutron's exploiter

What happened

  • Neutron proposal 9, pitched as research into letting AI agents run a test network, passed on the expedited track with 81.88% of votes on Sept. 22.
  • The attacker swapped custom code into 10 of the 11 targeted Astroport and Drop contracts from 02:38 UTC and drained them in 24 minutes.
  • The ATOM taken at the restart now sits at cosmos1z8pq5c, an address no key has ever signed for, and no one has been named as controlling it.

Compiled by The InvestorSomething wrong?How this is made

Why it matters

  • exposure A coordinated validator restart can move a Hub balance without its key, so custody of ATOM on the Hub depends on validator consent as well as the private key.
  • precedent After the Cronos rollback and the TAC freeze in August, the Hub's transfer makes validator intervention the expected response to the next exploit that parks funds on these chains.
  • decision Someone now has to decide who receives the 1,227,121 ATOM, and getting it out of a keyless address would take another state-level action by the same validators.

Control of those contracts cost about $0.00064 per NTRN. According to on-chain analyst Rarma, one account voted yes while holding about 100 NTRN, then spent 20,199 USDC on 31.6 million more and staked them less than 12 minutes before voting ended [13]. Most of that purchase came out of Astroport pools the attacker drained soon after [14]. Rarma estimated Neutron's entire bonded stake at around $113,000, guarding contracts that held about $9.4 million [15]. On those figures, the contracts held roughly 83 times the value of the stake that governed them [2].

The Hub's answer was one write to its state. Validators halted at block 33,086,740 and, on resuming at block 33,086,741, executed the transfer directly with no signature from the wallet owner [3]. The chain logged it as a block event [2]. The block numbers run on consecutively, so the Hub did not rewind its history, as Cronos validators did after an estimated $75 million exploit at Tectonic in August [18]. The Hub team had flagged the change a day before [6] and says its own chain was never compromised [7]. The bill for that precision went to every other ATOM holder, or more exactly to anyone who needed to move ATOM during a freeze that ran 24 hours and 42 minutes [3].

The write also caught only what was in the wallet at 12:00 UTC. Seven minutes later [4], a THORChain vault sent 168,990 ATOM to the same wallet from an order that never fully executed [8]. A 500,000-ATOM send to Osmosis at 12:09 UTC bounced because the wallet held about a third of that [9]. At 17:54 UTC the owner bridged the 168,990 ATOM to an Osmosis address of the same key [10], five hours and 47 minutes after it landed [6]. The refund equals about 14% of what the validators moved, or roughly $290,000 at the ATOM price implied by the $2.1 million figure [5].

If the 1,227,121 ATOM ends up with Neutron's users through a published process, the Hub has a recovery tool with a narrow trigger: a traced exploit, one day's notice and one block. If the tokens stay at an address no one has been named as controlling [4], value has moved from the attacker to nobody. If the next use targets a balance with no exploit behind it, the exposure extends to every holder. I think investors should treat a Hub balance as final subject to a validator override that has now been used once, with warning, against funds traced to a theft. The strongest counter-case is the leak. The override needed a freeze of nearly a day, and it still missed a refund that landed seven minutes after the restart [3][4].

Cronos rolled back after Tectonic [18], and in the same month a bug in an EVM component used by multiple Cosmos chains forced TAC to freeze its network [19]. The Hub is the third chain since August to halt or rewrite state after an exploit or bug [8]. The expectation that validators will do this again is wrong if the next exploiter to park funds on the Hub is left alone. Neutron itself has produced no block since 07:43 UTC on Tuesday [17], and Rarma put only about $1.96 million of the take on live chains as of that day, with the rest immobilized [17].

What to watch

  • Whether the Hub team names a controller for cosmos1z8pq5c or sets out how the 1,227,121 ATOM would reach Neutron's users.
  • Whether Neutron, halted since 07:43 UTC Tuesday, restarts with the drained Astroport and Drop contracts restored or rewritten.
  • Whether anyone acts on the 168,990 ATOM the exploiter bridged to an Osmosis address of the same key.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories