Lighter's key exploit prompts questions over Hyperliquid agent permissions

Editorial illustration: Translucent tiles flow through an open brass hatch from a circular container into a tray. A magnifying glass enlarges the closed, keyed hatch of a second container.

In brief

  • Lighter's Nov. 16 update tied an account drain to exposed trading keys and public-pool shares.
  • Lighter said withdrawals resumed after a safeguard let about 5 million USDC be returned.
  • Bitquery traced a 10,393,057 USDC withdrawal but couldn't inspect internal rollup transactions.
  • CryptoSlate's analysis examines Hyperliquid's agent and vault permissions, without alleging any exploit.
  • DefiLlama put Hyperliquid's open interest at $5.7 billion, about 55% of the tracked total.

How the Lighter drain worked

According to Lighter's update as reported by CryptoSlate, the affected accounts used unsafe signing code outside its official software kits. Reused signing nonces let the attacker reconstruct API private keys from public signatures. Lighter said its protocol, contracts, infrastructure and official kits weren't affected.

The attacker created a public pool under the affected account, picked up shares through a second account, then moved victim funds into the pool without creating matching shares. Redeeming the existing shares let the money leave.

Lighter said wallet signatures are now required for public-pool transfers. It's also made API signatures non-public and added IP allowlists and configurable limits.

Separately, Bitquery traced a 10,393,057 USDC withdrawal from Lighter's Ethereum contract the same day. That isn't a confirmed loss total (Bitquery couldn't inspect the internal rollup transactions or independently establish the reported second account loss).

Why Hyperliquid comes up

Size is the reason. DefiLlama's Nov. 16 snapshot put Hyperliquid's open interest at $5.7 billion, against nearly $554 million for Lighter and a tracked total of roughly $10.5 billion. That's about 10.3 times Lighter's size and roughly 55% of the market.

Hyperliquid's API-wallet documentation says a master account can authorize agents to sign for itself or its subaccounts, and its official agent example describes trading authority without transfer or withdrawal permissions. The exchange endpoint does allow an agent-signed asset transfer when the destination matches the source address. Hyperliquid also documents a vault-transfer function, which its Python SDK signs through a different path than external USDC transfers and bridge withdrawals.

What the analysis does (and doesn't) say

CryptoSlate's case rests on Hyperliquid's documentation, not on a reported incident.

CryptoSlate's Gino Matos argued that a comparable extraction would need both the relevant permissions and a matching share-accounting path. He also wrote that the documented internal transfers and vault functions give no basis for assuring that every agent-authorized vault path is impossible.

The risk he flags most isn't theft by withdrawal. A stolen agent with valid authority could open unwanted positions, change exposure or cause adverse execution, potentially exhausting an account's collateral without a single withdrawal to the thief. HLP losses would require relevant strategy or liquidation exposure, he wrote.

Liquidity matters here too. DefiLlama's exchange snapshot showed about $1.4 billion of aggregate dollar-perpetual depth within 2%, with far less in individual markets.

Frequently asked questions

How did the attacker drain funds from Lighter?

Lighter said reused signing nonces in unsafe third-party signing code let the attacker reconstruct API private keys. The attacker created a public pool under the affected account, bought shares from another account, moved victim funds in without creating shares, then redeemed the existing shares.

Has Hyperliquid been exploited the same way?

No such incident is reported. CryptoSlate's analysis says a comparable extraction would need both the relevant permissions and a matching share-accounting path, but argues Hyperliquid's documented vault functions don't support a blanket assurance that every agent-authorized path is impossible.

What changes did Lighter make after the exploit?

Lighter said wallet signatures are now required for public-pool transfers, API signatures have been made non-public, and IP allowlists and configurable limits have been added. Withdrawals resumed after a safeguard allowed about 5 million USDC to be returned.