Entry · Ref 6GM2QRR0
What to verify before signing in through a mirror link
- Posted
- 2026-11-17
- Last amended
- 2026-11-17
- Account
- @hiddennetworkguide
Before you enter your credentials on any mirror page of a darknet marketplace, you need to confirm that the page is genuine and that your session won't be intercepted. A fake mirror can capture your password, your two-factor codes, and your session cookie in seconds. The safest habit is to verify the PGP signature on the mirror's announcement, check the URL character by character, and never reuse a password that has ever touched another service. This article walks through the practical checks that protect your account when you use a mirror link.
Why mirrors are risky by design
A mirror is a copy of a site hosted on a different onion address. Marketplaces use them to spread traffic and stay online when one address is blocked or slow. The problem is that anyone can create a page that looks identical to the real login screen. If you type your details into a phishing mirror, the attacker gets your username, password, and any two-factor code you enter. From there they can drain your account before you even realise something is wrong. The same risk applies to session cookies: a fake mirror can steal an active session cookie and let the attacker act as you without needing your password again.
Because mirrors are published by the marketplace itself, the only safe source for a mirror address is the marketplace's official PGP-signed announcement. If you find a mirror link on a forum, a chat, or a search engine, treat it as hostile until you can verify its signature against the marketplace's known public key. This is the core of PGP security guidance for anyone who uses darknet services: never trust a link you cannot verify with a cryptographic signature.
Verify the PGP signature on the mirror announcement
Every reputable marketplace publishes its mirror addresses inside a PGP-signed message. That message might appear on a clearnet news site, a dedicated status page, or a forum thread that the marketplace controls. The signature proves that the message came from the marketplace's private key, not from an impostor. To check it, you need the marketplace's public key, which you should have saved from the very first time you visited the real site. If you never saved it, find it through a trusted source: the marketplace's own help page, or a community that cross-checks keys.
When you open the signed message, look for the block that starts with "-----BEGIN PGP SIGNED MESSAGE-----" and ends with "-----END PGP SIGNATURE-----". Paste the whole block into your PGP software (GnuPG, Kleopatra, or a mail plugin) and verify the signature. The output should tell you the key ID and whether the signature is good. If it says "good signature" and the key ID matches the one you saved, the mirror addresses in that message are genuine. If you see "bad signature" or a key ID you do not recognise, stop. Do not use any of the links in that message.
A common mistake is to check the signature only once and then reuse the same mirror address for weeks. Marketplaces rotate mirrors often, and an address that worked last month might now point to a phishing site. Check the signature every time you visit a new mirror, even if the URL looks familiar. This is tedious, but it is the single most reliable way to stay safe.
Check the onion URL character by character
Onion addresses are long random strings, usually 56 characters for version 3 addresses. Phishers often register addresses that look similar at a glance: they swap a letter, double a character, or use a homoglyph that resembles the original in a certain font. A real address might be "abcdefghijklmnopqrstuvwxyz1234567890abc.onion" and a fake one might be "abcdefghijklmnopqrstuvwxyz1234567890abd.onion", the difference is a single character near the end. If you do not check every character, you can land on a perfect copy of the login page that sends your credentials to an attacker.
One practical method is to copy the mirror address from the signed announcement and paste it directly into your Tor browser. Never type it manually. If you must compare two addresses, put them side by side in a text editor and read them aloud character by character. Some people use a checksum tool to compare the hash of the address, but that is overkill for most users. What matters is the discipline of checking, not the tool.
When you are on the mirror page, look at the URL bar again before you type anything. A page that loads quickly and looks identical to the real site can still be fake. The only thing that proves it is the marketplace's server is the onion address itself. If the address is correct, the connection is end-to-end encrypted and authenticated by the Tor network. If it is off by one character, you are on a different server entirely.
Use a unique, strong password and a password manager
Even if the mirror is genuine, your account is only as secure as your password. If you have used the same password on another marketplace, a forum, or a clearnet site, that password is probably already in a credential dump. Attackers buy these dumps and try the same email-password combinations on every darknet marketplace they can find. If your password appears in a dump, it does not matter how carefully you verify mirrors, your account can be taken over by someone who never touched a phishing page.
A password manager solves this by generating and storing a random, long password for each service. You only need to remember one master password. When you sign in through a mirror, the password manager will auto-fill the credentials only if the domain matches the one you saved. If the mirror URL is even slightly different, the manager will not offer to fill, which acts as a second check on the address. This is one reason why security-conscious users never type passwords from memory on a darknet site.
Combine the strong password with a recovery code that you store offline. Most marketplaces give you a recovery code when you enable two-factor authentication. Keep that code in a safe place, like an encrypted file on a USB drive or a printed piece of paper in a secure location. If you ever lose access to your second factor, the recovery code is the only way back in. Do not store it in your password manager or on your phone.
Enable two-factor authentication and review your session settings
A password alone is not enough. Two-factor authentication adds a second check that even a stolen password cannot bypass. Most darknet marketplaces support TOTP-based two-factor authentication, where you enter a six-digit code from an authenticator app. Some also support PGP-based two-factor, where the site sends you an encrypted challenge that you decrypt with your private key. Both are far better than password-only protection, but they are not foolproof. A phishing mirror that captures your password and your TOTP code in the same form can still compromise you if the attacker uses both immediately.
That is why you should follow a proper two factor setup guide when you first configure your account. A good guide will tell you to scan the QR code in a secure environment, save the recovery code before you confirm the setup, and test the second factor by logging out and back in. It will also warn you never to enter a two-factor code on a page you have not verified. If you have not done this yet, set aside 15 minutes to complete it. The same two factor setup guide applies whether you are on the main site or a mirror, the security of the second factor depends on the honesty of the page you are using.
Watch for session theft and logout after every visit
Even after a successful login, your session remains vulnerable. A session cookie is a small token that the site uses to remember that you are authenticated. If an attacker steals that cookie, they can impersonate you without needing your password or your two-factor code. Session theft can happen through a malicious mirror, a compromised browser extension, or a man-in-the-middle attack on an insecure network. On Tor, the network itself is encrypted, but the browser is still ordinary software with its own vulnerabilities.
To reduce the risk, log out of the marketplace when you are done. Closing the browser tab is not enough, the session cookie may still be valid until it expires. Use the site's logout button, which tells the server to invalidate the cookie. If the marketplace offers a "log out of all sessions" option, use it every few days, especially if you have used a mirror that you were not 100% sure about. Some users set a browser profile that does not save cookies at all, so every visit starts with a fresh login. That adds friction but removes the risk of a persistent stolen session.
Also consider using a separate Tor browser instance for each marketplace. That way, a compromise on one site cannot leak cookies to another. It is not strictly necessary for everyone, but if you manage multiple accounts, it is a cheap layer of isolation.
Treat every mirror as suspicious until proven otherwise
The mindset matters as much as the steps. Assume that any mirror address you encounter outside the signed announcement is hostile. Do not click links from private messages, even if they appear to come from a moderator. Moderators' accounts can be compromised, and a fake message with a real-looking signature is not hard to create if the attacker has access to the moderator's key. Verify everything through the official channel, which is the marketplace's own PGP-signed status page or its clearnet news site.
If you ever enter your credentials on a page that you later realise was a fake, act immediately. Change your password, rotate your two-factor secrets, and check your account for unauthorised transactions. Most marketplaces have a support ticket system for compromised accounts, but they cannot reverse a withdrawal that already happened. The best protection is prevention: verify the mirror, verify the signature, and never trust a link you cannot prove is genuine.