Published verdictRanking snapshot 3 November 2026
Rabby Wallet leads by 1 point
Rabby Wallet scores 1 point above Trust Wallet, led by key export and account recovery.
RBRabby Wallet #1 of 1181
Trust Wallet #3 of 1180Why, term by termRabby Wallet leads on 2 of 4 published criteria; Trust Wallet on 1. The terms sum to the gap.
TermRabby WalletTrust WalletWeightPoints
Key export9/108/106.7+1.7for Rabby Wallet+0.9 of 32
Incident record7/108/105.8−1.5for Trust Wallet−0.8 of 32
Account recovery8/107/104.3+1.1for Rabby Wallet+0.6 of 32
Net of the terms+1.4
Criteria roundingThe criteria block is rounded to whole points before it is spread−0.1
Reproduced gap+1.3
Published gapAfter score rounding and bounds — see the note below8180+1.0
Weight is in points of the 86-point weighted total. Points are score points of the gap between the two.
Rabby WalletScore 81The reference implementation of pre-signature transparency in this pool, and the product that proves the signing axis actually separates. Rabby is a self-custodial EVM wallet from OPCODE LABS PTE. LTD. (the DeBank team), shipping as an MIT-licensed browser extension, a desktop app and iOS/Android apps. Where most wallets show a confirm button, Rabby's help centre documents an entire pre-signature apparatus: a simulation that previews the exact balance change, a decode that turns calldata into a readable action, a named Security Engine whose heuristics are published rather than hand-waved, and — uniquely in this pool — a hard lockout, "If a risk is detected, the Sign button will be disabled." Key custody is equally plain: one vendor page documents both Backup Seed Phrase and Backup Private Key on both platforms, with no email or account anywhere in the flow. The paperwork is better than it first appears: fourteen dated third-party audit reports across two repositories, from SlowMist, Least Authority and Cure53, spanning 2021-2025 and covering the extension, iOS and Android separately, joined by SlowMist reports dated 2026-08-24 for all three. What is genuinely missing is the disclosure machinery — no bug bounty, no security policy, no advisory archive — and the help centre remains silent on the October 2022 Rabby Swap contract exploit that cost users roughly $194,000, an event the vendor did in fact disclose on the day, on X, but never on its own website.Strength: Key export — 9/10Watch-out: Read the incident record before the feature list. Rabby is the strongest pre-signature product in this pool and among the weakest at maintaining a place to tell you when it has failed. There is no bug bounty (zero occurrences of "bount" anywhere in the homepage bundle or the help centre), no SECURITY.md (GitHub states outright "No security policy detected"), no security.txt, no advisory archive, no security@ contact and no postmortem page anywhere on rabby.io or support.rabby.io — so a researcher has no published private channel to report a vulnerability. On 2022-10-11 the Rabby Swap contract was drained of roughly $194,000 of user funds via approvals granted to it. In fairness the vendor did disclose it the same day on X, with a list of affected addresses, the four exploited contract addresses and revoke instructions — but that thread is now the ONLY disclosure that exists, and nearly four years on Rabby's own website and help centre still contain no mention of the event, nor any confirmation that the promised "satisfying solution for users within 1 week" was ever delivered. Weigh that against what IS published, which is more than it first appears: fourteen dated third-party audit reports across two repositories, from SlowMist, Least Authority and Cure53, spanning 2021-2025, with iOS and Android audited separately, and the extension set linked from a "Security & Transparency" section on Rabby's own homepage. Better than most of this pool, and newly refreshed: since August, SlowMist reports dated 2026-08-24 for the extension, iOS and Android have been added to the two repositories' audits/2026 folders. Three narrower things before committing. First, the protection you are buying is documented and sold for the EXTENSION: the Chrome Web Store listing advertises "pre-transaction potential risk scanning" and "upcoming balance change before you sign", while Rabby's own App Store and Google Play descriptions claim neither, so do not assume the mobile app is the same object. Second, no Rabby page ever prints "BIP-39" or a derivation path — verified zero hits across every vendor surface — so if you later want to restore your phrase into a different wallet you will be cycling HD-path options by trial and error. Third, the open-source guarantee is uneven: the extension's code is under an MIT grant (its LICENSE adds that "Brand name and logo of Rabby is copyright reserved", and GitHub reports the licence as NOASSERTION), but the mobile repository carries no licence file at all, so its published source grants no formal right to rebuild it if the vendor disappears.Trust WalletScore 80Mainstream self-custody mobile wallet with a genuinely documented simulate-and-decode signing screen on both platforms — but whose browser extension was supply-chain compromised in December 2025, still cannot export a raw private key, and whose audit register and security page carry no account of its own 2023 key-generation flaw.Strength: Key export — 8/10Watch-out: Read the vendor's own v2.68 post-mortem before you install the browser extension: https://trustwallet.com/blog/company/trust-wallet-browser-extension-v268-incident-community-update. Between 24 and 26 December 2025 an attacker published a backdoored build of the extension straight to the Chrome Web Store using a leaked API key, bypassing Trust Wallet's internal review; the vendor confirms 2,520 wallet addresses drained and approximately $8.5m in assets impacted. Reimbursement is promised but not finished: as of the post's last update on 17 July 2026 it still reads "We are finalizing the reimbursement workflow and ownership verification process", against "over 5,000 claims" for 2,520 verified addresses, and the page's own description calls itself "A work-in-progress update". The extension is also the weaker half of the product on exit: Developer Mode, the only documented private-key export, is "not available on Browser Extension". Separately, no vendor account of the 2022-23 key-generation flaw (CVE-2023-31290, exploited in the wild in December 2022 and March 2023) appears on its security-audit register or its /security page, both re-read on 2026-09-28, despite a published policy that remediated vulnerabilities will be disclosed. If you want Trust Wallet, the mobile app is the surface the evidence supports; treat the extension as the higher-risk, lower-portability half.