If you keep crypto on an exchange, you do not hold the private keys yourself. What you control is the account: the password, the email address behind it, the second factor and the withdrawal settings. That is where crypto exchange account security is won or lost, and it is what an attacker goes after.
This guide is not an exchange ranking and not a seed-phrase tutorial. It covers account-level defences and a short first-response checklist. It is educational only, not financial, legal or security-audit advice, and no setting guarantees safety. Crypto withdrawals are generally irreversible: if an attacker moves your funds, you may not get them back. Keeping assets with any custodial provider also carries platform risk, which we explain in what happens to your crypto if an exchange fails.
Why the exchange login is the real “key” for custodial crypto
On a custodial exchange, the provider holds the keys that move funds on-chain. Your login, your password-reset route and your two-factor method decide whether you, or someone else, can request a withdrawal.
That differs from self-custody, where you protect a recovery phrase. Here you protect credentials and the email account that can reset them. For how self-custody devices work, see hardware wallets explained. This piece stays on the exchange side.
Your exchange support team has no reason to ask for a wallet recovery phrase, your password or your 2FA codes. Coinbase, for example, states in its help centre that its agents will never ask for your password or 2-step verification code, never ask you to install software and never remotely access your device. If anyone asks for these, treat it as a scam: see how to spot crypto scams and, for offline storage of your own wallet’s phrase, seed phrase backup. Prefer an authorised provider and type the official address yourself; the basics are in how to check if a crypto exchange is licensed in the EU.
Strong, unique password and a separate email
Use a unique password for each exchange. Reused passwords turn one breach elsewhere into a working login here. Length and uniqueness matter more than clever substitutions. A password manager can help; NIST’s current digital identity guidelines (SP 800-63B-4) require services to allow password managers and autofill for exactly that reason.
Treat the email account as part of the exchange. Password resets, 2FA changes and device alerts usually go there. If that inbox is weak, a strong exchange password alone will not save you. Use an address you do not hand out for newsletters and shopping, give it its own strong password and second factor, and keep its recovery options under your control.
Avoid shared family logins, and do not save exchange passwords in a shared browser.
2FA methods compared by risk
Two-factor authentication (2FA) asks for something beyond the password. Not every method resists the same attacks. The table below is qualitative: it compares relative phishing resistance, exposure to SIM swaps and the effort of recovery where an exchange supports the option. It is not a product ranking, and no method is unbreakable.
| Method | Phishing resistance (relative) | SIM-swap / number hijack exposure | Recovery burden if you lose it |
|---|---|---|---|
| SMS codes | Low: codes can be phished or intercepted | High: tied to your mobile number | Usually easy through the mobile provider, which is also the weakness |
| Email codes | Low: whoever controls the inbox gets the code | Indirect: depends on email security | Easy if you still control the inbox; serious if you do not |
| Authenticator app (TOTP) | Medium: codes are generated on your device, but you can still type them into a fake site | Low for the code itself | You need backup codes or a second device; lose both and recovery is slow |
| Passkey | High for the login itself: it only works on the genuine site or app. Weaker fallback methods left on the account can still be phished | Not tied to SMS | Depends on the device or sync account; keep a second method where allowed |
| Hardware security key | High when used as a FIDO2/WebAuthn key (one-time codes generated by some keys can still be phished) | Not tied to SMS | You need a spare key or backup method; register a second key where allowed and store it separately |
This ordering matches official guidance. The US Cybersecurity and Infrastructure Security Agency (CISA) lists SMS and voice codes as vulnerable to phishing, SIM swaps and phone-network attacks, and describes app-based one-time codes as still vulnerable to phishing. NIST SP 800-63B-4 states that one-time codes, codes delivered out of band and backup codes are not phishing-resistant, and that WebAuthn (the standard behind passkeys and FIDO2 security keys) provides phishing resistance by tying the credential to the real domain. The UK National Cyber Security Centre (NCSC) concluded in April 2026 that all traditional methods, including SMS codes, email codes, app or token codes and push approvals, are “inherently phishable”, and that it now recommends passkeys wherever a service supports them, with two-step verification where it does not.
Prefer something stronger than SMS where the exchange offers it. SMS is better than nothing, as the NCSC also stresses, but a SIM swap or a phished code can defeat it. Authenticator apps avoid the phone-number route for the code itself. Passkeys and security keys go further by tying proof to the real service instead of a code you can be tricked into typing elsewhere. That protection only holds if an attacker cannot fall back to a weaker method, so check whether SMS is still set as a fallback or recovery option. Where the exchange allows it, remove SMS once a stronger method and offline backup codes are in place.
Do not email yourself backup codes. That creates a new inbox target. Store them offline somewhere only you control, for example on paper in secure storage, and treat them like passwords. Keep them out of shared cloud albums, chat apps and auto-synced photo libraries, and away from the place where your exchange password is stored. Do not photograph the setup QR code or secret key: a copy of it is a copy of your second factor. Backup codes are typically single-use, so generate a fresh set once you have used some.
Turn on 2FA on the exchange and on the email account behind it. Leaving either one without 2FA leaves a gap.
Passkeys and security keys in plain English
A passkey is a login credential based on FIDO standards that lives on your phone, computer or a hardware security key. Instead of typing a password plus a six-digit code, you approve the sign-in the same way you unlock your device (fingerprint, face or PIN), and your device proves to the real site or app that it is you. A lookalike domain cannot complete the same check, which is why the FIDO Alliance describes passkeys as phishing-resistant.
If your passkeys sync through a cloud account, that account becomes part of your exchange security. The NCSC names the strength of the authentication protecting the sync account as the key control, so give it a strong unique password and its own second factor. Anyone who can unlock your phone or computer may be able to use the passkeys on it, so use a device PIN or biometric and do not share your device unlock code.
A hardware security key is a small physical device you tap or plug in to confirm a login or sensitive action. The secret stays on the key, and confirmation needs you to be physically present. The FIDO Alliance notes that security keys can also act as a recovery credential if you lose the devices your synced passkeys live on.
Practical points that matter more than brand names:
- Availability varies. Not every exchange offers passkeys or security keys for every action (login, withdrawals, API). Use what your provider documents for your account.
- Keep a second method. One broken phone can lock you out. Where the platform allows a spare key, a second passkey device or offline backup codes, set that up before you need it.
- Register only through official settings. Add new factors from the exchange’s own security page after typing the address or using a bookmark, never from an email or chat link.
- Expect a temporary withdrawal hold after changes. Changing your password, 2FA or allowlist settings can trigger one. Kraken, for example, documents a hold on withdrawals to new addresses after a password change on accounts without sign-in 2FA or a Master Key. Make changes when you do not need to withdraw urgently, and confirm your backup factor works before you rely on it.
Menus and labels change, so follow your provider’s current help pages rather than old screenshots.
Withdrawal allowlists, address locks and cooling-off periods
Even with a strong login, a stolen session can still move funds unless withdrawals are restricted.
Many exchanges offer some version of:
- Withdrawal allowlist (whitelist): only addresses you have approved can receive funds.
- New-address delay: a waiting period before a newly added address can be used.
- Settings or withdrawal lock: a control that blocks changes or crypto withdrawals until you or the provider lift it.
- Anti-phishing code: a personal code shown in genuine platform emails. An email without it is a red flag, but its presence alone does not prove an email is genuine.
Three examples from official help pages, checked in November 2026, show how different these controls can look:
- Coinbase describes allowlisting that limits sends to addresses in your address book; a newly added address becomes available after 48 hours, and turning allowlisting off also takes 48 hours (unless done within 8 hours of switching it on).
- Kraken describes a Global Settings Lock that, while active, blocks adding withdrawal addresses, changing 2FA, changing your email address and adding API keys. Unlocking without a Master Key takes the waiting period you chose (1 to 29 days), and you get an email when an unlock is requested.
- Bitvavo describes an address book where new addresses are confirmed by email, an anti-phishing code, a withdrawal address whitelist, and a “Freeze withdrawals” button that stops crypto leaving the account until its fraud team lifts the freeze.
Feature names and details differ and can change. Treat these as examples of what to look for in your own provider’s settings, and confirm the details in its documentation. Not every platform offers every control.
Why allowlists help. Someone who gets into your account cannot simply withdraw to their own address; they first have to add it. Where adding an address needs your second factor or email confirmation and starts a waiting period, that delay gives you time to notice and lock the account. An allowlist does not help if the attacker also controls your 2FA or your email, so it works alongside a strong login, not instead of one. Turn on login, withdrawal and settings-change alerts, and use in-app notifications as well as email where offered.
Allowlists limit withdrawals, not trading. If you use API keys, give them only the permissions you need, avoid withdrawal rights unless they are essential, and restrict them to your own IP address where the platform offers it.
Before allowlisting an address, check it in full against the source, not just the first and last characters, and do not copy it from past transaction history. Make sure the network matches on both sides. Consider a small test withdrawal first; sent crypto usually cannot be reversed.
If you allowlist a self-hosted wallet, your exchange may ask you to show that you control it. Under the EU’s Transfer of Funds Regulation (Regulation (EU) 2023/1113), a crypto-asset service provider sending more than EUR 1,000 to a self-hosted address must take adequate measures to assess whether that address is owned or controlled by its client. That is separate from account hardening; for the details see the EU travel rule and self-hosted wallets.
SIM swap and phishing: two takeover routes to plan for
SIM swap and number porting. CISA describes a SIM swap as social engineering in which criminals convince a mobile provider to move your phone number to a SIM card they control. A fraudulent transfer of your number to another provider has the same effect. Either way, SMS codes and some voice-based resets can reach the attacker. Ask your mobile provider what extra protection it offers against unauthorised SIM changes and number transfers, such as a transfer PIN or extra identity checks, and use it. Options vary by country and provider, so rely on the provider’s own pages. Best of all, use 2FA that does not depend on SMS.
Phishing and fake support. Fake login pages, “security team” messages and lookalike apps harvest passwords and codes. Type the exchange address yourself or use a bookmark. Never approve a login or withdrawal you did not start. Nobody legitimate needs remote access to your device to “secure” your account. For fake-support scripts and other patterns, read how to spot crypto scams; this section stays on how takeovers happen.
Malware, fake apps and malicious browser extensions can also steal logged-in sessions. Install apps only from official sources and keep your devices updated.
Signs your account may be compromised and what to do first
Warning signs include login or withdrawal emails you did not trigger, 2FA or password changes you did not request, unknown sessions or devices, API keys you did not create, new withdrawal addresses you did not add, and a phone that suddenly loses mobile signal.
If you suspect a takeover, speed and official channels matter more than clever fixes:
- Open the exchange only via a bookmark or a typed address, not through links in the suspicious message.
- Use any freeze, lock or disable-withdrawals control in the app or website, or ask official support on that same verified site.
- Revoke unknown sessions and API keys.
- Contact support through the official channel, say you believe the account is compromised, and follow their steps. Do not hand control to anyone who contacted you first. Genuine support will not ask for your password, 2FA codes or recovery phrase.
- Secure the email account first, then the exchange password, from a device you trust. In the email account, check for forwarding rules, filters, recovery addresses or phone numbers you did not add. Change or re-register 2FA only through the exchange’s official process or as support directs, and do not remove your only working factor.
- If your phone suddenly lost signal, contact your mobile provider through its official channel about a possible SIM swap.
- Write down a short timeline (when you noticed, which emails, which devices) for support and for any later police report. If you later have a dispute with the platform itself, our guide on how to complain about a crypto exchange under MiCA explains the formal route.
Be wary of “recovery” services that contact you on social media or promise to unlock funds for an upfront fee. They are a known follow-up scam aimed at people who have just lost money; see how to spot crypto scams.
This is first aid, not a guarantee of getting funds back. Outcomes depend on timing, platform controls and the facts of the case.
A 10-minute security check you can repeat
Run this when you open an account, after any suspicious email, and every few months:
- Unique exchange password; the email account also has a strong password and 2FA.
- Exchange 2FA stronger than SMS if offered; SMS removed as a fallback where possible; backup codes stored offline, not in email.
- Passkey or security key if offered, plus a spare method.
- Withdrawal allowlist on for the addresses you use; new-address delays and lock features understood.
- Login, withdrawal and settings-change alerts on; anti-phishing code set if available.
- Sessions, devices and API keys reviewed; unknown ones revoked.
- Bookmark for the real domain; no saved exchange password on a shared device.
Moving long-term holdings into self-custody is one option once you understand the trade-offs. It is not required, and it brings its own risks. If you explore it, start with moving crypto from an exchange to a hardware wallet; self-custody mistakes are usually irreversible too.
In short
For custodial crypto, the account is the key. Use a unique password and a well-protected email account, prefer phishing-resistant sign-in such as passkeys or security keys over SMS where your exchange supports it, and restrict withdrawals with allowlists and delays. Plan for SIM swaps and phishing. If something looks wrong, lock what you can and contact the provider through an official channel, never through a stranger who messaged you first.
Sources: NIST SP 800-63B-4 digital identity guidelines; CISA fact sheet on implementing phishing-resistant MFA; NCSC blog: passkeys are more secure than traditional ways to log in; NCSC guidance on setting up two-step verification; FIDO Alliance overview of passkeys; Regulation (EU) 2023/1113 on information accompanying transfers of funds and crypto-assets; help pages from Coinbase on allowlisting and support impersonation scams, Kraken on the Global Settings Lock and new withdrawal addresses, and Bitvavo on freezing crypto withdrawals and its security features. Information as of November 2026. Exchange security menus, 2FA options and withdrawal controls change; check your provider’s official documentation. Not financial, legal, or security advice.
This article has no affiliate links. Our Affiliate Disclosure explains how we handle partner links when we use them.

