@devmikets/hyperliquid-sdknpm
@devmikets/hyperliquid-sdk is a confirmed malicious npm package (MAL-2026-14042) that typosquats a legitimate package to trick installs (malicious version 1.9.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @devmikets/hyperliquid-sdk (npm)
What this malware does
package.json declares inquirer with a tarball URL pointing at registrynpmjs.to — a domain that typosquats the official npm registry (registry.npmjs.org). Running npm install fetches and installs whatever tarball is hosted at that attacker-controlled URL as a transitive dependency, delivering arbitrary code into the installer's node_modules on every install. The package otherwise mimics a legitimate Hyperliquid TypeScript SDK (README shape, @nktkas/rews dep, jsr.io/@std references), and inquirer (an interactive-prompt library) is not a normal runtime dependency for a trading SDK, indicating the entry exists as a delivery vector rather than a functional dependency.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @devmikets/hyperliquid-sdk (version 1.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @devmikets/hyperliquid-sdk across your stack and pipelines.
If you installed it — respond
@devmikets/hyperliquid-sdk is a typosquat — you almost certainly intended a legitimately-named package. Remove @devmikets/hyperliquid-sdk, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @devmikets/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 @devmikets/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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @devmikets/hyperliquid-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.