BlogEcosystem

Hyperliquid Security: A Guide for Traders and Builders

Secure your Hyperliquid account in self-custody: keys, API wallets, approvals and multi-sig. Plus a checklist for teams building apps on Hyperliquid.

HydromancerTeam
Hyperliquid Security: A Guide for Traders and Builders

There's nothing worse than having whatever you built or made stolen overnight. You can be extremely careful, yet, it only takes one mishap to catch you offguard and all of your assets are gone.

In October 2025, one Hyperliquid user lost about $21 million after a private key leak, according to the security firm PeckShield. On Hyperliquid, your wallet key is your account, and whoever holds that key can act as you.

So Hyperliquid security comes down to two questions: which keys can act on an account, and who would notice if one did. In this guide, we'll answer both, for traders and for teams that build on Hyperliquid.

If you are a trader:

  • Your main wallet key can do everything. Keep it on a hardware wallet, and never type its seed phrase (the words that recreate the key) into a website.
  • Apps and bots trade with a second key, called an API wallet.
  • Read a request's name before you sign it. ConvertToMultiSigUser, for one, hands your account to other keys.
  • Check what has access. Five free requests show it.

If you are a builder:

  • Never ask for a seed phrase. Users approve your API wallet and your fee with their own wallet.
  • Name each API wallet, give it an expiry and never reuse its address.
  • Watch every way money leaves your users' accounts, not only withdrawals.

How we checked. On 14 November 2026 we read the permissions of 300 wallets that traded through one large Hyperliquid app, checked the 1,500 largest accounts on Hyperliquid's leaderboard for multi-sig and pulled that app's week of deposits, withdrawals and transfers. It's all public data.

On 15 November we tested API wallets, fee approvals, multi-sig and each signing request on Hyperliquid's testnet with throwaway wallets, and moved nothing on mainnet.

What self-custody means on Hyperliquid

Self-custody means you hold the key that moves your money, and no company holds a copy. In the words of Hyperliquid's help page: "Hyperliquid is non-custodial. Only someone with access to your private key or seed phrase can sign transactions on your address' behalf."

That means:

  • Your wallet, such as Rabby or MetaMask, is the login. There's no password and no two-factor option.
  • A leaked key can't be changed. Hyperliquid's advice is to treat the address as "burned" and move what's left to a new wallet.
  • Email login is still a wallet. The 6-digit login code goes to your inbox, so protect your inbox with a strong password and two-factor login. You can export the wallet's private key.

Hyperliquid has two parts: HyperCore, where trading happens, and HyperEVM, where smart contracts run. Your address is the same on both. Here's how they differ.

One thing to keep straight first: your main key isn't the only thing that can act on your account.

What can act on your Hyperliquid account

Five things can act on a Hyperliquid account, and only the first is your seed phrase.

What What it can do How it gets access How it's removed
Your main wallet keyEverything:
trade, withdraw,
transfer, and
approve
everything below
It's the key
your seed phrase
creates
It can't be.
Move your funds
to a new wallet
An API walletTrade for you:
place and cancel
orders, move
funds between
your own balances
and deposit into
vaults
Your main wallet
signs
ApproveAgent
On the API page
of Hyperliquid's
app. Don't wait
for it to expire
A builder fee approvalLets one app add
its fee to the
orders it sends
for you, up to a
cap you approved
Your main wallet
signs
ApproveBuilderFee
You can revoke it
at any time.
Hyperliquid's app
lists them on its
approvals page
Multi-sig signersEverything on
HyperCore, once
the account is
converted
The account signs
ConvertToMultiSigUser
Only the signers
can change it
back
A linked staking accountLock your
account, then
receive its funds
a year later
Your main wallet
links to it, to
share a staking
fee discount
It can't be.
Linking is
permanent

The API wallet row needs a closer look, since it's how apps and bots trade for you.

