On 20 August 2026, the MANTRA blockchain stopped producing blocks, and the project froze all network activity after detecting an exploit. On its official status page, MANTRA told users: “There has been an incident on MANTRA Chain. We have halted the chain.” The native OM token fell about 18 percent to a record low near $0.0041 as word of the halt spread.
In two statements on its official X account, MANTRA first confirmed that it had frozen all endpoints and transactions, then, several hours later, narrowed the scope of the incident. The team said the exploit was “isolated to the Cosmos EVM module of MANTRA Chain and affected two wallet addresses before we achieved containment,” and that “no user funds were exploited.” In an update on its official status page, MANTRA said both affected addresses were wallets it manages itself.
What broke on MANTRA
According to MANTRA, the exploit did not stem from a flaw unique to its own application layer. In its statements, the team located the problem in the Cosmos EVM module, a component that MANTRA Chain shares with the broader Cosmos ecosystem rather than something it built alone. MANTRA says it has completed a root-cause analysis of the exploit and addressed the underlying issue in a patched build.
At the time of writing, MANTRA had not published a detailed technical post-mortem, so the precise mechanism and any external advisory reference remain unconfirmed. Readers should treat the company’s account of where the fault lies as its own characterisation until an independent review lands.
What was affected and unaffected across MANTRA?
MANTRA's status page states that it has completed a root-cause analysis of the exploit, that the incident was confined to the EVM module, and that “no third-party user, exchange, or partner funds were directly impacted.” The team has staged a patched build, v8.4.0, and says dry-run testing was successful. Restarting the chain is pending a coordinated validator upgrade, with MANTRA-operated validators upgrading first before the wider validator set follows.
One thing MANTRA has not done is put a number on the incident. It has disclosed neither a stolen amount nor a loss figure, and its public messaging emphasises containment rather than quantifying impact. Readers should therefore treat any specific dollar figure circulating elsewhere as unconfirmed until MANTRA or on-chain analysis substantiates it.
Compliance and risk teams to take note
For regulated venues and institutions weighing exposure to newer chains, the episode is a compact case study in three risks that sit outside the price chart. The first is shared-dependency risk at the protocol layer: if a fault sits in common infrastructure rather than a single project’s code, it can halt a network regardless of how sound that project’s own work is, and potentially affect more than one chain. The second is incident-response governance: how quickly a team detects, contains, communicates and patches, and whether it can coordinate a validator set to restart safely, is now a material part of counterparty due diligence. The third is disclosure discipline: MANTRA’s decision to halt first and explain in stages kept the network from bleeding while it investigated.
A halted chain that protects user funds is a very different outcome from a drained one, and MANTRA’s framing leans firmly on that distinction.
