MANTRA Suspends Unstaking for Seven Days After Private Key Leak

By Daniel Okafor

MANTRA, an RWA blockchain project, suspended new unstaking requests for seven days after a wallet private-key leak involving Web3Auth and Keplr wallets, according to Odaily’s November 13 report on MANTRA’s disclosure.

MANTRA said it had found signs that hackers “not only stole liquid assets from users’ wallets following the private key leak involving Web3Auth and Keplr wallets, but also unstaked MANTRA tokens without authorization.” The two forms of impact differ: the reported theft targeted assets already liquid in users’ wallets, while the unauthorized unstaking altered staked MANTRA positions.

The project said it would “suspend all new unstaking requests for seven days and reevaluate the situation after the pause ends.” It also specified that the suspension would not affect unstaking requests already in progress.

What does the seven-day pause cover?

The restriction covers all new unstaking requests. It does not cancel or pause requests already underway, which remain subject to MANTRA’s eight-day unstaking waiting period. The report did not give a calendar date for the start or end of the seven-day window, so November 13 should not be treated as the suspension’s published end date.

That split creates two operating conditions during the response: existing requests can continue, while anyone trying to initiate a new unstake must wait for MANTRA to reassess access after the pause. The project described no exceptions, thresholds or alternative route for new requests.

Users who had already submitted requests therefore face a narrower problem than prospective requesters. Their pending positions were not frozen by this measure, but MANTRA still warned that hackers could seize the assets if users did not act before the waiting period ended.

What should users do before the waiting period ends?

MANTRA urged users to redelegate tokens before the end of the eight-day unstaking waiting period to prevent hackers from seizing the assets. Its warning applies to pending requests: a user with an active request was told to act before that request reached the end of its wait, while a prospective requester could not submit during the pause.

The project did not explain how users should redelegate, which wallet to use or whether the recommendation changes if a request is nearly complete. Its instruction did, however, set a user-level deadline tied to the end of each eight-day waiting period.

What is known about the wallet-key leak?

Web3Auth and Keplr wallets are the only wallet names in the report. MANTRA did not publish a dollar value for the exploit, a token amount, the number of affected wallets, the identity of the attackers or any recovery. The report also did not name a blockchain or provide transaction hashes.

Without those details, the loss and the unauthorized unstaking activity cannot be independently sized from the information supplied. The seven-day pause therefore stands as a risk-control response to the disclosed wallet-key problem, not as an accounting of the full loss.

What changes when the seven days end?

MANTRA has said it will reevaluate the situation after the pause, leaving the restoration of new unstaking requests dependent on that review. The project has not promised an automatic restart, and the report gives no criteria for lifting the restriction. For MANTRA’s operations, the measure limits a route for moving staked tokens out while the wallet-key exposure remains under review.

The next fixed deadline for users is the end of each eight-day waiting period, the point by which MANTRA has urged them to redelegate. The next checkpoint for unstaking access is the end of the seven-day suspension, when MANTRA has said it will reassess whether new requests can resume.