Which versions of hyperliquid-composer are malicious?

The following npm versions of hyperliquid-composer are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hyperliquid-composer if I installed it?

hyperliquid-composer 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 hyperliquid-composer — how do I know if it already compromised me?

If hyperliquid-composer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hyperliquid-composer part of a known attack campaign?

Yes — hyperliquid-composer is associated with the IN-MAL-2026-019307, GHSA-5v7v-27c5-fr8q 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 hyperliquid-composer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hyperliquid-composer (version 1.0.0).

Malicious package

hyperliquid-composernpm

Advisory published Aug 31, 2026Updated Sep 3, 2026

hyperliquid-composer is a confirmed malicious npm package (MAL-2026-15627) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hyperliquid-composer (npm)

MAL-2026-15627

Immediate action

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

npm uninstall hyperliquid-composer

What this malware does

bin/cli.js (also declared as the package main) collects the installer's username via whoami / os.userInfo(), plus os.hostname() and platform, and POSTs them to the hardcoded Cloudflare Workers endpoint https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9. The exfiltration fires on require() of the module or on CLI invocation, with no user consent or configuration. The package name resembles legitimate Hyperliquid tooling.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1fb2b7d17a47aa4fcd585374f33063197f52d6ba8619e4105ae5a1d30331bb62

2f8645d3f313a1fa2b7d0fcf6e4aa3f896c73fa51fc2ee845eab9aaf1645a287

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for hyperliquid-composer (version 1.0.0).
If you installed it — respond
hyperliquid-composer 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 hyperliquid-composer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hyperliquid-composer on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019307GHSA-5v7v-27c5-fr8q

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hyperliquid-composer-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

Explore

All malware advisories How O3 detects malware Vulnerability database