Most wallet losses do not start with a broken curve. They start with a setting nobody changed and a transaction nobody read.
This checklist is ordered by how much damage each item prevents, not by how technical it feels. The first four cover the majority of real incidents we have written about; the rest are cheap insurance. Work down the list once, then put items 6 and 7 on a calendar.
The checklist
| # | Fix | Why it matters |
|---|---|---|
| 1 | Separate wallets by job | A wallet that signs everything eventually signs the wrong thing |
| 2 | Long-term holdings on a hardware wallet | Keys stay offline; host malware cannot reach them |
| 3 | Revoke old approvals quarterly | Standing allowances are standing orders to drain |
| 4 | Never sign blind | Blind signing is how drains get past careful people |
| 5 | Treat unsolicited tokens as bait | Interaction, not holding, is the attack |
| 6 | Use a burner for airdrops and new dApps | Caps the blast radius of a mistake |
| 7 | Review the approval dashboard monthly | Early warning beats post-mortem |
| 8 | Verify addresses character by character | Address poisoning targets the clipboard and the habit |
| 9 | Turn on app-based 2FA everywhere | SMS is the weakest link in account recovery |
| 10 | Keep the seed phrase offline and tested | A backup you never restored is a rumour |
| 11 | Send a small test transaction first | Cheap rehearsal, expensive mistake avoided |
| 12 | Write an incident plan | Minutes matter after a leak; improvisation does not |
Why these four wallet security fixes carry most of the weight
Wallet separation. Almost every incident story we publish has the same shape: one wallet, multiple jobs. It holds the long-term position, connects to new protocols, and claims airdrops, and the person using it is tired at 1am. Splitting by job means a mistake costs the pocket-money wallet, not the one holding years of savings. The hot wallet vs cold wallet distinction exists for exactly this reason.
Hardware for anything you would not gamble. A hardware wallet keeps the key out of the host machine’s memory; malware with screen capture gets nothing useful. It does not review what you sign, which is why the next item matters.
Approval hygiene. Every time you interact with a token contract, you may leave behind an allowance that lets it move your balance later. Infinite approvals are the extreme version, but any allowance is a standing order. Check the approval dashboard, revoke what you do not recognise, and repeat quarterly. Our longer explainer on token approval safety walks through what each permission means.
Refusing blind signing. When a wallet shows raw hex or an opaque “Sign” prompt, the device is asking you to authorise something you cannot verify. Attackers build their flows around this: a signature that looks like a login, an EIP-712 payload with fields you skim. If the wallet cannot decode it, decline and use a different interface.
The ones people skip, and regret
Unsolicited tokens. A token appearing in your wallet is not a gift; it is a contract address you have not vetted. The moment you try to sell it, you are signing against attacker-controlled code. Honeypots and approval drainers both live here. Ignore, hide, move on.
Address poisoning. The attacker sends a tiny transfer from an address that starts and ends with the same characters as the one you copy often, then waits for you to paste from history. Read the full address, use an address book, and treat a new “recent recipient” you do not remember as a red flag. We covered the mechanics in the wallet drainer explainer.
2FA on the recovery path. Your email is the master key to exchange accounts, password resets and support impersonation. SMS codes are routinely intercepted by SIM swaps. Move to an authenticator app or a hardware key, and store backup codes offline.
The restore test. A seed phrase written down but never restored is an untested assumption. Restore it once on an empty device, confirm the same addresses, then wipe. This is also the moment you find out whether your handwriting is legible six months later.
Test transactions. Every new recipient or chain gets a small transfer first. Fees are trivial; a mistyped address on a large transfer is permanent.
An incident plan. Write down, in advance: which wallets exist, where backups live, which revoke tool you will use, and the first three actions if something drains. Panic is faster than research, and only a plan survives it.
Limitations
No checklist removes risk; it moves risk to places you have chosen. Hardware wallets can arrive tampered, as the Ledger reseller case showed. Approvals can be re-created by a single signature. And none of this helps if the seed phrase is exposed at the root, which is why seed phrase safety comes first.
What this list does do is remove the losses that are boring, repeated, and entirely avoidable. In our incident archives, that is most of them.
Frequently Asked Questions
What is the single most effective wallet security change?
Separate wallets by purpose. A hardware wallet that never touches a dApp holds long-term assets; a hot wallet with pocket money does the interacting; a burner takes the airdrops. Most catastrophic drains happen because one wallet did all three jobs at once.
How often should I revoke token approvals?
Every three months for wallets you use weekly, and immediately after any interaction with a new or unaudited protocol. Approval dashboards show every contract that can still move your tokens; leaving old allowances open is how a compromise from last year becomes a loss this year.
Are hardware wallets enough on their own?
No. A hardware wallet protects the key, not the signature. If you approve a malicious contract and confirm it on the device without reading the details, the hardware wallet signs the theft. Device plus approval hygiene is the unit that works.
What should I do with free tokens I did not buy?
Assume they are bait. Do not interact with the contract, do not try to swap them, and do not 'claim' anything they advertise. Most unsolicited tokens are honeypots whose only function is to make you sign something. Hide them and move on.
Is two-factor authentication worth it for wallet-related accounts?
Yes, but only app-based or hardware-key 2FA, never SMS. Email and exchange accounts are the recovery path for everything else, so they belong on passkeys or authenticator apps, with a backup code stored offline.