Hyperliquid

Hyperliquid trading bots on GitHub: telling real code from malware

Hyperliquid names one official SDK and a short list of community ones. Everything else you find searching GitHub for a Hyperliquid trading bot needs its own check, because real malware campaigns have used fake GitHub repos and Hyperliquid-named packages to find victims. Here is what Hyperliquid itself points to, what has actually gone wrong, and how to lower the risk if you run someone else’s code anyway.

[

November 16, 2026

]
•
[

14

 

min to read

]

The short answer

Hyperliquid names one official SDK, for Python, at github.com/hyperliquid-dex, and a short list of community SDKs its own docs link to by name. Everything else on GitHub needs its own check: real malware has shipped as fake GitHub repositories and npm packages, some of them typosquatting the names of trusted developers.

What makes a Hyperliquid bot on GitHub official, and what does not?

Hyperliquid’s own organization on GitHub, github.com/hyperliquid-dex, held 11 public repositories when we read it on November 16, 2026: the Python SDK, the software that runs a validator or a regular node, the audited bridge contracts, two stats repos, a Rust SDK, a folder of TypeScript examples, and a few smaller infrastructure tools. Sitting in that org is a real signal. It is not the only one worth checking.

Hyperliquid’s developer docs list SDKs on their own API page, and only one of them lives in Hyperliquid’s own organization: the Python SDK, at the same address. For every other language, the page sends you somewhere else entirely. Its Rust SDK is described as “written by community member, Infinite Field,” hosted at github.com/infinitefield/hypersdk, a different GitHub account altogether, not the hyperliquid-rust-sdk repo that happens to sit inside hyperliquid-dex itself (475 stars, last updated October 2025, and not the one the current docs page points to). Its two TypeScript options, by developers named nktkas and nomeida, are community-maintained and live outside the org too. CCXT, a library that speaks to many exchanges at once, gets a third-party mention of its own.

The lesson sits in that mismatch. An address inside the official org is worth something, but it is not the whole test, and an address outside it is not automatically a problem; what matters is whether today’s docs page, read on the date you are checking, actually names the repo in front of you.

What do Hyperliquid’s own SDK READMEs actually tell you to do?

We read each repo’s README directly rather than take someone’s word for it. A few things stand out.

  • The Python SDK leads with a key-safety instruction, before any trading code. Its README has you copy a config file and fill in two separate fields: account_address, your main wallet’s public address, and secret_key, a private key to sign with. Right under that, an optional step tells you to generate a fresh key on app.hyperliquid.xyz/API instead, and to put that key in secret_key while still putting your main wallet’s public address, “not the API wallet,” in account_address. Getting that one line backwards is an easy way to confuse the two.
  • The Rust SDK’s README is a few lines long. Install it, look in one folder for examples, MIT license. Thin documentation is not malware by itself, but it is also not a reason to assume this is “the” Rust SDK just because of where it lives; the docs page, as covered above, names a different one.
  • The TypeScript folder is honest about not being an SDK. Its README calls itself “Sample scripts/snippets for computing various frontend values” and then names and links the two real community SDKs. A repo that tells you plainly what it is, and points you past itself, is a good sign in general.
  • Even the node software is distributed as a signed download. The node repo, for running a validator or a regular Hyperliquid node, has you import a published public key with gpg and check it against a signature file before you run the binary. That is the standard Hyperliquid holds itself to for its own infrastructure: a key you can check a download against, not a file you just trust.

None of this is a security feature built for GitHub browsers; it is how a careful team documents its own code. Reading it costs a few minutes and tells you more than a star count ever will.

What malware campaigns have really used fake GitHub repos?

This is not a hypothetical. Kaspersky’s security research team has documented two campaigns that show the two different shapes the risk takes: a fake repo built to look real, and a real, popular package turned hostile after the fact.

GitVenom: repos built to look real

Kaspersky’s GitVenom report, published February 24, 2025, found hundreds of fake GitHub repositories posing as useful tools, including an Instagram automation tool, a Telegram bot for managing Bitcoin wallets, and a cheat for the game Valorant. Each one carried a convincing, well-written README, and a timestamp file rewritten every few minutes inflated the number of commits, so the repo looked busy and maintained. The code itself hid its payload differently by language: encrypted in Python, Base64-encoded in JavaScript, buried in a Visual Studio project file in C, C++ and C#.

