Guide library PENGER Academy

Operational Security (OpSec)

Turn a threat into a repeatable check: before installation, before signing and before recovery is needed.

What you’ll learnRecognize a phishing request, verify a transaction and rehearse recovery without exposing a live seed.

Before you startKnow which backup and device authorize your funds. Never enter them into a website.

What Is OpSec?

Operational security (OpSec) is the practice of protecting sensitive information by identifying vulnerabilities and eliminating them before an adversary can exploit them. Originally a military concept, OpSec has become essential for anyone holding significant value in cryptocurrency.

In crypto, OpSec spans three interconnected domains:

  • Digital security — protecting your devices, accounts, and online identity from hacking, malware, and phishing
  • Physical security — protecting your seed phrase backup, hardware wallet, and physical environment from theft, fire, and natural disaster
  • Social security — controlling what information you reveal about your holdings, habits, and identity to prevent targeted attacks

Name the asset, the attacker and the route to it. Then identify what could prevent the attack, how you would notice it and how you would recover. “Is my wallet secure?” is too broad to choose a useful control.

Good OpSec is not about being paranoid — it is about being methodical. You systematically identify what you're protecting, who you're protecting it from, and what practical steps reduce your risk surface.

Threat Modeling Basics

Before implementing security measures, you need to understand what you're protecting against. A threat model is a structured way of thinking about risk. Ask yourself:

  1. What am I protecting? — seed phrases, private keys, hardware wallets, account access
  2. Who might want to steal it? — hackers, scammers, criminals, insiders
  3. What methods would they use? — phishing, malware, physical theft, coercion
  4. What is the impact if they succeed? — total loss, partial loss, privacy breach
  5. What am I willing to invest in prevention? — time, money, convenience trade-offs

Common Threat Actors

  • Opportunistic hackers — automated scanning for weak passwords, exposed keys, and phishing victims. They cast a wide net and rely on volume.
  • Targeted attackers — individuals or groups who know (or suspect) you hold significant crypto. They invest time in reconnaissance and custom attacks.
  • Phishers and scammers — impersonating exchanges, wallet providers, or support staff to trick you into revealing credentials or seed phrases.
  • Physical attackers — may resort to coercion, extortion, or the "$5 wrench attack" (physical violence to force compliance). This is why you should never publicly disclose your holdings.
  • Insiders — family members, roommates, or colleagues who may have physical access to your backup material.

Prioritize controls you can maintain. Consider exposure and the harm a loss would cause. A fixed dollar threshold cannot tell you which setup is appropriate for you.

One event, two kinds of damage

A stolen laptop might expose an unlocked hot wallet, a watch-only address list or neither. The same theft can also destroy your only recovery instructions. List confidentiality and availability separately before selecting a control.

Digital Security Habits

Start with the devices and accounts that can expose secrets or authorize actions. Unique passwords, phishing-resistant account authentication and maintained software cover different parts of that path.

Authentication

  • Use a password manager to generate and store unique, random passwords for every account
  • Enable two-factor authentication (2FA) on every crypto-related account — exchange, email, cloud storage
  • Use hardware security keys (FIDO2/WebAuthn) instead of SMS or TOTP codes whenever possible — hardware keys are phishing-resistant
  • Never use SMS-based 2FA for high-value accounts — SIM-swap attacks can bypass it trivially

Device Security

  • Keep operating systems and wallet software up to date — security patches are released for a reason
  • Use full-disk encryption on all devices (FileVault on macOS, BitLocker on Windows, LUKS on Linux)
  • Avoid installing unnecessary software, browser extensions, or mobile apps — each is a potential attack surface
  • Use a dedicated browser profile (or separate browser) for crypto activities — isolated from your general browsing

Do not disclose your recovery phrase or private key. Support staff, message senders and websites do not need them to “verify” a wallet. A genuine local recovery procedure is a different action: confirm its purpose and use the intended trusted signer. Never give another person your login password.

Physical Security Fundamentals

Your seed phrase backup is the most critical physical item in your crypto setup. If it is lost, stolen, or destroyed, your funds may be permanently inaccessible.

Storage Best Practices

  • Record your seed on a durable medium — stamped or engraved metal plates can resist heat, water and corrosion better than paper; performance depends on material, construction and the exposure
  • Store in a fireproof, waterproof safe that you control
  • Maintain geographically separated copies to protect against localized disasters (fire, flood, earthquake)
  • Consider a safety deposit box or trusted second location for one backup copy
  • If using a BIP39 passphrase, store it separately from the seed phrase — an attacker who finds both can access your funds

Keep seed phrases out of photos, cloud storage and messages. Do not photograph them on your phone, enter them on a website or send them by email or chat. These actions create extra copies you may not be able to control or delete.

