Which versions of @wagni_bot/hyperliquid-sdk are malicious?

The following npm versions of @wagni_bot/hyperliquid-sdk are flagged malicious: 1.0.0, 1.1.0, 1.1.1, 1.1.3, 1.1.4, 1.1.5, 1.2.0. Treat any of these as compromised.

How do I remediate @wagni_bot/hyperliquid-sdk if I installed it?

@wagni_bot/hyperliquid-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @wagni_bot/hyperliquid-sdk — how do I know if it already compromised me?

If @wagni_bot/hyperliquid-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @wagni_bot/hyperliquid-sdk part of a known attack campaign?

Yes — @wagni_bot/hyperliquid-sdk is associated with the IN-MAL-2026-009045, IN-MAL-2026-009077, IN-MAL-2026-009052, IN-MAL-2026-009044, IN-MAL-2026-009066, IN-MAL-2026-009059, IN-MAL-2026-009034 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @wagni_bot/hyperliquid-sdk across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wagni_bot/hyperliquid-sdk (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wagni_bot/hyperliquid-sdk across your stack and pipelines.

Malicious package

@wagni_bot/hyperliquid-sdknpm

Malicious code in @wagni_bot/hyperliquid-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10026

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @wagni_bot/hyperliquid-sdk

What this malware does

The package is scoped and named to impersonate the Hyperliquid exchange SDK (@wagni_bot/hyperliquid-sdk) but ships no SDK code — only a harvester in postinstall.js that is wired to run automatically on npm install via both preinstall and postinstall lifecycle hooks. On install, the script scans the installer's home directory, Desktop, Documents, Downloads, /root, and /tmp for wallet-related artifacts (id.json, wallet.json, keystore.json, metamask.json, phantom.json, seed.txt, mnemonic.txt,.env, credentials.json,.npmrc,.git-credentials,.netrc), reads Solana/Ethereum keystores, ~/.ssh/ private keys, ~/.aws/credentials, ~/.git-credentials, and Chrome/Brave/Edge MetaMask and Phantom extension Local Extension Settings directories. It additionally reads user.txt/.md/.rtf/.csv files, tokenizes their content, and if 10 or more tokens match a BIP39 wordlist, uploads the file. All collected contents, along with hostname, username, and cwd, are POSTed to hardcoded endpoint http://107.161.90.180:7777. The package name impersonation targets crypto developers looking for the legitimate Hyperliquid SDK.

Malicious versions

7 flagged

1.0.01.1.01.1.11.1.31.1.41.1.51.2.0

Indicators of compromise (SHA-256)

1e14d014ce531c2ac67ad2161b85f8d80cd36d832a75498261c7e6a732d84e03

acb65c5406a7548eb967eaf83b160f0e4e7ec41540795e25c81fd899471da7ad

ad42a5ae741ef707d93ea139f44d4e092a7e636821f842246c9c5c3d4da02a04

ca6ec83c9621f8afc9616d49876cc451ca8d99397d99288889b81298eb410d7e

ee985df6bea9ffe959983fde092d996bd1bfc088d88364f0dd55839c033f301a

2adf8fbb987c388f63095955c060414b8b7bc6406393856c50a4d3d045936d2c

5a0924176ca46558d5c6f28aafb614e8271efdcf288a728176b6847853d76386

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wagni_bot/hyperliquid-sdk (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wagni_bot/hyperliquid-sdk across your stack and pipelines.
If you installed it — respond
@wagni_bot/hyperliquid-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @wagni_bot/hyperliquid-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @wagni_bot/hyperliquid-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @wagni_bot/hyperliquid-sdk on npm has been identified as a malicious package (versions 1.0.0, 1.1.0, 1.1.1, 1.1.3, 1.1.4, 1.1.5, 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009045IN-MAL-2026-009077IN-MAL-2026-009052IN-MAL-2026-009044IN-MAL-2026-009066IN-MAL-2026-009059IN-MAL-2026-009034

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wagni_bot/hyperliquid-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring