0x68f1c92568f1…68f1c928

ConfirmedSecurity538 vB141 sat/vB3 min decode

Initia Halts Network After Cloud Key Breach Moves $3.27 Million

Initia says a Nov. 9 cloud key breach let an attacker forge IBC withdrawals and move $3.27 million; $2.16 million sits frozen on the halted network with no restart date.

Initia Says Cloud Key Breach Moved $3.27 Million in Assets
WitnessInitia Says Cloud Key Breach Moved $3.27 Million in Assetsgeralt / pixabay

Outputs

  1. An attacker moved about $3.27 million in assets after a Nov. 9 cloud key breach on Initia.

  2. Initia and validators halted the network at 1:18 a.m. ET on Nov. 10, freezing about $2.16 million on-chain.

  3. A compromised Google Cloud Platform key enabled command injection exposing GitHub, cloud accounts and the Anvil rollup-hosting platform.

  4. Forged IBC withdrawals were validated from five rollups, releasing escrowed assets.

  5. This is Initia's second incident in under three weeks, after an Oct. 23 MoveVM bug allowed about $2.7 million to be bridged out.

Initia, the Cosmos-based layer-1 that hosts application rollups, says an attacker moved approximately $3.27 million in assets after breaching a Google Cloud Platform key, forcing a network halt that has left about $2.16 million of those funds frozen on-chain. The project has not announced a restart date.

The intrusion occurred on Nov. 9 through a command-injection attack on Initia's systems, according to the project's own account of the incident. The compromised cloud key exposed environment variables and opened a path into Initia's GitHub and cloud accounts, additional credentials, and Anvil, the company's rollup-hosting platform.

How the theft unfolded

With that access, the attacker validated forged Inter-Blockchain Communication (IBC) withdrawals from five rollups. Those forged messages released assets held in escrow on Initia's layer-1 network, the mechanism by which the chain backs value moving to and from its rollup ecosystem.

About $3.27 million moved to an attacker-controlled address. Initia and its validators halted the network at 1:18 a.m. ET on Nov. 10 (06:18 UTC) after detecting the unauthorized escrow transfers, trapping roughly $2.16 million of the drained assets on the stopped chain where they cannot be moved.

Before the halt took effect, Initia routed transfers through Noble totaling approximately $605,000 in USDC plus about $10,000 in other tokens. The updated loss figure of $3.27 million also includes assets that remain on the halted chain.

A second incident in three weeks

The breach is Initia's second security failure in under three weeks. On Oct. 23, an attacker exploited a MoveVM script-caching bug that bypassed security checks and bridged out approximately $2.7 million in assets.

Taken together, the two incidents put roughly $6 million in exposed value on the books in under a month — a material figure for a young network whose core value proposition to rollup builders is precisely the security of its escrow and IBC routing infrastructure.

What does this change for rollup operators and users?

For teams hosting rollups through Anvil, the incident reveals that the custody chain extends well beyond on-chain code. A single cloud credential, once exposed via command injection, was sufficient to reach the hosting platform and forge valid IBC withdrawal messages. The MoveVM bug of October broke a virtual machine check; this breach broke the operational perimeter around it. Neither failure required a consensus-level attack on Initia's validators.

For users, the immediate consequence is access: the network is halted, transfers are impossible, and roughly $2.16 million sits in limbo until restart. Initia says it is rebuilding affected infrastructure in an isolated environment and plans to restore the backing of affected assets in full, though it has published no timeline for either the rebuild or a chain restart.

The open question is sequencing. A restart before the rebuilt infrastructure and credential rotation are complete would risk a repeat drain; a prolonged halt compounds user and rollup-operator pressure. Validators, who executed the halt within hours of detection, will bear the restart decision. Until Initia publishes a restart date and a technical post-mortem, the frozen balance and the assets already moved remain the operative facts.

via tokenpost.com (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,512 articles