xmr.club
EN 中文 ES RU
★ FRONT-PAGECDexsport— Web3 crypto sportsbook + casino since 2021, No-KYC, accepts XMR (+38 coins). Read first: documented cancelled-winnings /→
/wallets · verified 2026-10-21

XMRtab (Monero Wallet · Standalone)

F

Chrome-extension Monero wallet whose store build hides a data channel to its own server. Do not install it; if you did, move your funds to a new wallet.

Incident timeline
  1. 2026-10-02 Public GitHub repository published at v2.3.0; no further commits.
  2. 2026-10-20 Chrome Web Store build updated to v2.4.0.
  3. 2026-10-21 xmr.club compares the store build with official monero-ts 0.11.15 and finds the hidden data channel; listed at F.

At a glance

Grade
F
Last verified
2026-10-21
Operating since
2026-10 · 0y — GitHub account created 2026-09-30, repository 2026-10-02.
Incident
⚠ Active since 2026-10-21 — /incidents
curator verdict · bottom line

Curator Verdict & OpSec Breakdown

THE BOTTOM LINE

XMRtab (Monero Wallet · Standalone) carries significant OpSec reservations, unverified compliance claims, or unresolved incident flags. It is not recommended for critical privacy workflows.

✓

Proven Strengths

  • ▸ Established listing actively reviewed in the xmr.club Monero wallet directory.
⚠

OpSec Trade-offs & Caveats

  • ▸ ACTIVE INCIDENT (2026-10-21): The Chrome Web Store build (v2.4.0) contains code absent from the public repo: a custom-compiled wallet engine with two extra functions, and a 90-second routine that sends a hidden string, cut into 64-character chunks and disguised as transaction lookups, to node.xmrtab.com along with a browser fingerprint, regardless of the node you chose.
  • ▸ Clearnet-only footprint: lacks an official .onion hidden service mirror; exposes visitor network IP unless routed through VPN/Tor.
  • ▸ Fresh operational history: established recently (2026-10); limited track record under severe market volatility.

Review

Do not use this wallet. "Monero Wallet · Standalone" (xmrtab.com) presents itself as an open-source, non-custodial Monero wallet for Chrome, built on the official monero-ts library. The website and the code on GitHub look clean. The version actually served by the Chrome Web Store is not that code.

What we found in the store build. We downloaded version 2.4.0 straight from the Chrome Web Store (extension id `lkabbmdknccomhhhfhnljhfpofnhhifm`, package SHA-256 `5d10f7fb0b260abc2338118717815e526683583cb073d0df38891a805e2bad0a`) and compared it with official monero-ts 0.11.15, the version it claims to use:

  • The wallet engine (the WebAssembly code that holds your keys) was compiled separately and contains two functions that don't exist in monero-ts: `get_node_health_state` and `set_node_health_device`.
  • Every 90 seconds, the extension passes your browser's fingerprint (user agent, languages, time zone, CPU count, memory, platform) into the engine, reads a hidden string back out, cuts it into 64-character pieces and sends them to `node.xmrtab.com` disguised as ordinary transaction lookups. It does this no matter which node you chose in the settings.
  • Anything it couldn't send is stored in the browser and retried later.
  • None of this code is in the public GitHub repository, which is still at version 2.3.0. The extension's own "provenance" file also gives a wrong hash for the original monero-ts code.

We haven't decoded what the hidden string contains. A covert channel built into the code that holds your private keys has no innocent explanation, so we treat the wallet as malicious.

If you installed it. Assume your seed is compromised. Create a new wallet in a different, trusted app (on a clean device if you can), move your funds to it, and remove the extension.

Links

Audit trail — receipts for the editorial claim

Reviews — moderated · rules

No community reviews yet. Be the first below.

Add a review

Honest, brand-neutral feedback welcome. A curator approves before it appears here. No JS required.

What happened? (optional, tick any)

Keep order IDs, txids and addresses out of the review text: anything ID-like there is hidden when published.

Required: review body. Honest, descriptive reviews get approved within a day. Marketing copy, slurs, or invective get rejected. Per-day cap of 5 submissions per IP.