An API wallet (Hyperliquid's docs also call it an agent wallet) is a separate key that trades for your account, so an app or a bot never needs your main key. Withdrawals and sends to another address need the main wallet's signature. A stolen API wallet key is still dangerous: whoever holds it can trade your balance away, for example by buying from their own orders at a bad price.

Apps that trade for you work this way, Hyperliquid's own included: setting up trading there asks your wallet to sign ApproveAgent. All 300 wallets we sampled had at least one API wallet, and more than half had two or more.

Part 1: How to secure your Hyperliquid account

Start with the key that can do everything. Then move to what you add to it, and finally to fake sites and DMs.

1. Guard the seed phrase

Write your seed phrase down and keep it somewhere physical. Hyperliquid's help page says to never enter it into a website or share it with a "support" person. No real support desk asks for it.

2. Use a hardware wallet

A hardware wallet keeps your key on a separate device, where you press a button to approve each request. Hyperliquid's help page names Ledger, Trezor and Keystone, paired with a browser wallet like Rabby. The device approves an API wallet once, then that key signs your orders from the app or browser. So the device guards withdrawals and approvals, not each trade.

OneKey's hardware wallets work this way in OneKey's own app.

3. Keep savings and trading apart

Use one wallet for trading and another for money you don't touch. If the trading wallet's key leaks, the loss stops at what was in it.

4. Give bots and apps an API wallet, never your key

If a bot, a script or an app asks for your main private key, stop. It should ask your wallet to approve an API wallet instead (our Hyperliquid API guide shows how).

  • One named API wallet per bot, so you can remove one without stopping the others.
  • Limit what it can reach. Run a bot on a separate wallet, or on a sub-account (a second account under the same wallet, open after $100,000 of trading), holding only what it needs.
  • Set an expiry. The maximum is 180 days.
  • Remove the ones you don't use. Each is a live key that can trade your account. 21 of the 300 wallets we sampled listed more than three named ones, and 2 listed 23. The limit starts at three and rises with trading volume.

5. Consider multi-sig for a large or shared account

A multi-sig account can require signatures from several keys before it acts, so one stolen key isn't enough. HyperCore has it built in, with up to 10 signers per account.

Of the 1,500 largest accounts on Hyperliquid's leaderboard, each worth about $1.9 million or more, 30 are multi-sig (2%), including 8 of the top 100. Together they held about $925 million, more than half of it in one account. The most common setup, on 12 of them, is 2 of 3: any two of three signers must agree.

Two cautions:

  • You can lock yourself out if you can no longer gather enough signers.
  • It covers HyperCore only. Hyperliquid's docs say the original wallet still controls the account's HyperEVM side, and that multi-sig users should not use HyperEVM at all.

Hyperliquid lets you link a trading account to a separate staking account, so the HYPE tokens locked up there lower your trading fees. Its docs warn that the staking account can then lock the trading account with one irreversible request and receive its funds a year later. The link is permanent: only link two accounts that are both yours. Trading and staking from one address needs no link.

Hyperliquid's own list:

  • Bookmark the sites you use, and beware of sponsored links in search results.
  • Assume most DMs are scams, above all one that asks you to install something.
  • Don't download unknown apps, or PDFs from strangers.
  • Keep your browser and its extensions up to date.

A key that never leaks can still sign the wrong request, so the next thing to guard is what you sign.

Part 2: Read what your wallet asks you to sign

Hyperliquid's help page says to read every transaction you sign, and not to sign without enough information. Every app uses the same request names, and wallets that show signing details display them, written like HyperliquidTransaction:Withdraw. The main ones that grant access or move money:

Request name What you're agreeing to Check before you sign
ApproveAgentThe key in agentAddress
can trade on your account
You're setting up trading
or adding a bot right
now, on a site you trust
ApproveBuilderFeeThe app at builder can
add a fee of up to
maxFeeRate to your orders
The rate is what
the app told you
Withdrawamount USDC goes to
destination on Arbitrum
The destination is
an address you chose
UsdSend, SpotSendamount goes to destination
on Hyperliquid
You meant to pay
that address
SendAssetA token moves to
destination. Apps also
use it to move funds
between your own balances
The destination is
yours, or one you chose
UsdClassTransferUSDC moves between your
own spot and perp balances
Nothing leaves your account
ConvertToMultiSigUserThe keys listed in signers
take over the account
You are setting up
a multi-sig
yourself, right now
LinkStakingUserThe staking account in user
is linked to yours for good
Both accounts are yours
Agent with a connectionIdA trading action, or
an account action such
as a vault deposit,
shown only as a string
of letters and digits
You can't read it, so sign
it only on an app you trust

The last row is the odd one. Orders, and a few account actions such as a vault deposit, aren't signed in a readable form. That's why apps trade through an API wallet: your main wallet then only signs requests you can read.

A HyperEVM transaction can do the same jobs. A transaction to Hyperliquid's contract at 0x3333333333333333333333333333333333333333 can add an API wallet, approve a builder fee or send tokens, showing none of the names above. If you don't know why a site wants one, don't sign it.

That covers what you sign from now on. What about access that's already there?

Part 3: Check what has access to your Hyperliquid account

In Hyperliquid's app, the API page lists your API wallets and lets you remove them, and the Builder Code Approvals page lists the apps you've approved a fee for.

You can also ask Hyperliquid's API, free and with no key. Send each of these to https://api.hyperliquid.xyz/info with your own address:

json
{"type": "webData3", "user": "0xYourAddress"}
{"type": "extraAgents", "user": "0xYourAddress"}
{"type": "approvedBuilders", "user": "0xYourAddress"}
{"type": "userToMultiSigSigners", "user": "0xYourAddress"}
{"type": "userFees", "user": "0xYourAddress"}

What a healthy account returns:

webData3

Under userState, agentAddress is your unnamed API wallet, if any (one an app set up without a name), and agentValidUntil is its expiry. It isn't in the next list. If you can't place it, set up trading again on an app you trust: a new unnamed API wallet replaces the old one. If you never set up trading anywhere, an address there means a leaked key: go to Part 6.

extraAgents

Your named API wallets, each with a name and an expiry. Every name should be an app or a bot you use. An expired one can still work, so remove it as well.

approvedBuilders

The address of each app you've approved a fee for. 294 of the 300 wallets we sampled had approved exactly one. For the cap you gave an app, send maxBuilderFee with your address as user and the app's as builder. The answer is in tenths of a basis point, so 1000 means 1%.

userToMultiSigSigners

null. Anything else means the account is a multi-sig. None of the 300 was.

userFees

stakingLink is null unless the account is linked to a staking account.

There are two places to revoke. Hyperliquid's hack checklist sends you to revoke.cash, which removes smart contract permissions on HyperEVM and other chains. API wallets and builder fee approvals live on HyperCore, and you remove those in Hyperliquid's app.

Part 4: Hyperliquid security for builders

If you run an app, a bot or a tool on Hyperliquid, your users' safety is partly your design. If you only trade, read step 5 below, then skip to Part 5.

1. Never hold a user's main key

Your app needs two approvals from a user's own wallet: an API wallet, so you can trade for them, and a builder fee, if you charge one. Nothing else. A bot can trade for every user without seeing one main key. Explain each approval on screen before the wallet prompt appears, and send every trade through the API wallet.

2. Handle trading keys with care

The API wallet keys you hold are the most sensitive thing on your servers. From Hyperliquid's docs:

  • Name each one and give it an expiry. Add valid_until and a timestamp after the name, at most 180 days ahead.
  • Never reuse an address. The docs "strongly" advise against it: once an API wallet is removed, Hyperliquid can forget which of its requests it has seen, and old signed requests can then be replayed.
  • One key per process. Hyperliquid tracks used request numbers per signing key, so two processes sharing one trip over each other.
  • Plan for renewals. 65 of the 647 named API wallets in our sample expire within 30 days, so users will see your "approve again" screen often.

Keep the keys in a key manager or a signing service, never in a config file or a log.

Default settings leak keys too. In November 2025, the security firm SlowMist found more than 1,000 copies of NOFX, an open-source AI trading bot, online with default or weak settings. Many would hand their keys, Hyperliquid keys included, to anyone who asked. Change every default secret before you deploy, and never let an API send a key back.

3. Protect your own keys

  • Your builder address never signs an order, so keep its key off servers. Orders only name it. It needs 100 USDC in its perps account and collects your fees.
  • Keep data API keys on your server. They can't move funds, but don't ship one in a web page or a mobile app.

4. Protect your front door

Your users are told to bookmark your site and distrust DMs. Help them:

  • Lock your domain and social accounts with hardware keys.
  • Publish one list of official links.
  • Say you never message first or ask for a seed phrase, and treat anyone offering "support" in your chat as a scammer.

5. Guard the computer you build on

Your own computer holds the keys, so attackers go after it.

Fake packages. In July 2026, someone put a package called @wagni_bot/hyperliquid on npm, the main store for JavaScript code, dressed up as a Hyperliquid toolkit. Installing it was enough: it read the computer's .env files (where many projects keep keys), SSH keys and wallet files, and sent them to the attacker over Telegram, according to GitHub's security advisory. It was one of 25 fake crypto packages from the same publisher, and it's no longer on npm.

Files that open themselves. In November 2026, Harley Foote, CEO of hyperliquidated.dev and a Hyperliquid trader, said a file sent to his WhatsApp downloaded on its own and gave an attacker full control of his computer. The attacker waited five days, tested a $10 withdrawal, then closed his positions and withdrew everything from Hyperliquid. "Nothing flagged it," he wrote.

  • Get SDKs from the links in Hyperliquid's docs, and check the exact name and publisher of every package before you install it.
  • Commit your lockfile, the file that pins each package version, so an install can't quietly pull in something new.
  • Keep funded keys off the computer you code and chat on. Your main key belongs on a hardware wallet. A .env file should only hold keys with small balances.
  • Turn off automatic downloads in chat apps on that computer.
  • Alert on every withdrawal, even a small one. Part 5 shows how.

Part 5: Watch for activity nobody asked for

Good keys fail too, so the second half of security is noticing fast.

That's the second question from the top: who would notice? In the WhatsApp hack in Part 4, a $10 test withdrawal came before the real one, and nothing flagged it.

What to watch

Money leaving. Over one week, money left the HyperCore balances of one large app's users 1,264 times:

  • 134 withdrawals through Hyperliquid's bridge
  • 974 sends to another Hyperliquid address
  • 147 sends to HyperEVM, where the funds stay under the same address
  • 9 deposits into a vault

An alert that only watches withdrawals would have seen 11% of it. Don't alert on every send, though: 765 sends went to one address that 352 users paid into. Alert on a destination the account has never sent to before.

Permission changes. A new API wallet, fee approval, multi-sig conversion or staking link isn't a money movement, so no feed of deposits and transfers shows it. Re-check them with the five requests above, on a schedule.

Watch one account or many

How you watch depends on how many accounts you're responsible for.

One account. Hyperliquid's API streams deposits, withdrawals and transfers for one address per subscription, and its docs allow 10 users per IP address (roughly, per server). The whale tracker guide shows how to subscribe.

Every user of your app. Past a handful of accounts, you can poll each user, process Hyperliquid's raw node data yourself, or use one feed for all of them. Hydromancer added such a feed, builderApprovedNonFundingLedgerEvents, which isn't part of the original Hyperliquid API. Give it your builder address, and it sends every deposit, withdrawal and transfer by the users who approved your fee, covering each new user from the moment they approve you:

json
{
  "type": "subscribe",
  "subscription": {
    "type": "builderApprovedNonFundingLedgerEvents",
    "builder": "0xYourBuilderAddress"
  }
}

Send it after connecting to wss://api.hydromancer.xyz/ws?token=YOUR_KEY, from your server. Each event names the user, their role, such as sender or receiver, and a delta with the type, amount and destination.

Related requests:

History

builderApprovedNonFundingLedgerUpdatesByTime returns the same events for a past period: the week above, for 1,208 users, took 3 requests. Both were first built for VALR.

A list you choose

userNonFundingLedgerEvents takes a list of addresses on one connection. Use it for accounts that must stay covered: a user who revokes your fee approval drops out of the stream above.

Everything

allUserNonFundingLedgerEvents sends every such event on Hyperliquid, about 72 a minute when we listened. It's for security tools and for following stolen funds.

Part 6: What to do if your Hyperliquid account is hacked

An alert tells you something happened. If it wasn't you, the steps below are what to do.

Hyperliquid's help page lists the signs: transactions you didn't make, missing funds, or "an unknown multi-sig on your Hyperliquid account". Its steps:

  1. Stop using the address. Treat it as burned for good.
  2. Create a new wallet with a provider you trust.
  3. Move whatever is left to it, from every app you used, HyperEVM assets included. Those can still move even if your HyperCore account was converted into a multi-sig you don't control.
  4. Revoke smart contract permissions at revoke.cash, and clear your browser's cache and cookies.
  5. Work out how it happened, and check your device for malware.

Three cases need more.

You know that only an API wallet leaked, for example because a bot's operator told you. Your main key is safe, so you don't need a new wallet. Remove the API wallet on the API page, cancel orders you didn't place, check your positions and vault deposits, and run the five checks above. If anything else changed, or money left the account other than through trades or a vault deposit, treat it as a leaked main key.

A multi-sig you didn't set up. A multi-sig can have a single signer: 2 of the 30 we found are controlled on HyperCore by one key other than the account's own. Set up by the owner, that moves an account to a new key. Signed by mistake on a fake site, it's a takeover, so never sign ConvertToMultiSigUser in a hurry.

A staking link you didn't set up. It can't be undone, and the staking account can lock your funds. Move everything to a new wallet before the staking account locks it.

If your app leaks a trading key

In November 2026, HyprEarn, an app that trades for users through API wallets, reported trades its users hadn't placed on a small number of accounts. It dropped every API wallet it held, reminded users an API wallet can trade but can't withdraw, and asked them to remove the old one on Hyperliquid's API page and approve a fresh one. By 16 November it hadn't said how it happened. That's steps 1 and 2 below:

  1. Ask every affected user to approve a replacement. Only a user's main wallet can remove an API wallet, and a new one under the same name replaces the old at once. Don't count on expiry: Hyperliquid's docs don't say how soon an expired API wallet is cleared, and in our testnet test an expired key was still placing orders 20 minutes after its expiry, when we stopped checking.
  2. Tell your users what the key could and couldn't do.
  3. Cancel open orders you didn't send.
  4. Re-check every account with extraAgents and webData3.
  5. Review the hours the key was exposed for sends to destinations your users had never used.

If you hold funds in multi-sig accounts and lose a signer device, which accounts can that key sign for? Hydromancer's multiSigsBySigner returns the multi-sig accounts an address signs for, with the other signers and the number required. Hyperliquid's API works the other way round, from an account to its signers. In our scan, 3 signer addresses each signed for three of the 30 accounts.

What changes with Hydromancer?

For one account, nothing. Hyperliquid's app and free API show everything in this guide, and that's where to start.

Hydromancer is a read-only data layer: it can't sign, trade or move funds, so every order, approval and withdrawal still goes through Hyperliquid. What it adds is scale: one feed for every user who approved your app, many addresses on one connection, and a lookup from a signer to its multi-sig accounts. The permission checks answer the same on both APIs.

Whichever API you use, the two questions from the top stay the same. The five requests show what can act on an account, and Part 5 is how you'd notice activity nobody asked for.

FAQ

Does Hyperliquid have 2FA?

No. You log in with a wallet, so there's no password to protect. A hardware wallet adds a button press, multi-sig adds keys, and email login users should turn on two-factor for their email.

Can an API wallet withdraw from Hyperliquid?

No. A withdrawal needs the main wallet's signature, but a stolen API wallet can still lose money through trades.

Can I use a Ledger with Hyperliquid?

Yes, paired with a browser wallet like Rabby. Hyperliquid's help page names Ledger, Trezor and Keystone.

What happens if I lose my Hyperliquid seed phrase?

If the wallet is still on a device, move your funds to a new wallet and write down its seed phrase. If not, nobody can restore the key. With email login, log in with the code and export it.

Can Hyperliquid recover a hacked account?

No. A leaked key can't be changed, so move what's left to a new wallet.

Is Hyperliquid safe?

This guide covers the part you control: your keys and your approvals. For the exchange itself, Hyperliquid has an audits page and runs a bug bounty program.

Sources

#1: Hyperliquid docs, I got scammed/hacked
#2: Hyperliquid docs, Nonces and API wallets
#3: Hyperliquid docs, Exchange endpoint
#4: Hyperliquid docs, Builder codes
#5: Hyperliquid docs, Multi-sig
#6: Hyperliquid docs, How to start trading
#7: Hyperliquid docs, Export your email wallet
#8: Hyperliquid docs, Rate limits and user limits
#9: Hyperliquid Python SDK, signing
#10: Hyperliquid leaderboard file
#11: PeckShield on X, 10 October 2025
#12: The Block, $21 million stolen from Hyperliquid user, 10 October 2025
#13: Fordefi docs, Sample Hyperliquid Policy rules
#14: Revoke.cash, HyperEVM Token Approval Checker
#15: Hydromancer docs, builderApprovedNonFundingLedgerEvents
#16: Hydromancer docs, multiSigsBySigner
#17: Hydromancer docs, Monitor approved builder users
#18: Hyperliquid docs, Fees (staking linking)
#19: Hyperliquid docs, Interacting with HyperCore
#20: Chainstack docs, Link staking user
#21: HyprEarn on X, security notice, 14 November 2026
#22: SlowMist on X, NOFX security analysis, 17 November 2025
#23: GitHub Advisory Database, malicious code in @wagni_bot/hyperliquid (GHSA-35jp-phg5-g2hr)
#24: Harley Foote on X, 13 November 2026
#25: Harley Foote on X, how the file arrived, 13 November 2026

Continue