12 Monero OpSec Mistakes That Undo Your Privacy (and Fixes)
The most common Monero opsec mistakes, from random remote nodes and exchange round trips to address reuse and view key leaks, with a practical fix for each one.
On this page
- Quick reference
- 1. Connecting to random remote nodes over clearnet
- 2. Fast, same-size round trips between exchanges
- 3. Treating an exchange as your wallet
- 4. Reusing one address everywhere
- 5. Using one wallet for identities that must never meet
- 6. Sharing your private view key
- 7. Looking up your transactions on clearnet block explorers
- 8. Changing fee settings or using unusual wallets
- 9. Sweeping all your outputs into one transaction
- 10. Cross-contaminating identities
- 11. Downloading wallets from unofficial sources
- 12. Thinking a VPN equals anonymity
- Bonus: if you run a node, harden it
- A 10-point privacy checklist
- The takeaway
Key takeaways
- Monero's cryptography is rarely what fails. People get caught through their habits around it.
- The biggest leaks are IP addresses, fast same-amount transfers between exchanges, and reusing one identity across contexts.
- Use your own node or Tor, a new subaddress per counterparty, separate wallets per identity, and default fee settings.
- Never share your private view key or seed, and look up transactions on explorers only over Tor.
- Download wallets only from official sites, and verify them, since fake wallets are a bigger threat than any spy node.
Monero is the strongest privacy tool most people will ever hold, but it can’t protect you from yourself. When Monero users show up in court filings and investigations, the story is almost never “the cryptography broke.” It’s a reused email, a careless remote node, or a payment that arrived at an exchange forty minutes after it left another one. Here are the twelve mistakes that come up most often, and how to avoid each.
Quick reference
| # | Mistake | What it leaks | Fix |
|---|---|---|---|
| 1 | Random clearnet remote nodes | IP linked to your broadcasts | Own node or Tor |
| 2 | Fast, same-amount exchange round trips | Link between your exchange accounts | Delay, vary amounts, avoid round trips |
| 3 | Treating an exchange as a wallet | Full history to a third party | Withdraw to your own wallet |
| 4 | Reusing one address everywhere | Links all payers to you | New subaddress per counterparty |
| 5 | One wallet for separate identities | Janus-style linking | Separate seeds per identity |
| 6 | Sharing your private view key | All incoming payments, forever | Use payment proofs instead |
| 7 | Explorer lookups over clearnet | IP plus transaction ID | Tor Browser or local tools |
| 8 | Custom or odd fee settings | Makes your transactions stand out | Keep default priority |
| 9 | Sweeping all outputs together | Proves those outputs share an owner | Spend only what you need |
| 10 | Cross-contaminated identities | Real name tied to private activity | Separate emails, logins, shipping |
| 11 | Unofficial wallet downloads | Your seed and funds | Official sources, verify hashes |
| 12 | Trusting a VPN as anonymity | IP to the VPN company | Tor or I2P |
1. Connecting to random remote nodes over clearnet
A remote node can’t steal your coins or see your balance, but it does see your IP address and the transactions you push through it. That pairing is exactly what blockchain surveillance firms want. Investigations into leaked Chainalysis material found broadcast logs from nodes behind a round-robin DNS name that some wallets included by default. Feather’s documentation adds that a malicious node can tamper with fee data or attempt to bias decoy selection.
Fix: Run your own node. A pruned one uses about a third of the disk space. If you can’t, connect to a node you trust over Tor or I2P, ideally using its .onion address, and avoid hostnames that rotate between unknown nodes.
2. Fast, same-size round trips between exchanges
This is the mistake behind several public cases. Coins leave one service, pass through Monero, and land at a verified exchange shortly afterwards in a similar amount. Neither side has to break Monero. They just line up timestamps and amounts. This is the “Eve–Alice–Eve” pattern: an observer who sent you an output watches for it to come back.
Fix:
- Let real time pass between receiving and spending, hours or days rather than minutes.
- Don’t forward the exact amount you received.
- Avoid moving funds directly between KYC services. If you must, go through your own wallet with a delay, and consider whether a peer-to-peer route makes more sense.
Key point: Monero hides who sent a transaction among many possible senders. It can’t hide the fact that 3.4 XMR left your verified account at 14:02 and 3.39 XMR arrived at another one at 14:40.
3. Treating an exchange as your wallet
While your coins sit on an exchange, the exchange has your identity, your balance, every deposit and withdrawal, and often the IP and device you logged in from. Monero’s privacy only starts when the coins are in a wallet you control.
Fix: Withdraw to your own wallet promptly. Keep only what you’re actively trading on any custodial platform.
4. Reusing one address everywhere
Your primary address is like a permanent public identifier. Post it on your website, give it to an employer, and use it on a marketplace, and anyone who learns it from two places can connect those contexts.
Fix: Generate a new subaddress for each sender or purpose. Every Monero wallet supports this, and subaddresses can’t be linked to each other or to your main address by outside observers. Receiving to a new subaddress costs nothing.
5. Using one wallet for identities that must never meet
Subaddresses have a subtle weakness known as the Janus attack. Someone who knows two of your subaddresses can craft a payment to test whether they belong to the same wallet, then ask you, “Did you get it?” Confirming tells them the answer.
Fix: For identities that must stay separate, such as a public persona and a private one, use entirely different wallets with different seeds, not just different subaddresses or accounts. Be careful about confirming receipts to people you don’t trust, and check which address actually received the funds.
6. Sharing your private view key
A view key lets the holder see every incoming payment to your wallet, past and future. People hand it out to “prove” a balance, to tax tools, or to a support agent who asks for it.
Fix: Don’t share it unless you truly mean to give permanent read access to your incoming history. To prove a single payment, use a transaction proof (get_tx_proof in the CLI, or the “Prove/check” tab in the GUI), which reveals only that payment. If a view key does leak, move funds to a new wallet.
7. Looking up your transactions on clearnet block explorers
Block explorers can’t decrypt amounts or recipients, but the operator can log that your IP searched for a particular transaction ID, often seconds after it was broadcast. That’s a neat link between you and a transaction.
Fix: Use Tor Browser for explorer lookups, or rely on your own wallet’s history and your own node instead. Never paste transaction IDs or keys into random websites.
8. Changing fee settings or using unusual wallets
Monero’s privacy relies on transactions looking alike. If your wallet uses an odd fee level, a rare transaction structure, or a nonstandard client, your transactions become easier to pick out. A malicious remote node can also push unusual fee data at you deliberately.
Fix: Stick to the default fee priority unless you have a reason, use well-maintained mainstream wallets, and keep them updated so you match current transaction formats.
9. Sweeping all your outputs into one transaction
When a transaction spends several outputs at once, those outputs are publicly linked as coming from the same owner. If several of them came from places that know you, combining them strengthens any analysis.
Fix: Spend only what you need for a payment and let the wallet pick inputs. Use sweep_all only when you actually want to consolidate, such as when moving to a new wallet. Monero’s upcoming FCMP++ upgrade is expected to weaken this kind of linking, but it wasn’t on mainnet as of November 2026.
10. Cross-contaminating identities
The most common real-world deanonymization has nothing to do with blockchains. It’s a reused username, the same recovery email, a home shipping address, or a selfie on a public account.
Fix:
- Use separate email addresses and usernames for private activity.
- Don’t log in to private accounts from the same browser profile and IP as your real-name accounts.
- Remember that what you buy also identifies you. A delivery address undoes any amount of on-chain privacy.
11. Downloading wallets from unofficial sources
Fake Monero wallets in app stores and look-alike domains have stolen seeds for years. A compromised wallet is a total failure: theft plus every privacy leak at once.
Fix: Download only from official project sites, such as getmonero.org for the GUI and CLI, featherwallet.org for Feather, and the developer’s verified store listing for mobile wallets. Check hashes and signatures where the project publishes them. Never type your seed into a website, and never store it as a screenshot or in cloud notes. We go deeper on this in the Wallets category.
12. Thinking a VPN equals anonymity
A VPN hides your traffic from your ISP but shows all of it to the VPN company, which may keep logs or be compelled to share them. Paying for it with a card also links it to your name.
Fix: Use Tor or I2P for Monero traffic. Feather has Tor built in, the GUI and CLI accept a SOCKS proxy, and monerod can send your transactions only over Tor or I2P with --tx-proxy. The official Tor/I2P node guide walks through both networks.
Bonus: if you run a node, harden it
Node operators can protect their own transactions and everyone they relay for:
- Keep
monerodupdated. Version 0.18.4.3 added /24 subnet deduplication to disadvantage spy nodes, and later releases continued hardening peers and RPC. - Enable the community spy-node ban list that the Monero Research Lab recommends.
- Broadcast your own transactions with
tx-proxyover Tor or I2P. - Use restricted RPC for anything exposed beyond your own machine.
A 10-point privacy checklist
Print this, or keep it next to your wallet:
- My wallet connects to my own node, or to a trusted node over Tor or I2P.
- My coins live in my own wallet, not on an exchange.
- I use a new subaddress for each sender.
- Separate identities use separate seeds.
- I wait and vary amounts when moving funds between services.
- I don’t send funds in quick round trips between verified exchanges.
- My private view key and seed have never been typed into a website or shared.
- I look up transactions only over Tor, or not at all.
- I use default fee settings and an up-to-date official wallet.
- My private activity doesn’t share emails, usernames or addresses with my real-name life.
The takeaway
Monero gives you private amounts, hidden recipients and plausible deniability over every input, all by default. What it can’t do is stop you from attaching your name, IP address or timing to that privacy. As one long-time developer said in a 2026 community discussion, the best approach is usually to just use Monero normally and skip elaborate rituals. Get the basics above right and you’ll be more private than most people who obsess over churning schedules. More guides are in our Privacy & OpSec category.
Frequently asked questions
What is the most common Monero privacy mistake?
Moving funds quickly between custodial services with nearly identical amounts. Timing and amount correlation, combined with exchange records, is how most real-world cases have unraveled.
Is using a remote node a big privacy mistake?
Using a random clearnet remote node is. The operator can link your IP to the transactions you broadcast. A trusted node over Tor is acceptable, and your own node is best.
Should I use one Monero wallet for everything?
Use separate subaddresses for different senders at minimum, and separate wallets with different seeds for identities that must never be linked, such as a public persona and a private one.
Is it safe to look up my transaction on a block explorer?
The explorer can't see amounts or recipients, but it can log your IP alongside the transaction ID you searched for. Use Tor Browser, or the explorer built into your own node or wallet.
Does a VPN make Monero anonymous?
No. A VPN moves trust from your ISP to the VPN provider, which can see the same traffic. Tor or I2P is the better tool for hiding your IP from Monero nodes.