Malicious Code Vulnerability in hyperliquid-composer Package

hyperliquid-composer Updated 01 Sep 2026

Summary

31/08/2026
CRITICAL
No i
Critical
Not published

MAL-2026-15627: Malicious code in hyperliquid-composer (npm). Affects hyperliquid-composer versions 1.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The hyperliquid-composer package is an npm module designed for developers to facilitate interactions with Hyperliquid tooling. It is intended to streamline the development process by providing various utilities. However, this package has been identified to contain malicious code that compromises user data without consent.

Vulnerability Detail

The vulnerability originates from the bin/cli.js file within the hyperliquid-composer package. This file collects sensitive information, including the installer's username, hostname, and platform details, using the whoami and os.userInfo() functions. This data is then sent to a hardcoded Cloudflare Workers endpoint without user consent or configuration. The malicious behavior triggers upon requiring the module or invoking the CLI, posing significant risks to user privacy and security.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall hyperliquid-composer

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can avoid using the hyperliquid-composer package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the risk of malicious code.

Conclusion

The hyperliquid-composer package has been identified to contain malicious code that poses significant risks to user privacy. It is crucial for users to take immediate action by updating or removing the package and monitoring for any updates from the maintainers.

See every vulnerability recorded for hyperliquid-composer →

Share this vulnerability

FAQ

The malicious code collects sensitive user information and sends it to an external server without consent.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code.

If you have installed hyperliquid-composer, it is recommended to uninstall it immediately and check for updates or alternatives.

Currently, there is no patch available for the identified vulnerability. Users should monitor the package repository for updates.

Using hyperliquid-composer can lead to unauthorized data exfiltration, compromising user privacy and potentially exposing sensitive information.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall hyperliquid-composer

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback