Security
17 Days After a Code Bug, a Cloud Key Cost Initia a Reported $3.27 Million
Initia says the October bug is not what failed this time. An attacker got in Monday through a compromised Google Cloud key and reached the platform that hosts its rollups. About $2.16 million of the reported loss is frozen.
Initia, the Cosmos SDK Layer 1 that halted itself on October 23 over a bug in its Move virtual machine, says it has been breached a second time. Per Cointelegraph, the attacker got in on Monday, November 9, Initia halted the chain on Tuesday, and the project announced the incident on Wednesday. The reported loss is about $3.27 million. About $2.16 million of the stolen assets is, in Cointelegraph’s words, “frozen on its halted network.”
This desk could not read Initia’s posts on X directly; the page returned an error when fetched. Everything below about what Initia said comes from Cointelegraph and FinanceFeeds, both of which link those posts, and it is marked as relayed.
The route, as relayed
Both outlets give the same chain of events. A command injection attack involving a compromised Google Cloud Platform key exposed environment variables. Those variables gave the attacker access to Initia’s GitHub and cloud accounts, and from there more credentials. The attacker used them to reach Anvil, a platform that hosts rollups, and validated fraudulent Inter-Blockchain Communication (IBC) withdrawals from five rollups. Those withdrawals released assets held in the network’s escrow accounts.
The attacker then sold assets on Initia’s decentralized exchange and withdrew 13,400 TIA, 8,000 USDC.inj and 597,000 Noble USDC, according to Cointelegraph and FinanceFeeds. Both say no INIT tokens were withdrawn.
Two incidents, 17 days apart, as reported
| Date | Entry point | Reported loss | State |
|---|---|---|---|
| Oct 23 | MoveVM script-cache flaw bypassed checks; unbacked balances bridged out | About $2.7M | Chain halted; see earlier report |
| Nov 9 | Compromised Google Cloud key, command injection, then rollup-hosting platform | About $3.27M | L1 halted Nov 10; about $2.16M frozen |
A different door
The October attack ran through the chain’s own execution layer. This one, per the reports, ran through the build and hosting side: a cloud credential, source-code and cloud accounts, and a rollup platform. FinanceFeeds argues the two share no technical overlap and reads that as gaps across several layers of the stack rather than one unpatched flaw. That is the outlet’s analysis, not Initia’s, and the desk offers it as an argument rather than a finding.
What the reports do establish is narrower. A virtual-machine fix does nothing about a credential the attacker already holds, and the second loss came 17 days after the first. They do not say how long the Google Cloud key was exposed, whether it had been rotated after October, or what “validated” meant for the five rollups: whether the attacker held validator-level keys, or the platform accepted its submissions on the strength of other credentials.
The figures do not line up
Most outlets print $3.27 million. A comparison by Newscord notes that some headlines use $615,000 instead, and that one outlet it reviewed called the final total unsettled. This desk did not read those pieces and cannot say what the $615,000 counts.
There is a second ambiguity. FinanceFeeds adds the October and November figures to roughly $5.97 million “including” the frozen $2.16 million. Adding a gross loss to a partly frozen one does not give a net loss, and none of the reports say whether $3.27 million is the amount taken or the amount that left the network. The frozen sum matters for users: Cointelegraph says Initia intends to restore the backing of affected assets, but no source gives terms, a date, or who is covered.
What is still open
No report says when the chain restarts. FinanceFeeds says Initia has not disclosed a timeline and has not said whether it plans an independent security review before restarting. Initia says recovery is ongoing with law enforcement and security partners and that it is rebuilding infrastructure. None of the reports this desk read link a post-mortem for either incident, and Initia’s October promise of one had no date.
The Take
A chain can be audited line by line and still be run from a small set of secrets. The October fix answered a code question; the November breach asked an operations one. Initia’s restart notice should say which credentials were rotated, what the rollup platform trusts, and who looked at that before the chain came back.