Hardware Wallet Physical Security

  • Store your hardware wallet in a location separate from your seed backup (so a single burglary doesn't compromise both)
  • Use the device PIN to protect against casual physical access
  • Enable the auto-wipe feature (if available) that erases the device after a set number of incorrect PIN attempts
  • Check packaging integrity when receiving a new device — look for signs of tampering, broken seals, or pre-initialized state

Social Engineering Defense

Social engineering is the manipulation of people to divulge confidential information or perform actions that compromise security. In crypto, it is one of the most effective and common attack vectors.

Key Rules

  • Never disclose your holdings publicly — on social media, forums, in-person conversations, or anywhere that could reach an attacker. You become a target the moment someone knows you have significant crypto.
  • Verify before trusting — always independently verify the identity of anyone requesting sensitive information. Don't trust caller ID, email addresses, or display names.
  • Be skeptical of urgency — scammers create artificial time pressure ("your account is compromised, act now!") to bypass your critical thinking.
  • Never share your screen during wallet operations, and never allow "remote support" to access your device.

Common Social Engineering Tactics

  • Impersonation — pretending to be exchange support, wallet developers, or government officials
  • Fake giveaways — "send 0.1 BTC, receive 1.0 BTC back" scams are ubiquitous and always fraudulent
  • Compromised accounts — a friend's hacked social media sends you a malicious link or seed phrase request
  • Fake wallet apps — cloned apps in app stores that look identical to legitimate wallets but steal your keys
When a message asks for a secret
  1. PauseUrgency is a reason to check, not to disclose.
  2. Leave the messageDo not use its links, attachments or phone numbers.
  3. Verify independentlyOpen a support channel you already know. Never send your recovery phrase.

Verify the download and the spend

These are separate checks. A valid download signature says something about the publisher of a file; a correct transaction display says something about the spend you are about to authorize.

  1. Establish the source. Use a previously verified bookmark or follow the project’s documented distribution channel. Search ads, display names and HTTPS alone do not establish identity.
  2. Verify the release. Compare a checksum from an authenticated source and, where provided, verify a release signature against the expected public key. A hash copied from the same compromised page is weak independent evidence.
  3. Read the whole destination. Compare the full address and network on the signer with an independently verified destination. Comparing two screens that repeat the same poisoned input is insufficient.
  4. Check the authorization. Read the amount, fee, change handling and any contract permissions. If the signer cannot explain the action, do not approve it merely because the app calls it safe.
A matching prefix is not a match

An attacker can search for a lookalike address with the same first and last characters. Checking six characters at each end is not a substitute for checking the full address. A small test transfer is useful only if the destination for the next transfer is checked again.

For a file hash: sha256sum filename on Linux, shasum -a 256 filename on macOS, or Get-FileHash filename in PowerShell. These commands calculate a hash; they do not authenticate its reference value.

Set up without removing your fallback

  1. Obtain a signer through a verified distribution channel. Inspect its condition and follow model-specific authenticity and firmware instructions. Reject pre-supplied recovery words.
  2. Generate training keys first if the workflow is unfamiliar. Keep cameras, screen sharing and remote support out of secret-handling steps.
  3. Create and check the complete backup on the intended trusted device. For a funded wallet, use a built-in check or a spare compatible signer; do not wipe your only working device as the first test.
  4. Receive a small amount at a verified address, then complete a spend. Confirm what the device displays and which metadata recovery needs.
  5. Separate backup failure locations and record the procedure without exposing all secrets in the instructions.

Stop conditions

Stop if the device arrives initialized unexpectedly, the software identity cannot be established, a backup check fails or the displayed transaction differs from your intention. Resolve the cause through independently verified channels before funding or signing.

Review access and respond to an incident

Review after a move, a device change, a new signing policy or a relevant security advisory. Check readability, access to backup locations, exact passphrases and policy metadata without casually exposing the secrets.

Choose the response to the actual event
Event First useful action
Device fails; backup remains confidential Restore with compatible tools and verify known addresses. A routine failure alone does not mean the seed must change.
Seed may have been copied Treat the old secret as potentially known. Use a trusted setup with new keys and a verified backup to move remaining funds. A new PIN does not revoke the old seed.
Suspicious support message or transaction prompt Stop the requested action. Independently verify the account or software state; do not use the contact link supplied by the message.
Backup location becomes inaccessible Check surviving recovery paths before altering anything. Avoid destroying or resetting the remaining working signer.

Preserve nonsecret records relevant to an incident. Do not publish seed material in a support ticket or attempt recovery by entering it into an unfamiliar website.

Questions that remain

Should I tell people how much crypto I own?

No. Public disclosure of holdings makes you a target for social engineering, phishing, SIM-swap attacks, and even physical coercion. The crypto community principle is: never reveal your portfolio size. Keep holdings private and only discuss specifics with trusted advisors (lawyer, accountant) under appropriate legal confidentiality.

Is a password manager safe for storing seed phrases?

Password managers are excellent for account passwords and 2FA backup codes, but storing your seed phrase there is risky. If your master password is phished or your device is compromised, the attacker gains access to the seed. Seed phrases should exist only on physical media (stamped metal, hand-written paper) stored in secure offline locations. The principle is clear: seed phrases belong in the physical world, not the digital one.

What is a “$5 wrench attack”?

This refers to physical coercion to obtain access. Cryptography cannot guarantee personal safety or that a decoy will be accepted. Reduce unnecessary disclosure, plan access carefully and prioritize personal safety; distributed signers change authorization requirements but do not eliminate coercion risk.

How often should I test my backups?

Test recovery after setup and whenever the backup format or signing policy changes. Prefer the hardware signer’s built-in seed-check or a wiped, compatible hardware signer, then verify known addresses. Never type a live seed into an ordinary online software wallet; use a training seed, or move the funds first if software restoration is unavoidable. An untested backup is only a hope.

Is it safe to buy a hardware wallet from Amazon or eBay?

Use the manufacturer or an authorized reseller confirmed through the manufacturer’s verified site. Follow model-specific authenticity checks and reject unexpected initialization or supplied recovery words. Packaging alone cannot prove that a device is trustworthy.

What happens to my crypto if I die?

Without an inheritance plan, your crypto is likely lost forever. Unlike bank accounts, there is no institution that can grant your heirs access. You need to create a documented recovery plan: a sealed letter of instruction stored with your will, explaining where your seed backups are located and how to use them. For advanced setups, consider multi-sig with a trusted family member or lawyer as cosigner, or Shamir's Secret Sharing (SLIP39) with shares distributed among trusted parties.

[ CHECK YOURSELF ]

Test Your Knowledge

Take a quick quiz to check your understanding of this guide.

Take the Quiz

5 questions per level · ~2 min