MANTRA Halts Unbonding for 7 Days; Token Falls 7.3%

MANTRA Halts Unbonding for 7 Days; Token Falls 7.3%


MANTRA has imposed a seven-day freeze on unbonding transactions after attackers exploited a private-key exposure affecting some Keplr wallets created through Google or Apple logins. The team said the attackers first drained liquid MANTRA tokens from compromised wallets before initiating unbonding requests against victims’ staked holdings without their consent.

In a November 13 update, MANTRA said the pause was intended to prevent further losses linked to the wider Web3Auth security incident. The team said it would review the restriction after seven days but reserved the right to extend it if necessary.

Web3Auth breach exposes systemic risk of shared authentication services across multiple blockchain ecosystems.

MANTRA’s freeze highlights how third‑party wallet compromises can disrupt staking operations and market confidence.

Loss estimates revised to $1.82 million, underscoring challenges in tracking cross‑chain thefts and recovery efforts.

Market Reaction

The announcement came as MANTRA’s token traded around $0.002677, down approximately 7.3% over 24 hours, with a market capitalization near $18.2 million, according to CoinGecko data at 12:33 UTC on November 13. The price movement coincided with the security update, although the available information does not establish that the freeze or exploit alone caused the decline.

Source: MANTRA 24-Hr Price Chart, 12:33 UTC on November 13, 2026, CoinGecko

MANTRA Freezes New Unbonding Requests

The freeze applies to new unbonding transactions, but it does not automatically stop withdrawals that were already underway when the restriction took effect.

That distinction matters because MANTRA’s normal unbonding period is eight days. Users whose staked tokens have already entered that process may still face an approaching unlock date. MANTRA warned that affected stakers must redelegate before the existing unbonding period finishes to prevent attackers from claiming the tokens once they become transferable.

According to the team, redelegating the tokens places them back under the network’s staking restrictions while the broader freeze remains active. Users should check the latest instructions through MANTRA’s official channels before taking action, particularly if their staking status or wallet exposure is unclear.

MANTRA also said it had frozen several wallets associated with the attackers through Governance Proposal No. 41. The team is coordinating with Web3Auth and Keplr on the response and recovery process.

Web3Auth Breach Reaches Keplr Users

The incident traces back to a security issue in Web3Auth’s infrastructure, which provides the embedded-wallet technology behind Keplr’s Google and Apple social-login option.

On November 7, Keplr warned that it had received reports of unauthorized transactions involving accounts created through those login methods. The wallet provider said users who created wallets using a recovery phrase or hardware wallet were not affected by the issue, based on its initial assessment.

Keplr paused Google and Apple logins while investigating and advised potentially affected users not to send additional funds to those accounts. It also cautioned users against unsolicited recovery messages and links.

Web3Auth, which is part of Consensys and is now marketed as MetaMask Embedded Wallets, separately said it had temporarily paused its embedded-wallet service. The company reported no evidence that MetaMask users were affected.

Keplr co-founder Josh Lee said the incident did not originate in Keplr’s code but in the infrastructure of the provider it uses. That distinction places the reported compromise in a shared wallet-service dependency rather than identifying a vulnerability in MANTRA Chain itself.

Updated Analysis Puts Confirmed Theft at $1.82 Million

The total losses from the Web3Auth incident have been difficult to establish because attacker transactions overlapped with a recovery operation carried out by Web3Auth.

An updated Bitquery investigation, covering activity through November 12, estimated that attackers took at least $1.82 million from affected wallets. The analysis identified 7,842 Cosmos wallets that lost at least $1, alongside affected Ethereum wallets and Hyperliquid accounts. Bitquery said at least $1.01 million had been taken before Web3Auth began its first recovery sweep.

The revised estimate is materially different from an earlier figure of roughly $6 million that was attributed to attacker activity. Bitquery later clarified that the larger amount included transfers into Web3Auth recovery addresses. The company had moved funds from vulnerable wallets into addresses it controlled to protect them from further theft.

Web3Auth said those recovery transfers were part of its mitigation effort and that the funds were safe. The company has not yet provided a complete public accounting of the amount stolen versus the amount recovered, or a full process for returning recovered assets to users.

MANTRA has not disclosed how much its own users lost in the incident.

Separate From MANTRA’s August Chain Exploit

The November wallet incident is distinct from a separate exploit that affected MANTRA Chain in August.

In its August 28 post-mortem, MANTRA said an attacker exploited an unsigned-integer underflow vulnerability in the upstream Cosmos EVM module, moving approximately 720.9 million MANTRA from two addresses that had not authorized the transactions. The chain halted for more than 30 hours before resuming on a patched software release.

MANTRA said the August vulnerability was in a shared software dependency, not in its own chain-specific code. The post-mortem also acknowledged monitoring gaps that delayed detection of the first unauthorized transfer.

The two incidents involve different attack paths. The August event exploited a flaw in the chain’s balance-accounting infrastructure, while the November episode involves exposed private keys associated with a third-party wallet authentication service.

The project has also faced a major token-market collapse before. Its former OM token lost more than 90% of its value in April 2025, an event that MANTRA and market participants discussed separately from the later security incidents. The Crypto Times previously covered the token collapse and the project’s subsequent restructuring.

What Affected Stakers Need to Know

The immediate concern for affected MANTRA holders is whether their wallets were created through Keplr’s Google or Apple login and whether any staked tokens are already in the unbonding process.

The seven-day freeze does not mean all existing unbonding requests have been cancelled. Users with tokens approaching the end of the eight-day withdrawal period should follow MANTRA’s verified instructions and check their staking status through trusted interfaces.

The incident also highlights the risks of relying on shared authentication infrastructure for wallet access. A compromise at a third-party provider can expose accounts across multiple blockchain networks, even when the affected chains and wallet applications have not themselves been breached.

For now, MANTRA’s freeze is a containment measure rather than a resolution of the wider Web3Auth incident. The amount stolen from its users, the final recovery total and the timeline for restoring normal unbonding activity remain unclear.

Also Read: Unocoin Says BitGo Multisig Backup Was Likely Exploited Despite Account Freeze


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *