Skip to main content
Mallory
MediumPublic exploit

Predictable mnemonic generation in Trust Wallet Core / Trust Wallet browser extension

IdentifiersCVE-2023-31290CWE-338· Use of Cryptographically Weak…

CVE-2023-31290 affects Trust Wallet Core before 3.1.1, as used by the Trust Wallet browser extension before 0.0.183, specifically extension versions 0.0.172 through 0.0.182. The vulnerability is caused by use of the mt19937 Mersenne Twister PRNG with a single 32-bit seed as the entropy source for wallet mnemonic generation. Because the seed space is only 2^32, the number of possible mnemonics is drastically reduced from the expected cryptographic keyspace to roughly four billion possibilities. This makes generated wallet secrets predictable and enumerable. The issue was reportedly exploited in the wild in December 2022 and March 2023. The description provided indicates attackers could identify Ethereum addresses created since the 0.0.172 release and test whether they correspond to wallets generated by the vulnerable extension, enabling recovery of the associated wallet secrets and theft of funds.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows attackers to recover or predict wallet mnemonics/private keys for wallets generated by affected versions and steal cryptocurrency funds. The practical impact is direct compromise of wallet confidentiality and integrity, resulting in unauthorized transfers of assets. Because the entropy is only 32 bits, large-scale offline enumeration is feasible, especially when targeting addresses likely created by the vulnerable extension. The content states this was exploited in the wild.

Mitigation

If you can’t patch tonight, do this now.

Immediately stop using wallets generated by affected extension versions, upgrade to a fixed release, and transfer all assets to a new wallet generated after remediation. Treat any mnemonic or address created by vulnerable versions as compromised. Where operationally possible, identify wallets created during the affected version window and monitor for unauthorized transactions until funds are migrated.

Remediation

Patch, then assume compromise.

Upgrade Trust Wallet Core to 3.1.1 or later and the Trust Wallet browser extension to 0.0.183 or later. For users who created wallets with affected extension versions 0.0.172 through 0.0.182, upgrading alone is insufficient; funds should be moved to a newly generated wallet address created with a fixed version, because previously generated mnemonics may already be predictable or recoverable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Trust WalletTrust Wallet Browser Extensionapplication
Trust WalletTrust Wallet Coreapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

perelmanworkNews
Jan 16, 2026
Phantom Signature Attack: An Analysis of the Critical Vulnerability CVE-2025-29774 in the Bitcoin Protocol, SIGHASH_SINGLE Implementation Flaws, and the Mathematical Framework for Private Key Recovery in Lost Cryptocurrency Wallets Enabling Unrestricted Control over BTC Assets - Perelman Work

The content references CVE-2023-31290 in connection with deterministic random number generation and private key compromise, but provides no concrete technical details about the vulnerability itself.

Read more
f5 communityNews
Dec 30, 2025
F5 Threat Report - December 31st, 2025 | DevCentral

Referenced in the Trust Wallet extension incident section as an associated CVE, but the content does not describe what CVE-2023-31290 is or how it relates technically to the compromise.

Read more
f5 communityNews
Dec 30, 2025
F5 Threat Report - December 31st, 2025 | DevCentral

Referenced in the Trust Wallet extension hack section as a CVE associated with the broader threat/IOC listing, but not explained in the provided content.

Read more
key5News
Dec 15, 2025
시그니처 하이드라 공격: ECDSA 역직렬화 및 분실된 비트코인 ​​지갑의 개인 키 복구 과정에서 발생하는 심각한 취약점으로, 공격자는 서명 역직렬화 오류와 버그를 악용하여 피해자의 지갑에 대한 제어권을 점진적으로 획득합니다. - 열쇠 사냥꾼

결정론적 난수 생성 취약성과 연계된 비트코인 개인 키 노출 위험으로 언급되지만, 본문 내 상세 설명은 제한적이다.

Read more
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.