Pionex Guide

How to Run an Exchange Account Security Checklist Without Missing the Layer That Drains You

Most exchange account security checklists stop at the password. Attackers don't. They look for the gap you left open somewhere else: the inbox that can reset your login, the session you forgot to kill, or the API key you created for a bot six months ago and never revoked. A working checklist covers four layers — the login, the email behind it, the devices and keys that can reach it, and the withdrawal path where money actually leaves.

Layer 1: The login is the start, not the finish

A strong, unique password is the baseline. It's also the part most people get right, which is why it's rarely the thing that gets an account drained. The second factor is where accounts actually fall.

Choose a hardware key or authenticator app over SMS

SMS codes can be intercepted through SIM-swap fraud, where a criminal convinces your carrier to port your number to a new SIM. Authenticator apps and hardware security keys don't have that weakness. On Pionex, as on most major exchanges, you can enable app-based two-factor authentication (2FA) and, where offered, a hardware key. Turn on the strongest option available to you.

Store your 2FA backup codes offline

When you set up 2FA, the exchange gives you recovery codes. Screenshot them and you've put your backup in the same phone a thief might take. Write them down or print them and keep them somewhere physical and separate. A password manager works too, as long as it isn't protected by the same phone-only 2FA.

Layer 2: Lock down the email address behind the account

Your exchange login is only as safe as the inbox that can reset it. If someone gets into your email, they can trigger a password reset and, in some setups, intercept verification links.

Give your email its own strong second factor

The same rules apply: a unique password and app-based 2FA on the email account itself. Don't reuse a password you use anywhere else. If your email provider offers passkeys or hardware-key support, use it.

Watch for forwarding rules you didn't create

A favorite attacker move is to slip a silent forwarding rule into your inbox so they see your exchange notifications without ever logging in as you. Open your email settings and scan for auto-forwarding or filter rules you don't recognize. Remove anything that isn't yours.

Layer 3: Audit devices, sessions, and API keys

Exchanges usually show you a list of active sessions and authorized devices. That list is a security tool, not a curiosity. Review it monthly, and read it carefully — a session from a city you've never visited is worth a password change on the spot.

  • Log out of sessions on devices you don't recognize, and change your password if anything looks off.
  • Remove old API keys you created for bots or tools and no longer use.
  • Restrict any API key to the permissions it actually needs. A trading bot usually doesn't need withdrawal rights.
  • Turn off API keys entirely if you've stopped running automated strategies.

That last point matters more than people think. An API key with withdrawal permission is a password that never expires and often skips 2FA. If you run bots through a platform like GridHarbor Bots connected to Pionex, check what scope those keys were granted. Withdrawal access should be off unless you have a specific, current reason for it.

Layer 4: Guard the withdrawal path specifically

Everything above protects the login. This section protects the money, and it's the part a checklist often skips.

Use address whitelisting and withdrawal locks

Most exchanges let you whitelist withdrawal addresses and enable a withdrawal lock that blocks transfers for a set period after a security change. Turn both on. A whitelist means even a compromised login can only send funds to addresses you already approved.

Enable anti-phishing codes and login alerts

An anti-phishing code is a phrase you set that appears in genuine exchange emails, so a fake one stands out. Login alerts tell you the moment someone signs in from a new device. Both are free and take a minute.

Here's the scenario worth sitting with. A trader reuses one password across a forum and his exchange, skips app-based 2FA because SMS felt easier, and keeps an old API key with full permissions from a bot he stopped running months ago. A SIM swap and that stale key are two separate doors into the same account. Either one, closed, changes the outcome. Fixing both is a twenty-minute job.

Frequently asked questions

Is SMS 2FA good enough for an exchange account?

It's better than nothing, but it's the weakest common second factor because phone numbers can be hijacked through SIM-swap fraud. If app-based 2FA or a hardware key is available, switch to it. Keep SMS only as a fallback if the exchange requires a phone number.

How often should I review my exchange security settings?

Once a month is a reasonable rhythm for checking active sessions, API keys, and whitelisted addresses. Do it immediately after any security change, a new device, or a period where you shared account access with a tool. Small, regular checks beat one big annual audit.

Should my trading bot's API key have withdrawal permission?

Almost never. A bot needs to read balances and place orders, not move funds out. Grant only the permissions the strategy requires and revoke the key when you stop using it. A withdrawal-enabled key is one of the most valuable things an attacker can find.

Set a calendar reminder for this weekend and walk through the four layers once, starting with the session list. Twenty minutes now beats a recovery ticket later.