NewsCryptoInitia Cloud Breach Enables Forged IBC Withdrawals Worth $3.27 Million Across Five Rollups

Initia Cloud Breach Enables Forged IBC Withdrawals Worth $3.27 Million Across Five Rollups

Author: Crypto Ninjas·

Key Takeaways

  • •A compromised GCP provisioning key enabled the attacker to seize Initia's private nodes through command injection on Nov. 9 and escalate into GitHub, GCP, and the Anvil rollup hosting platform.
  • •Forged IBC withdrawals validated across five rollups unlocked roughly $3.27 million from Initia's Layer 1 IBC escrow accounts, of which about $2.16 million remains trapped on the paused network.
  • •The attacker sold stolen assets on Initia's DEX and withdrew 13,400 TIA, 8,000 USDC.inj, and 597,000 Noble USDC before outbound IBC rate limits stopped further transfers, and no INIT was taken.
  • •This is Initia's second major breach in three weeks, following an Oct. 23 MoveVM script cache exploit that cost about $2.7 million, bringing combined losses to just under $6 million.
  • •Initia intends to fully restore the backing of affected assets and is rebuilding its infrastructure from scratch in an isolated environment with least-privilege controls, a process expected to take longer than a routine network restart.
Initia Cloud Breach Enables Forged IBC Withdrawals Worth $3.27 Million Across Five Rollups

Initia has disclosed new details about a breach of its cloud credentials that gave an attacker access to the infrastructure of rollups built on its Layer 1, allowing fraudulent Inter-Blockchain Communication (IBC) withdrawals to be validated from five rollups. Approximately $3.27 million in assets were moved to the attacker's Initia L1 address, of which around $2.16 million remains stuck on the network's paused Layer 1 and cannot currently be moved.

The Nov. 9 incident is the second major security breach Initia has suffered in three weeks, following an unrelated exploitation in October. According to the team, the backing of all affected assets will be restored in full.

Compromised GCP Key Opened the Door

Based on Initia's investigation so far, the compromise began on Nov. 9, when the attacker used an Initia-provisioned key on Google Cloud Platform (GCP) to take control of private nodes through a command injection attack. The intrusion exposed environment variables, which in turn allowed the attacker to access Initia's GitHub and GCP accounts and obtain further credentials.

Armed with those credentials, the attacker gained access to Anvil, the hosting platform used by rollups on Initia. Through Anvil, the attacker was able to validate forged IBC withdrawals from five rollups, unlocking assets held by the Initia Layer 1's IBC escrow accounts. In effect, the fraudulent withdrawals were double-validated across the five rollups before the assets were untethered on Initia's Layer 1, and the breach came to light only once the attacker entered the rollup and IBC systems. The access chain — from a single provisioning key to GitHub and GCP accounts, then on to Anvil and the validation of cross-chain withdrawals — shows how an off-chain cloud compromise can translate directly into on-chain losses when one set of credentials spans the systems that validate IBC transfers.

IBC, the Inter-Blockchain Communication protocol, is the cross-chain messaging standard used across the Cosmos ecosystem. On Initia, assets held in the Layer 1's IBC escrow accounts back the funds bridged to connected rollups.

Initia detailed the incident in a statement posted on X on Nov. 10, one day after the intrusion:

"Based on our investigation so far, on November 9th an attacker gained unauthorized access to Initia's infrastructure through a command injection attack with a compromised GCP key used for provisioning private nodes. This exposed environment variables, which allowed the attacker to access our GitHub and GCP accounts and obtain further credentials.

With these credentials the attacker gained access to Anvil, the hosting platform used by rollups on Initia. Through this the attacker was able to validate forged IBC withdrawals from five rollups, unlocking assets held by the Initia L1's IBC escrow accounts.

Around $3.27m of assets were moved to the attacker's Initia L1 address with $2.16m of the stolen funds remaining on the paused L1 where they cannot be moved. The attacker sold stolen assets on the Initia DEX and then withdrew 13.4k TIA, 8k USDC.inj, and 597k Noble USDC reaching Initia's outbound IBC rate limits. No INIT was withdrawn from Initia by the attacker.

We intend to restore the backing of affected assets in full. We are finalizing the plan and will share the details once it is confirmed.

As a precaution, we are rebuilding the affected infrastructure from scratch in an isolated environment, enforcing least-privilege access controls, and hardening security at every layer of the stack from cloud infrastructure to onchain IBC validation. Given the above, we expect this process to be longer than a routine network restart. We will share timelines as they become available.

All announcements will be made through Initia's official channels. Thank you for your patience."

— Initia 🪢 @initia November 10, 2026

Forged IBC Withdrawals Released $3.27M

Nearly $3.27 million worth of assets were sent to the attacker's Layer 1 address, according to figures released by Initia. The attacker then sold some of the stolen assets on Initia's decentralized exchange and withdrew 13,400 TIA, 8,000 USDC.inj, and 597,000 Noble USDC before hitting the network's outbound IBC rate limits, which capped the amount that could be moved out of the network through IBC.

Initia confirmed that no INIT tokens were withdrawn by the attacker. More than $2.16 million in assets remain on Layer 1 and are not transferable at this time, and the remaining stolen funds cannot leave the network while the Layer 1 stays paused.

Initia Rebuilds Infrastructure Ahead of Network Restart

Initia said it intends to restore the backing of all impacted assets in full and is finalizing a recovery plan, the details of which will be announced once confirmed.

As a precaution, the team is rebuilding the affected infrastructure from scratch in an isolated environment rather than performing a routine restart. It is also enforcing least-privilege access controls and hardening security at every layer of the stack, from cloud infrastructure through on-chain IBC validation. For that reason, Initia expects the process to take longer than an ordinary network restart, and the network may remain offline for an extended period. Timelines will be shared as they become available, and all announcements will be made through Initia's official channels.

The company added that asset recovery efforts are continuing alongside law enforcement and security partners, and that it will continue to publish updates as the recovery progresses.

Second Major Breach in Three Weeks

The cloud breach follows an exploit on Oct. 23 in which attackers defrauded approximately $2.7 million from the company using a MoveVM script cache vulnerability. That earlier incident enabled credentials to be created and cross-chain withdrawals to be made without authorization prior to the network being paused.

The two attacks were distinct in nature: the October exploit was based on migration issues involving the blockchain's execution logic, whereas the current breach was an off-chain compromise of cloud infrastructure that came to light only through the attacker's entry into the rollup and IBC systems. Taken together, the two incidents account for just under $6 million in losses within a three-week span.

Source: CryptoNinjas