Malicious code in @2oolkit/hyperliquid-cli (npm)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @2oolkit/hyperliquid-cli
- Affected
- >= 0.2.1, <= 0.2.1>= 0.2.2, <= 0.2.2>= 0.2.7, <= 0.2.7>= 0.2.6, <= 0.2.6>= 0.2.5, <= 0.2.5>= 0.2.4, <= 0.2.4>= 0.2.3, <= 0.2.3>= 0.2.0, <= 0.2.0>= 0.1.0, <= 0.1.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-3679 lists affected ranges: npm @2oolkit/hyperliquid-cli >=0.2.1 =0.2.2 =0.2.7 =0.2.6 =0.2.5 =0.2.4 =0.2.3 =0.2.0 =0.1.0 <=0.1.0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (1c3af30011dcf54950f270463028270d732fce20b5cd5da44342a0748922e6df) The package is advertised as a neutral CLI/MCP wrapper for Hyperliquid, but its distributed code silently routes value from the installer to an author-controlled address. In dist/index.js and dist/mcp.js, the constants BUILDER_ADDRESS = 0xa6f967d47c6f85a5ba4fc43543e5e1c171cccf98, BUILDER_FEE = 1 (0.01%), and REFERRAL_CODE = '2OOLKIT' are hardcoded. On `config init` / `config set --private-key...`, a fire-and-forget `silentAutoSetup(env, privateKey, walletAddress)` signs and submits (a) a `setReferrer('2OOLKIT')` transaction and (b) an `approveBuilderFee(0xa6f9...cf98, '0.1%')` transaction on the user's Hyperliquid account, with errors swallowed so the user sees no indication. Additionally, `HyperliquidClient.placeOrder` unconditionally injects `action.builder = { b: BUILDER_ADDRESS, f: BUILDER_FEE }` into every order, so every…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-3679
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-qg83-c6x5-qw8f Advisory: Malicious code in @2oolkit/hyperliquid-cli (npm) IDs: GHSA-qg83-c6x5-qw8f Record: https://patchnext.com/advisories/mal-2026-3679 (revision 1, source checked 11 Nov 2026, 06:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @2oolkit/hyperliquid-cli: affected >= 0.2.1, <= 0.2.1; >= 0.2.2, <= 0.2.2; >= 0.2.7, <= 0.2.7; >= 0.2.6, <= 0.2.6; >= 0.2.5, <= 0.2.5; >= 0.2.4, <= 0.2.4; >= 0.2.3, <= 0.2.3; >= 0.2.0, <= 0.2.0; >= 0.1.0, <= 0.1.0 ## Suggested inspection (read-only) - `npm ls @2oolkit/hyperliquid-cli --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @2oolkit/hyperliquid-cli. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-3679 (OSV record MAL-2026-3679 lists affected ranges: npm @2oolkit/hyperliquid-cli >=0.2.1 =0.2.2 =0.2.7 =0.2.6 =0.2.5 =0.2.4 =0.2.3 =0.2.0 =0.1.0 <=0.1.0) Commands are suggestions: review each one before running it.
Loading voting…