Published verdictRanking snapshot 3 November 2026
Rabby Wallet leads by 1 point
Rabby Wallet scores 1 point above MetaMask, led by clear signing.
MetaMask #2 of 1180RBRabby Wallet #1 of 1181
Scores are out of 100; published scores fall within 41–99; a bar is empty at 41 and full at 99.Why, term by termRabby Wallet leads on 1 of 4 published criteria; MetaMask on 2. The terms sum to the gap.
TermRabby WalletMetaMaskWeightPoints
Clear signing8/106/107.2+3.7for Rabby Wallet+1.9 of 32
Incident record7/108/105.8−1.5for MetaMask−0.8 of 32
Account recovery8/109/104.3−1.1for MetaMask−0.6 of 32
Net of the terms+1.1
Criteria roundingThe criteria block is rounded to whole points before it is spread−0.1
Reproduced gap+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.MetaMaskScore 80The default EVM wallet: seed and per-account private-key export both documented on a stated BIP-44 path, a 2017-2025 public audit trail with three dated vendor advisories, and a pre-signature balance preview for contract interactions only, enforced onchain on 15 named networks for smart accounts on Extension.Strength: Key export — 9/10Watch-out: Read the fine print behind the three security claims on metamask.io before treating them as the product. All three are true and all three are narrower than they read. "Transaction protection available up to $10k" is not a wallet feature: it is Transaction Shield, "$9.99 monthly or $99 yearly", "Early access is now available on MetaMask Extension" only, capped at "Coverage of up to 100 transactions per month", and it explicitly "does not cover transactions deemed malicious by MetaMask" — so it does not pay out on the flagged case you most fear, and it does not exist on mobile. "Regularly audited by security firms" is backed by 17 genuinely public report links across 15 dated entries, but no report published since 2022 audits the shipped application itself: the 2023-2024 entries cover libraries, Snaps and build hardening, and the 2025 entries audit the mUSD stablecoin contract. And the pre-signature preview most buyers assume they are getting is, per MetaMask's own page (re-read 2026-09-28), available only "for contract interactions", not for native transfers; the enforced onchain simulation that reverts a transaction when execution diverges from the preview covers 15 named networks but is on by default only for "MetaMask smart accounts on Extension", and no page says what the confirmation screen shows when a simulation cannot be produced. If you pair a hardware device, two MetaMask troubleshooting pages tell you to enable blind signing, one of them with no qualifier at all. Finally, the exit that makes this record strong — pulling your encrypted vault out of local storage and decrypting it offline — is Chromium-desktop-only: MetaMask's own recovery page says it is "not currently possible" on Android or iOS, that the iOS method "is no longer working", that an Android solution is still being worked on, and that Firefox's data-encoding changes have made the instructions "of limited use".