Once installed, victims got a Node.js stealer that gathered saved credentials, cryptocurrency wallet data and browsing history and shipped it out over Telegram, plus backdoors (AsyncRAT and Quasar) and a clipboard hijacker that swapped a copied wallet address for one the attackers controlled. One of those attacker addresses alone took in about 5 BTC, roughly $485,000 at the time of Kaspersky’s research, in a single payment in November 2024. Kaspersky observed infection attempts worldwide.

Shai-Hulud: a real, trusted package turned hostile

Kaspersky’s report on the Shai-Hulud worm, published September 25, 2025, describes a different shape entirely: no fake repo to spot, because the packages were already real, already popular, and already installed. The worm read a victim’s npm and GitHub access tokens, used a secrets-scanning tool with AWS and GCP helpers to grab whatever credentials it could reach, and pushed what it found to a new repository, named “Shai-Hulud,” created right on the victim’s own GitHub account. Then it modified that same victim’s 20 most-downloaded packages to carry the same payload, bumped each one’s version number and republished it, so every newly infected machine turned around and poisoned the packages other developers would install next. Kaspersky counted more than 500 npm packages caught in it, including one, @ctrl/tinycolor, with more than two million weekly downloads, and nine packages published under the security firm CrowdStrike’s own name.

Neither campaign targeted Hyperliquid by name, but together they are exactly the two risks a Hyperliquid trading bot’s dependencies carry: a repo dressed up to look like what you searched for, and a package you already trusted turning on you without you touching a line of your own code.

Fake packages that do target Hyperliquid by name

GitHub runs its own Advisory Database, and a search for “hyperliquid” malware there, on November 16, 2026, listed 10 malware advisories across 7 distinctly named npm packages. One of them is the clearest lesson in this whole guide: a package published as @nklkas/hyperliquid, a one-letter swap of nktkas, the handle behind the real, widely used TypeScript SDK named on Hyperliquid’s own docs page and published on npm as @nktkas/hyperliquid. Type the name from memory, or copy it from a search result instead of the docs page, and that single swapped letter is the entire difference between the real SDK and a package GitHub itself has flagged as malware.

How do you vet a Hyperliquid repo before you run its code?

  1. Match the exact name against today’s docs page.

    Before anything else, check whether the package name, spelled exactly, appears on Hyperliquid’s own API docs page. A one-letter difference, as above, is the whole trick.

  2. Check who, not only where.

    A repo inside github.com/hyperliquid-dex is a real signal, and one outside it is not automatically a problem: the community SDKs the docs recommend both live elsewhere. Either way, open the author’s other work and history; a name with nothing behind it but this one repo is a reason to slow down.

  3. Read the code, not just the README.

    GitVenom’s repos had polished READMEs and fake, auto-updated commit history. Stars and forks can be bought or faked too. Open the files that actually trade or handle a key, and look for anything that runs automatically on install, downloads a separate binary, or calls itself a “loader.”

  4. Pin it, with a lockfile.

    Shai-Hulud spread by republishing a slightly newer version of a package already on people’s machines. A pinned, lockfile-checked dependency cannot be swapped out from under you by a later update alone.

  5. Keep your main key out of it completely.

    Whatever you decide to run, give it a Hyperliquid API wallet, never your seed phrase or your main private key. The next section covers exactly what that key can and cannot do.

  6. Try it on testnet first.

    Run anything new with no real funds anywhere near the process, on a machine that holds no other keys, before it ever touches mainnet.

How do API wallets cap the damage if you run bad code anyway?

Even careful vetting can miss something, which is why the key you hand to any Hyperliquid bot matters as much as the code itself. Hyperliquid’s own API page describes an API wallet, also called an agent wallet, as a key that “can perform actions on behalf of an account without having withdrawal permissions.” It can place orders, change leverage and move your own USDC between your own balances. It cannot send money to anyone else’s address, and it cannot approve another API wallet in your place; only your main wallet can do either of those.

