This crypto account security checklist helps you audit every route into an exchange or trading account, from authentication and email recovery to active sessions, trusted devices and API keys. Use it before moving larger balances, connecting a new tool, changing phones or responding to a suspected phishing attempt.
Overview
Security is not limited to choosing a strong password. A crypto account can be exposed through a reused email password, an old browser session, a forgotten API key, a compromised phone number or a trading application with more permissions than it needs. The safest audit treats the account as a collection of access paths and checks each one separately.
Start with the exchange or custodian’s official website or mobile application. Do not follow a security link from an unsolicited email, direct message or search advertisement. Platform menus vary, so the labels below may appear under names such as Security, Privacy, Account access, API management or Devices.
Record what you find without storing passwords, seed phrases or full authentication secrets in the checklist. If you see an unfamiliar login, withdrawal, API key or device, stop routine activity and follow the platform’s official account-compromise procedure. For a broader response plan, see Crypto Security Incident Response.
| Access control | What to check | Practical guidance |
|---|---|---|
| Passkey | Which devices or password managers hold the passkey? | Use only devices you control and remove entries you no longer recognize. |
| Hardware security key | Are registered keys named and accounted for? | Keep a separately stored backup key if the platform supports it. |
| Authenticator app | Is the code generator on a controlled device? | Protect the app and its recovery process; do not share one-time codes. |
| SMS | Is a phone number used for login or recovery? | Treat SMS as a fallback where possible and secure the mobile account separately. |
| Backup codes | Do codes exist, and where are they stored? | Keep them offline and private; replace them after use or exposure. |
| Withdrawal allowlist | Are permitted addresses current? | Remove old destinations and understand any waiting period before relying on the feature. |
| Active sessions | Which browsers, apps and locations are listed? | End sessions you do not recognize or no longer need. |
| API permissions | Can each key trade, withdraw or read account data? | Disable withdrawals unless essential, and delete unused keys. |
| Email recovery | Can the email account reset access? | Secure the mailbox with strong authentication and review forwarding rules. |
| Device trust | Which phones and computers are trusted? | Remove lost, shared, repaired or retired devices. |
Checklist by scenario
Routine quarterly audit
- Open the exchange’s security dashboard and review recent login history, active sessions, trusted devices and security notifications.
- Confirm that your primary email uses a unique password and strong multifactor authentication. Check mailbox forwarding, filters and recovery addresses for changes you did not make.
- Review every authentication method. Prefer a passkey or hardware security key where supported and practical. Keep an authenticator app or documented recovery method available without leaving secrets in an exposed note.
- Inspect withdrawal settings, address allowlists and any new-address delays. Remove destinations you no longer use, but verify the effect before saving changes.
- Export or record a non-sensitive inventory of API keys, connected applications and their purpose. Delete keys with no current owner or business need.
Before connecting a trading bot, portfolio tracker or tax tool
- Install the tool only from its official source and verify the domain before authorizing access.
- Create a dedicated API key when possible. Grant the minimum permissions required: read-only access for monitoring, or trading access only when execution is necessary.
- Do not enable withdrawals for a third-party tool unless you have a specific, well-understood reason and accept the added risk.
- Set an expiration date, IP restriction or other control if the platform provides it. Save the key label and owner in a private inventory, not the secret itself.
- After testing, confirm that the tool performed only the expected actions. Delete the key when the project ends.
After changing phones, computers or email addresses
Before retiring the old device, add and test the new authentication method while you still have an approved recovery route. Then remove the old device, passkey, authenticator registration and active sessions. Change the exchange password if the old device was lost, shared or repaired. Update the account email only through the official settings flow and expect additional verification or withdrawal restrictions.
When you suspect phishing or unauthorized access
Stop clicking links and do not approve login prompts you did not initiate. Use a known bookmark or manually typed official domain to sign in, change the email and exchange passwords from a clean device, revoke unfamiliar sessions and disable unknown API keys. Contact official support through the platform’s published channel. If funds or a self-custody wallet may be affected, prioritize containment over investigating the attacker yourself.
What to double-check
Authentication is only as strong as recovery. A powerful primary login can be undermined if an attacker controls the associated email account, phone number or backup codes. Confirm that recovery details are current, that codes are stored offline and that no one else can access the device or password manager holding them.
API labels can be misleading. Read the permission description on the platform, not just the name you assigned to a key. Separate read-only, trading and withdrawal capabilities. A key that was created for a dashboard may still retain permissions from an earlier use.
Sessions and devices are different from passwords. Changing a password may not remove every existing session or trusted device. Review both lists and use the platform’s option to sign out everywhere when you cannot identify an entry.
Withdrawal controls need a testable plan. Allowlists and address locks can reduce risk, but they may also delay legitimate transfers. Verify which assets, networks and account types they cover, and confirm how you would make an emergency change.
Separate trading access from long-term custody. Keep only the balance needed for active trading or connected applications in an exchange account where practical. Review How to Choose and Migrate Crypto Wallets when evaluating a different custody arrangement.
Common mistakes
- Using the same password for an email account and a crypto exchange.
- Accepting an unexpected login prompt because it appears to be a routine notification.
- Saving seed phrases, backup codes or API secrets in screenshots, email drafts or cloud notes.
- Leaving old API keys active after stopping a bot, changing vendors or closing a project.
- Granting withdrawal permission when a tool only needs balances or trade execution.
- Assuming a familiar device name proves ownership; names can be duplicated or unclear.
- Using a search result or social-media message to reach support during a stressful incident.
- Waiting for a breach announcement before reviewing access. An account audit is preventive maintenance, not only an emergency response.
When to revisit
Run a full audit at least once each quarter and a focused review whenever an access path changes. That includes buying a new phone, losing a device, changing your email, installing a new browser, adding a trading tool, moving to a different exchange or increasing the balance held online. Revisit the checklist after a phishing attempt, suspicious notification, password-manager alert or security incident involving a platform you use.
Also review it when an exchange changes its authentication options, API permission labels, recovery process, withdrawal rules or device-management screens. Platform instructions can change, so confirm the current procedure in the official help center rather than relying on an old screenshot or third-party tutorial.
Printable action list: open the official security page; review email security; confirm primary MFA and recovery; end unknown sessions; remove untrusted devices; delete unused API keys; reduce permissions; check withdrawal allowlists; update your private inventory; and record the date of the next audit. If any item cannot be verified, treat it as unresolved and contact official support before moving funds or authorizing another connection.