MANTRA Halts Chain After EVM Exploit Hits Two Managed Wallets

MANTRA EVM exploit halts mainnet operations

MANTRA’s public status page lists a full outage for blockchain public endpoints, MANTRA Chain validators, its Migrate bridge operations and MANTRA-managed IBC relays. The project separately said that transactions, transfers and staking were unavailable while the chain was paused.

The network is an application-specific Layer 1 with both Cosmos and EVM interfaces. Its technical documentation identifies the production chain as mantra-1 and its EVM chain ID as 5888. That dual environment can support Ethereum-compatible applications, but the incident places the EVM module at the center of the remediation.

The team said the vulnerability used in the exploit was in that EVM module and that v8.4.0 includes supplemental hardening. It also said the upgrade has no state migration or module changes, which describes the upgrade mechanics but does not establish the extent of the attacker activity before the halt.

The project took a full state snapshot before pausing block production. Its subsequent update said the incident affected two MANTRA-managed wallets, while its loss-impact check found no indication that user, exchange or partner funds had been affected. MANTRA had not published wallet addresses, token amounts, transaction hashes or a third-party forensic estimate at the time of publication.

That means the most supportable financial figure is currently not a theft total. It is the confirmed scope: two company-managed wallets and no reported third-party impact. The claim should be read as a preliminary project disclosure, rather than as an independently audited final accounting.

Patched v8.4.0 still needs validator coordination

The technical work does not itself restore a proof-of-stake chain. MANTRA said its v8.4.0 pre-release had been validated through repeated end-to-end upgrade rehearsals in an internal environment replicating mainnet state. It then said it would coordinate the broader active validator set for one upgrade rather than restart on a partial set.

Its status page says MANTRA-operated validators will upgrade first, followed by mainnet validator partners and then standard node operators, RPC providers and archive-node operators. The project told validators to keep mainnet nodes offline until an official coordinated restart signal, and said it would publish that window once it had sufficient validator coverage.

This leaves several practical limits in place. Users cannot assume an endpoint returning data means transfers are settled, and exchange deposit or withdrawal availability depends on each platform’s own controls as well as the chain restart. The status page also says managed bridge and IBC-relay operations are affected, so cross-chain routes need separate confirmation after mainnet resumes.

The situation differs from a routine software upgrade because MANTRA explicitly ties v8.4.0 to a security exploit. But it also differs from an established mass-loss event. On August 21, the available primary disclosure did not report customer theft, a loss amount or an affected-wallet count beyond the two MANTRA-managed addresses.

OM’s record-low area revives a difficult history

The outage arrived while OM was trading near record-low territory, which amplified the attention around a chain that already faced a major confidence shock. In April 2025, OM collapsed from roughly $6.30 to below $0.50 during a broader liquidity episode, a separate event covered in our report on MANTRA’s earlier crash.

The current incident should not be used to explain that old sell-off, and the price decline before the halt does not prove that the exploit caused it. What is clear is that a fresh security interruption now puts a network built around tokenized assets under a more demanding operational spotlight. That comes as tokenized real-world-asset deposits have continued to grow across DeFi, as our recent RWA market coverage found.

For holders and users, the first checkpoints are operational rather than directional: an official restart notice, confirmed block production, restored RPC and bridge services, and the project’s promised detailed post-mortem. A disclosure of the two managed-wallet addresses and any associated transfers would also allow outside researchers to assess the loss-impact claim against on-chain evidence.

Broader crypto sentiment was firm despite the isolated outage. Alternative.me’s Crypto Fear and Greed Index read 72, or Greed, in the August 21 reading.

MANTRA’s latest update keeps the network in an identified-incident state, not a resolved one. Until block production resumes and the post-mortem is published, the strongest confirmed facts are the halt, the patched release, the two company-managed wallets and the absence of reported third-party fund impact.