@wagni_bot/hyperliquid-sdk
Unofficial hyperliquid-sdk SDK
This report shows the evidence for @wagni_bot/hyperliquid-sdk@1.0.0. 8 of 8 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection confirms an install-time lifecycle script performs unconsented credential, SSH key, wallet/seed, and environment secret exfiltration to Telegram. This is concrete malicious behavior unrelated to a Hyperliquid SDK, especially because index.js exports only an empty object.
Decision evidence
public snapshot- package.json defines install-time hook: postinstall runs node postinstall.js.
- postinstall.js sends install host/user/cwd/platform data to Telegram during installation.
- postinstall.js recursively reads sensitive files from process.cwd(), os.homedir(), and ~/.ssh.
- postinstall.js filters process.env for SECRET/TOKEN/API_KEY/PASSWORD/AWS and sends values externally.
- index.js is empty, offering no legitimate SDK behavior to justify the install hook.
- No destructive file writes or persistence found.
- No child_process, eval, dynamic require, or native binary loading found.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @wagni_bot/hyperliquid-sdk@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/hyperliquid-sdk@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.