Initia’s MoveVM Exploit Left Its USDC Bridge Reserve With Just $63

Initia’s response to a MoveVM exploit has exposed the kind of crypto risk that a token balance alone cannot show: a bridge can display assets on one side while its redeemable reserve has nearly vanished on the other.

According to a detailed report from CryptoSlate, the incident drove the network’s USDC bridge reserve down to roughly $63 as users encountered failed withdrawals. That figure is the part investors will remember, but the mechanics behind it matter even more.

Initia first told users that its layer-1 network and associated rollups had been halted on October 23 after a security incident. The team said it was working with security firms, validators, and exchanges to determine the full scope of the damage.

As of Oct 23, 2026, 3:41:30 PM UTC, the Initia L1 and Rollups have been halted due to a security incident.

Our team is actively investigating the situation and working to establish the full scope of any impact with security teams, validators, and exchanges.

We will share…

— Initia 🪢 (@initia) October 23, 2026

A network halt is disruptive, but it also bought the project time to investigate a flaw that appears to have crossed the line from a software bug into a reserve problem.

Users do not experience that distinction as an academic debate. They experience it when a withdrawal fails.

In its follow-up, Initia said the attacker exploited a bug in MoveVM’s script-caching behavior. The project’s account said the flaw let malicious code bypass security checks, spoof the MoveVM state, and credit the attacker with unbacked WETH, iUSD, and USDC.

At 14:59 UTC on October 23rd, an attacker exploited a bug in Initia MoveVM’s script caching that allowed malicious code to bypass security checks. The attacker artificially spoofed the MoveVM state, thereby crediting themselves with unbacked WETH, iUSD, and USDC tokens without…

— Initia 🪢 (@initia) October 24, 2026

That explanation points to the central issue. The attacker was allegedly creating claims without matching reserves behind them.

Once those claims reached the bridge, the mismatch became a solvency and redemption problem.

Crypto users often focus on the number shown in a wallet or block explorer. Bridges add another layer: the asset represented on a destination chain must still be backed by something users can redeem.

If the backing pool is drained or contaminated by unbacked claims, a displayed token balance can look normal while its practical exit route breaks down.

That is why the reported $63 reserve is so alarming. It suggests the bridge’s remaining USDC liquidity had become effectively unusable for ordinary redemptions, even if balances elsewhere in the system continued to appear.

The episode is also a reminder that newer virtual-machine implementations and cross-chain systems combine several difficult security assumptions.

Code execution, state verification, token minting, and bridge accounting all have to agree. A failure in one layer can cascade quickly into the others.

The immediate questions are straightforward: how much value was ultimately extracted, which assets remain unbacked, how Initia plans to restore bridge solvency, and whether affected users will be made whole. The project also needs to explain the patch, the audit history around the caching behavior, and the conditions required before the network and withdrawals fully resume.

Until those answers arrive, users should treat official Initia updates as the primary operational source and avoid relying on screenshots or unofficial claims about restored withdrawals.

A restart by itself would not resolve the reserve gap. The important milestone is verified backing and dependable redemption.

For the wider market, the incident goes beyond another “bridge hack” headline. It is a vivid example of why reserve quality, minting controls, and withdrawal capacity deserve the same attention as price.

Join the conversation!

We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.