Hyperliquid’s API wallet docs set the limits that make this a leash rather than an open door:

  • A short, countable list. One unnamed API wallet and up to three named ones per account, plus two more named ones per sub-account.
  • An expiry date you choose. Per the exchange endpoint docs, “the expiration can be at most 180 days in the future.” Set a short one for anything you are not fully sure of.
  • It only signs; it cannot answer for your account. The docs are explicit: “API wallets are only used to sign. To query the account data associated with a master or sub-account, you must pass in the actual address of that account.”
  • Never reuse an old one. Once a wallet is deregistered or has expired, Hyperliquid may prune its record of used nonces, and the docs warn plainly: “previously signed actions can be replayed once the nonce set is pruned.” A tool you stopped trusting should get a fresh key next time, not the same one.

Put it into practice this way: give every piece of outside code its own named API wallet, never one shared with anything else, so a bad tool’s worst case is exactly that one key and nothing more. Remove it from the API page in the app the moment you stop trusting the code behind it, instead of leaving it live “just in case.” And keep the limit of this protection in view: an API wallet stops someone from draining your account to another address, but it can still lose your money through bad trades, because it can still trade. It caps the damage; it does not remove the risk of running code you have not read.

If you already ran something you now doubt, or you see activity you did not start, Hyperliquid’s own guidance for a compromised account is the same regardless of what caused it: stop using that address, move what is left to a wallet created fresh, and undo any smart-contract permission it was ever given, with the approval checker that page links to, before you trust that device again.

What are the safer ways to run a Hyperliquid bot than a random repo?

A few routes put a traceable name behind the code, instead of a GitHub username you have never heard of:

  • Hyperliquid’s own SDK, and your own code on top of it. Start from the official Python SDK and write the strategy yourself; our Hyperliquid API guide walks through the requests, the API wallet setup and the rate limits in full, and our Claude Code trading guide covers writing that code with an AI assistant and the permissions to set first.
  • Established open-source frameworks with years of history. Projects such as Hummingbot and Freqtrade are run by named organizations with a long public record, not a single anonymous repo. Our guide to Hyperliquid trading bots covers how those connect and how each kind of bot tends to fail.
  • A hosted platform with a company’s name on it. You still check what key it asks for, but a company with a support line and a track record carries a different kind of accountability than a repo with 20 stars from last week. Our comparison of Hyperliquid trading bots lists several, with what each one asks for.
  • An AI trading agent, so you never run anyone else’s trading code yourself. This is the route Ethy takes, covered next.

None of these removes every risk Hyperliquid itself carries, such as leverage or a market moving fast; our guide to whether Hyperliquid is safe covers those separately. They remove the specific risk this guide is about: code whose author you cannot name.

How does Ethy avoid this problem altogether?

Ethy is an AI trading agent you ask before you trade, reached in a browser or app rather than cloned from a repository. You never download, run or trust someone else’s trading code to use it, which sidesteps the whole question this guide is about.

Under the hood, its Hyperliquid orders go through the kind of key this guide recommends. When you activate it, Ethy is set up to sign for your wallet from its servers, which is how automations run while you are away, and it creates its own API wallet, named ethy-perps, which your wallet approves. That API wallet places the orders; its private key is stored encrypted on Ethy’s servers rather than published anywhere, and it is renewed automatically rather than left to quietly lapse. Ethy is software for research and analysis, so it does not give investment advice, but it can read a chart on four timeframes, look into why a market moved, and test a rule on past data, before you decide whether any bot, including one you found on GitHub, is worth trusting with real money.

