GitHub malicious-dependency incident touching protocol deps
Hyperliquid's assessment for RD-F-160 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Hyperliquid's auditable surface (Bridge2.sol) uses OpenZeppelin AdminUpgradeabilityProxy — a well-maintained, actively monitored library. The L1 node software uses a closed-source binary; dependency audit is not possible. Python SDK (hyperliquid-python-sdk) is a user-facing tool, not a protocol security-critical dependency. No GitHub security advisories flagging malicious dependencies in hyperliquid-dex org repos identified as of assessment date. Signal does not fire.
Sources #
- Curator noteSource for RD-F-160retrieved 2026-04-28
- https://github.com/hyperliquid-dex/contractsretrieved 2026-04-28
Methodology #
Determine whether a security advisory flags a malicious release in a dependency consumed by this protocol.
See the full factor methodology and distribution across all protocols →