OPERATIONAL SECURITY (OPSEC) — COMPLETE GUIDE
WHY DO YOU NEED TO THINK ABOUT OPSEC?
Operational Security (OPSEC) is a systematic process for protecting sensitive information and activities from adversaries. On Tor networks, most de-anonymisation incidents are not caused by cryptographic failures — they result from human error: careless metadata exposure, reused identifiers, and inconsistent behaviour patterns that correlation attacks can exploit.
Law enforcement agencies use a range of techniques: traffic correlation attacks on Tor circuits, infiltration of vendor/buyer communities, package interdiction with controlled deliveries, financial tracing via KYC exchange records, and traditional HUMINT. A single OPSEC failure can link an otherwise anonymous identity to a real person.
WHAT HELPS YOU REMAIN ANONYMOUS?
- Use unique usernames per platform — never reuse
- Create dedicated email addresses for each identity
- Never mix clearnet and darknet identities
- Avoid any language or style patterns from clearnet
- Never discuss real-world information in any darknet context
- Always use Tor Browser — never access .onion via VPN alone
- Never enable JavaScript on .onion sites (set Security: Safest)
- Don't change Tor Browser window size (fingerprinting)
- Don't install plugins or extensions in Tor Browser
- Consider Tails OS for amnesic sessions
- Use dedicated hardware for sensitive activity
- Encrypt all storage (VeraCrypt or LUKS)
- Keep OS and software updated at all times
- Disable webcam, microphone when not in use
- Never use activity on shared or corporate devices
- Always encrypt messages with PGP before sending
- Verify recipient PGP keys before sending sensitive info
- Never include real addresses in unencrypted messages
- Use short-lived, compartmentalised messaging identities
- Assume all marketplace messages may be logged
ESSENTIAL TOOLS
| TOOL | PURPOSE | RESOURCE |
|---|---|---|
| Tor Browser | Anonymous web browsing | torproject.org |
| Tails OS | Amnesic live OS — leaves no trace | tails.boum.org |
| Kleopatra / GPG | PGP key management and encryption | gpg4win.org |
| Feather Wallet | Private XMR wallet with Tor built in | featherwallet.org |
| VeraCrypt | Disk / volume encryption | veracrypt.fr |
| Mullvad VPN | Optional pre-Tor VPN layer (no-logs) | mullvad.net |
| KeePassXC | Offline password manager | keepassxc.org |
| Whonix | Privacy OS (VirtualBox + Tor) | whonix.org |
RED FLAGS — WHAT YOU SHOULD AVOID
- Accessing .onion sites from a non-Tor browser — IP EXPOSURE
- Logging into darknet accounts from home/work IP (even via VPN) — TRACEABLE
- Reusing usernames from Reddit, Discord, or other clearnet services
- Posting photos with EXIF metadata (GPS coordinates embedded)
- Discussing transactions on social media — even vaguely
- Using personal email for marketplace registration
- Sending physical mail to your own address
- Telling friends/family about activities — social engineering target
- Using real name, date of birth, or identifiable information anywhere
- Storing sensitive data on cloud services (Google Drive, iCloud, Dropbox)
- Operating on a compromised device (malware, keylogger, screen capture)
- Using Tor over Tor (double-Tor routing creates timing vulnerabilities)
THREAT MODEL: KNOW YOUR ADVERSARY
OPSEC is not one-size-fits-all. Define your threat model before choosing tools:
| THREAT LEVEL | ADVERSARY | MITIGATION |
|---|---|---|
| LOW | ISP monitoring, basic surveillance | Tor Browser only |
| MEDIUM | Targeted investigations, marketplace leaks | Tails OS + PGP + XMR |
| HIGH | Nation-state, FVEY intelligence agencies | Air-gapped device + Tails + physical security |
| CRITICAL | Active law enforcement operation | STOP all activity immediately |