Summary

  • Hyperliquid names one official SDK, for Python, at github.com/hyperliquid-dex, and a short list of named community SDKs; its Rust SDK lives in a different GitHub account entirely.
  • Read the actual READMEs: the Python SDK warns you, in its setup steps, not to mix up your main wallet’s address with an API wallet’s key.
  • Kaspersky documented GitVenom (February 2025), fake repos with stolen wallet data and a clipboard hijacker that took in about $485,000 in one payment, and the Shai-Hulud npm worm (September 2025), which turned real, trusted packages hostile and spread through more than 500 of them.
  • GitHub’s own Advisory Database listed 10 malware advisories across 7 npm packages, 6 of them named after Hyperliquid, on November 16, 2026, including a one-letter typosquat of a real community SDK’s maintainer handle.
  • Vet a repo against the current docs page, by author rather than by star count, by reading the code rather than the README, and on testnet before mainnet.
  • A Hyperliquid API wallet can trade but, per Hyperliquid’s own API page, cannot withdraw; give each tool its own, expiring key, and remove it the moment you stop trusting the code.
  • On Hyperliquid, Ethy places orders through its own encrypted, automatically renewed API wallet, and never asks you to run anyone else’s trading code.

Questions people ask

Is there an official Hyperliquid trading bot on GitHub?

Hyperliquid names one official SDK, for Python, at github.com/hyperliquid-dex, which you can build a bot on top of yourself. It is not a ready-made bot; it is the toolkit the docs point to for talking to the exchange. Hyperliquid’s docs also name community SDKs for other languages, by author, which live outside that same GitHub organization.

How do I know if a Hyperliquid bot on GitHub is safe?

Check its name against the SDK list on Hyperliquid’s own current API docs page, check who actually maintains it and for how long, and read the trading code itself rather than trust its README or its star count. Real malware campaigns have used polished READMEs and inflated activity to look trustworthy, so none of those surface signals proves anything on their own.

Has malware really been found in Hyperliquid-related GitHub repos or npm packages?

Yes. Kaspersky’s GitVenom report, though not aimed at Hyperliquid, documented fake repos, including one posing as a Telegram Bitcoin wallet bot, that stole wallet data and hijacked clipboards. GitHub’s own Advisory Database separately listed malware advisories for several npm packages named after Hyperliquid, including one that typosquats the handle of a real community SDK’s maintainer by a single letter.

Can a fake Hyperliquid bot steal my funds even if I use an API wallet?

An API wallet cannot withdraw or send funds to another address, per Hyperliquid’s own API documentation, so it blocks the most direct kind of theft. It can still place real trades, so malicious or broken code behind that key can still lose your money through bad orders. Treat it as a way to cap the damage, not a reason to skip vetting the code.

What is npm supply-chain malware, and does it affect Hyperliquid bots?

It is malicious code smuggled through a package your bot installs as a dependency, sometimes by compromising a package that was already legitimate, as Kaspersky’s Shai-Hulud report describes. A Hyperliquid bot written in JavaScript or TypeScript installs npm packages the same way any other project does, so the same risk applies to its dependencies, not only to the bot’s own code.

How do I vet a GitHub repo before running a Hyperliquid bot from it?

Match its exact name against Hyperliquid’s current docs page, check the author’s history beyond this one repo, read the actual trading code rather than the README, pin dependencies with a lockfile, and run it on testnet with an API wallet before any real funds are near it. Never your seed phrase or main private key, on any bot.

Sources

  1. GitHub: hyperliquid-dex organization (repository list, read November 16, 2026)github.com
  2. Hyperliquid Docs: API (the SDK list)hyperliquid.gitbook.io
  3. hyperliquid-python-sdk, the official Python SDK (GitHub)github.com
  4. Hyperliquid Docs: Nonces and API walletshyperliquid.gitbook.io
  5. Hyperliquid Docs: Exchange endpoint (API wallet expiry)hyperliquid.gitbook.io
  6. Hyperliquid Docs: I got scammed/hackedhyperliquid.gitbook.io
  7. Kaspersky Securelist: The GitVenom campaign (February 24, 2025)securelist.com
  8. Kaspersky Securelist: Massive npm infection, the Shai-Hulud worm (September 25, 2025)securelist.com
  9. GitHub Advisory Database: malware advisories matching “hyperliquid” (read November 16, 2026)github.com
  10. npm: @nktkas/hyperliquid package pagenpmjs.com

Trading involves risk, including the loss of your money. Ethy AI is a research and trading tool and does not give investment advice or recommendations. Backtests are simulations on historical data and do not predict future results.

Ethy blog

Read more

The $ETHY ecosystem

Stop watching charts.
Start living.

Deploy your AI trading agent in one click.