Crypto Safety Audit Checklist: Run This Every Quarter
A wallet compromise is rarely a single mistake. It is a set of habits that make one mistake expensive. Here is a twenty-minute quarterly audit that finds the exposures before someone else does.
Crypto Safety Audit Checklist: The Four Areas
- A wallet compromise is rarely one mistake. It is a set of habits that make a single mistake expensive.
- A twenty-minute audit every quarter finds the exposures before someone else does.
- The audit covers four areas: approvals, seed phrase storage, device hygiene and account access.
- The most common finding is a dormant unlimited approval to a contract you no longer use.
- The audit is only useful if it produces a written list of actions with dates.
Nobody hacks a careful wallet owner. They audit them first, looking for the same things you would look for: an approval that was never revoked, a seed phrase stored somewhere convenient, a device with an extension nobody remembers installing. The audit is cheap, and it is the reason most compromises are not surprises.
This tutorial is a twenty-minute quarterly audit. It covers four areas, produces a written list of actions, and takes less time than reading about a loss afterwards.
Why an audit beats being careful
Care is not a mechanism. You cannot be careful about a risk you have not identified, and the exposures that cause losses are usually invisible: an approval granted months ago, a seed phrase photographed once, an extension installed for a single task.
An audit is a mechanism. It is a fixed list of checks performed on a schedule, and its value is that it does not depend on remembering anything.
| Vigilance | Scheduled audit |
|---|---|
| Depends on memory | Runs from a written list |
| Applied when you think of it | Applied on a fixed schedule |
| Finds what you already suspect | Finds what you have forgotten |
| No record | Produces a dated action list |
| Degrades over time | Stays constant |
The audit is not about being more careful. It is about replacing care with a list, because a list does not forget and care does.
Area one: approvals
Approvals are the most common finding and the most dangerous. An approval is a permission you granted to a contract to move a token on your behalf, and an unlimited approval to a contract you no longer use is a standing invitation.
Review every approval and revoke anything you do not recognise or no longer need. This takes five minutes and it is the highest-value part of the audit.
- 01Open a reputable approval manager and connect the wallet you use for interacting with sites.
- 02List every approval, sorted by the spender address.
- 03Revoke anything you do not recognise.
- 04Revoke anything unlimited that you no longer actively use.
- 05Revoke approvals granted to contracts from sites you have stopped using.
- 06Screenshot the list before revoking, as a record of what was granted.
An unlimited approval to an address you do not recognise is the single most dangerous thing in a wallet. It can be used at any time, without another signature, and it does not expire.
Area two: seed phrase storage
The seed phrase is the wallet. If it has ever been typed into a website, sent in a message, photographed, or stored in a cloud note, the wallet is compromised regardless of what the balance shows.
The audit question is not whether the storage is convenient. It is whether the phrase has ever existed in a digital form, because there is no way to un-expose it.
| Storage | Verdict | Why |
|---|---|---|
| Paper, offline, in a safe | Safe | Never exists digitally |
| Stamped metal, offline | Safe | Survives fire and water |
| Password manager | At risk | One breach exposes it |
| Cloud note or photo | Compromised | Accessible to anyone with the account |
| Typed into a website | Compromised | Assume it was captured |
| Sent in a message | Compromised | Assume it was captured |
There is no way to un-expose a seed phrase. If it has been typed anywhere, the only response is a new wallet with a new seed phrase, and moving everything to it.
Area three: device hygiene
A compromised device can capture a new seed phrase as easily as an old one, which is why device hygiene is part of the audit rather than a separate concern. Malware, a malicious browser extension or a remote-access tool all defeat a perfect seed phrase policy.
The checks are quick. The point is to find anything you did not deliberately install.
- Review browser extensions and remove anything you did not install deliberately.
- Check for remote-access tools and remove them.
- Run a full malware scan.
- Check for software you do not recognise in startup items.
- Confirm your operating system and browser are up to date.
- Check whether any wallet software is out of date.
The question to ask about every extension and every piece of software is whether you installed it deliberately. If you cannot remember installing it, remove it.
Area four: account access
Exchange accounts and email accounts are the other half of the picture. An email account is the recovery route for everything else, so it is the account that matters most and the one most often left with the weakest protection.
The audit checks three things: the strength of the second factor, the list of active sessions, and the list of recovery options.
- 01Confirm two-factor authentication is enabled on email and every exchange account.
- 02Replace SMS-based second factors with an authenticator app where possible.
- 03Review active sessions and sign out anything you do not recognise.
- 04Review recovery email addresses and phone numbers, and remove anything stale.
- 05Check for forwarding rules you did not create.
- 06Change any password that is reused anywhere else.
An email account with SMS-based two-factor authentication is the weakest link in most setups. SMS can be intercepted, and the email account is the recovery route for everything else.
The written action list
The audit is only useful if it produces a written list. A finding you have not written down is a finding you will forget, and the whole point of the audit is to replace memory with a record.
Keep the list with a date, and keep the previous one. The comparison between audits is where the value accumulates, because it shows what you fixed and what you keep deferring.
| Field | Why |
|---|---|
| Date of the audit | Establishes the schedule |
| Finding | What the check revealed |
| Action taken | What you did about it |
| Deferred items | What you chose not to fix, and why |
| Next audit date | Keeps the schedule honest |
Twenty minutes every quarter, with a written list, is more protection than any amount of good intentions. The schedule is the mechanism; the list is the record.
The audit in one page
The whole audit fits on a single page, and it is worth printing or saving so the schedule does not depend on remembering it. Twenty minutes, four areas, one written list.
Work through it in order. The approvals area comes first because it is the highest-value check and the most common finding.
| # | Check | Time |
|---|---|---|
| 1 | Review and revoke token approvals | 5 min |
| 2 | Confirm seed phrase storage is offline and never typed | 2 min |
| 3 | Review browser extensions and remove anything unrecognised | 3 min |
| 4 | Run a malware scan and check for remote-access tools | 4 min |
| 5 | Confirm two-factor authentication on email and exchanges | 2 min |
| 6 | Review active sessions and recovery options | 2 min |
| 7 | Write the action list with a date and a next-audit date | 2 min |
Print the list and put the next audit date in your calendar. The schedule is the mechanism, and a mechanism that depends on memory is not a mechanism.
What to do with what you find
The audit will find things, and the response depends on what kind. Some findings are fixed in place; others mean the wallet should be abandoned. Knowing which is which prevents both overreaction and underreaction.
The dividing line is whether the seed phrase has been exposed. If it has, the wallet is finished regardless of what else the audit found.
| Finding | Response | Urgency |
|---|---|---|
| Unlimited approval to an unknown contract | Revoke it | Immediate |
| Approval to a site you no longer use | Revoke it | This session |
| Seed phrase stored digitally | New wallet, move everything | Immediate |
| Unrecognised browser extension | Remove it, then review approvals | Immediate |
| SMS-based two-factor authentication | Switch to an authenticator app | This week |
| Reused password on email | Change it and enable app-based 2FA | Immediate |
If the seed phrase has been exposed, the wallet is finished. Revoking approvals will not help, and the only response is a new wallet with a new seed phrase and moving everything to it.
The quarterly checklist
The whole audit fits on a single page, and it is worth keeping it there so the sequence does not depend on remembering it. Twenty minutes, once a quarter, and the list below is the whole of it.
Work through it in order. The seed phrase check comes first, because it is the one whose failure mode is permanent.
| # | Check | Why |
|---|---|---|
| 1 | Seed phrase storage | The failure mode is permanent |
| 2 | Approvals review | Unlimited approvals do not expire |
| 3 | Device hygiene | A compromised device defeats every other control |
| 4 | Account security | Two-factor authentication and recovery options |
| 5 | Address list | A short verified list removes the moment of copying |
| 6 | Withdrawal routes | Confirm you can still get money out |
Print the list and work through it in order. The seed phrase check comes first, because it is the one whose failure mode is permanent.
The audit log
An audit is only useful if you can tell what changed since the last one. A dated log of what you checked and what you changed turns a routine into a record, and the record is what makes the next audit faster.
The log does not need to be elaborate. A dated note with the checks and the changes is enough, and it is worth keeping it somewhere you will find it in three months.
- Date every audit and record what you checked.
- Record what you changed, and why.
- Record anything you decided not to change, and why.
- Note any new device, account or address added since the last audit.
- Keep the log somewhere you will find it in three months.
- Review the previous log before starting the next audit.
A dated log turns a routine into a record. It is what makes the next audit faster, and it is what shows you what changed when something goes wrong.
Safety Audit: Questions About Each of the Four Areas
Check Your Wallet's Exposure: Safety Audit Method
Paste your address into the tracer to see its recent activity and confirm nothing has moved that you did not authorise.
Primary sources and further reading
- CISA — Cybersecurity Best Practices www.cisa.gov
- FTC — How to Protect Your Accounts consumer.ftc.gov
- Chainalysis — Crypto Crime Report www.chainalysis.com
- NIST — Digital Identity Guidelines pages.nist.gov
External links open in a new tab and are provided so you can verify the underlying material yourself. TrueMoneyTalk is not affiliated with these organisations.
More prevention tutorials on wallet hygiene
Someone you know may be in this situation right now.
Disclaimer: this guide is general information, not legal, financial or recovery advice, and it is not a substitute for advice from a licensed professional in your jurisdiction. Individual outcomes vary and are never guaranteed.