Initia Halts L1 After MoveVM Script-Cache Flaw Enables $2.7M Token Mint

Root Cause

Initia's Layer-1 runs an EVM-Cosmos hybrid architecture that embeds MoveVM (Move language execution) alongside the Cosmos SDK. A script-caching flaw in the MoveVM component allowed an attacker to poison the module cache and forge credited balances of bridged assets (WETH, iUSD, USDC) without making the corresponding deposits.

Move's execution model loads compiled modules into a per-session cache for performance. The bug permitted a crafted sequence of Move script calls to leave stale, attacker-controlled state in that cache. Subsequent calls consulted the poisoned cache rather than the canonical on-chain state, causing the VM to credit the attacker with assets they never deposited.

// Conceptual illustration of the cache-poisoning path
script {
    use std::signer;
    use initia_std::coin;

    fun exploit_entry(account: &signer) {
        // 1. Call a module that populates the cache with a crafted resource slot
        malicious_module::seed_cache(account);
        // 2. The caching layer returns the seeded (fake) balance on subsequent reads
        // 3. Bridge module reads cached balance — not on-chain state — and authorises withdrawal
        bridge::withdraw(account, fake_amount);
    }
}

Note: Initia's full post-mortem was not yet published at time of writing; the above is a conceptual illustration derived from public disclosures.

Attack Steps

Impact

• ~$2.7M confirmed drained (1,135.52 ETH equivalent at time of exploit).
• Nominal token creation reached ~$7.48M at face value, but most consisted of synthetic iUSD that could not be redeemed.
• No native INIT tokens were minted; total INIT supply unaffected.
• Initia L1 and all rollups paused at 11:41 AM ET, October 23; no restart date confirmed as of publication.
• Agora (AUSD issuer) confirmed AUSD proper is fully backed; the bridged tokens were representations, not canonical AUSD.

Lessons for Auditors

1. Cross-VM state consistency. When a blockchain embeds multiple execution environments (EVM + MoveVM, or MoveVM + CosmWasm), each VM's internal cache must be treated as untrusted for cross-module calls. Canonical on-chain storage should always be the authoritative source for balance and permissions queries.
2. Cache invalidation at bridge boundaries. Any bridge or withdrawal operation that consults in-memory module state rather than committed chain state is a critical attack surface. Bridge modules must read from finalised, committed storage.
3. Auditing novel VM integrations. Bespoke MoveVM deployments that diverge from the reference implementation (Aptos, Sui) may introduce unique caching semantics. Auditors should trace the module-loading and caching lifecycle explicitly.
4. Post-halt fund movement. The attacker moved funds five seconds after the halt, indicating pre-arranged bridge transactions. Emergency halt procedures should include upstream bridge pause co-ordination.
5. Synthetic vs. canonical asset accounting. Bridge contracts should distinguish between canonical assets and synthetic representations; excess issuance of the latter should trigger circuit-breakers.