Secondary reports say Initia halted its L1 and rollups on 2026-10-23 after a security incident involving unauthorized asset issuance and transfers to Ethereum. Coverage places the amount involved in a roughly $2.6 million to $2.7 million range, while a separate reported statement from Agora says it had no smart contracts deployed on Initia, leaving the status of the AUSD mentioned in the incident unresolved.

What happened and why Initia halted the network

NewsCord reported that Initia suspended both its layer-1 chain and rollups on 2026-10-23 at 15:41:30 UTC after a security incident. That makes the current event a broad containment step rather than a single-app outage, because the reported halt covered the base blockchain and dependent rollup activity.

FinanceFeeds and the supplied report describe the trigger as unauthorized asset issuance followed by transfers to Ethereum through a cross-chain route. The reported value is not settled in one final number: the supplied report and FinanceFeeds use about $2.7 million, while NewsCord’s headline uses about $2.6 million. The clearest supported reading is that secondary coverage places the incident in that approximate range, not that a final official loss total has been established.

Which assets were reportedly moved, and why AUSD is disputed

Within that reported exploit path, FinanceFeeds and the supplied report describe roughly 1.4 million AUSD, 105 ETH, and 1.08 million USDC moving to Ethereum after alleged unauthorized minting. The supplied report also says 2 million AUSD were issued without collateral before part of that amount was bridged out.

That does not settle what the Initia-side AUSD actually was. NewsCord reported that Agora said it had no smart contracts deployed on Initia, and the supplied report similarly attributes to Agora the position that AUSD did not exist on Initia. So the incident can be described as involving an asset labeled AUSD in secondary coverage, but that label should not be treated as proof that canonical Agora-issued AUSD was natively deployed on Initia.

NewsCord also reported a preliminary co-founder view that the suspected bug was a previously unknown issue in Initia’s MoveVM implementation and did not apply to native INIT tokens. That is useful context for readers because it separates the reported unauthorized issuance from an unsupported claim that native INIT itself was minted through the incident. The technical root cause, however, remains at the level of secondary reporting rather than a published postmortem.

What the current status says about recovery

The current supported status is still the investigation phase. NewsCord says Initia was working with security researchers, validators, and exchanges to determine the full impact, which fits the network-wide halt described in the incident coverage.

No inspected material provides a restart time, rollback decision, recovery block height, or formal reopening criteria for normal operations. That means the practical takeaway is narrow but important: Initia was reportedly still in containment and assessment, and the next meaningful recovery milestone would be an official incident update that explains the exploit path, confirms affected assets, and sets out how the chain and rollups would resume.