Lighter DEX Hack Explained: How Leaked API Keys Led to a $10.39 Million Exploit
2026-11-17
The Lighter DEX hack hit the market on November 16, 2026, when an attacker drained 10.39 million USDC from a single trader's account through leaked API keys.
The twist is that Lighter's smart contracts were never broken.
The attacker rebuilt the trader's API keys from public signatures, because the trader's own signing code reused nonces.
This guide explains how the exploit worked, how much was stolen, what was recovered, and why the LIT token dropped.
Key Takeaways
- An attacker withdrew 10,393,057 USDC from Lighter after recovering a trader's API keys from public signatures.
- The Lighter protocol and smart contracts were not affected, and Guardian mode helped return about 5 million USDC to the trader.
- LIT fell more than 10% after the news and remains about 20.65% lower over seven days.
What Happened to Lighter DEX?
Lighter first flagged a security incident on November 16, saying it appeared to involve a single compromised external party.
As a precaution, the exchange temporarily suspended all withdrawals and pool creation.
A later update traced the incident to a leaked API key for a specific trader's account.
Here's what Lighter confirmed in that update:
- The Lighter protocol and smart contracts were unaffected.
- Guardian mode was enabled on the smart contract, with the Lighter Security Council performing the upgrade.
- The main priority was recovering funds involved in an additional withdrawal attempt by the attacker.
- The wallet believed to belong to the attacker is 0xb3fffca23d4444eE73349825ACD84f7b5020e387.
Lighter also said the affected accounts were linked to market makers' APIs.
Later that day, Lighter announced that deposits and withdrawals were back to normal after the Security Council deactivated Guardian mode.
How Much Was Stolen in the Lighter Hack?
The traced withdrawal stands at 10,393,057 USDC, or about $10.39 million.
The attacker's account deposited $20,000 into Lighter, then withdrew the $10.39 million roughly 36 minutes later, with the funds leaving Lighter's Ethereum contract at 10:11 UTC.
Here's how the stolen funds moved:
- Most of the USDC was swapped into ETH through CoW Swap within minutes.
- About 1,920 ETH, worth roughly $3.5 million, was then sent through 12 wallets to Hyperliquid in transfers of 160 ETH each.
- Those wallets bought XMR1, a token named after the privacy coin Monero.
At one snapshot, about 4,484 ETH worth roughly $8.12 million was still sitting in the attacker's main wallet.
Some researchers estimated potential losses closer to $15.5 million across two market maker accounts, although Lighter has not confirmed that figure.
How Did Lighter Get Hacked?
Lighter got hacked through the victim's own signing code, not through a bug in the exchange.
The affected accounts used signing code other than the official Lighter SDKs, and that code reused signing nonces, which made their private API keys recoverable from public data.
Because signatures on Lighter were public, the attacker needed no access to the accounts or to Lighter's systems.
The next step exploited how pools are treated.
An API key can send funds to its own account's sub accounts, and a public pool created by that account counts as one.
Here's how the attacker drained the account:
- The attacker created a public pool from the affected account.
- The attacker minted pool shares in a separate account under their control.
- The attacker transferred the victim's funds into the pool, raising its NAV without minting new shares.
- The attacker redeemed their shares and withdrew the funds.
This route sidestepped a core rule of how the Lighter protocol works, where an API key can only withdraw to the account owner's own wallet.
How Does Nonce Reuse Leak API Keys?
Every Lighter transaction is authorised by a signature from an API key.
Each signature relies on a one off random value called a nonce, which must be unique and unpredictable every time.
If the same nonce is used with the same key to sign two different transactions, anyone can calculate the private key from those two public signatures.
This weakness is not unique to Lighter, since the same principle applies to Bitcoin and Ethereum signatures.
Here's why weak nonces are dangerous:
- Nonces derived from timestamps, counters, transaction contents or cached values can repeat without the developer noticing.
- Weakly seeded random number generators can produce predictable values.
- Once a nonce repeats, the exposed key can no longer be trusted and needs to be rotated.
Lighter's official SDKs generate every nonce with a cryptographically secure random number generator, which is why they were not affected.
Sign up on Bitrue to trade LIT and other major assets on a regulated exchange.

Did Lighter Recover Stolen Funds?
Lighter recovered part of the funds, but not the full $10.39 million.
Its smart contract Guardian was triggered by the anomaly and temporarily paused withdrawals.
That pause allowed the Lighter Security Council to return about 5 million USDC to the affected trader.
Lighter had earlier named the funds involved in the attacker's additional withdrawal attempt as its main recovery priority.
Lighter has not announced any recovery of the $10.39 million that had already left its contract and moved towards Hyperliquid.
Guardian mode has since been disabled, withdrawals are unpaused, and pending withdrawals are being processed.
Why Did LIT Token Drop Today?
LIT dropped because traders reacted to the security headline and the withdrawal freeze.
The token fell more than 10% to below $2.48 shortly after the incident, before recovering to around $2.62 later that day.
At the time of writing, the LIT price sits near $2.63, down 2.46% over 24 hours after swinging between $2.34 and $2.78.
That intraday range of nearly 19% shows how quickly traders repriced platform risk as the news developed.
LIT's market capitalisation stands at about $680.42 million, while the token is down roughly 20.65% over seven days.
According to Bitrue Research Institute, the partial rebound suggests the market sees this as an account level security failure rather than a protocol failure, although sentiment may stay fragile until the new API protections go live.
What is Lighter Changing After the Exploit?
Lighter has already shipped two fixes and announced several more.
Here's what has changed so far:
- Transferring funds to a public pool now requires a wallet signature, so an API key alone cannot do it.
- API key signatures are no longer public.
Here's what Lighter is adding next:
- IP allowlists will let a key work only from the server its owner chooses.
- Configurable permissions and limits per API key will control which actions a key may take and which markets it can trade.
- Lighter will monitor signatures for nonce reuse, contact affected accounts directly and proactively void exposed API keys.
Programmatic traders should sign with an official Lighter SDK in Python, Go, TypeScript or the Agent Kit.
Anyone unsure whether their code has ever reused a nonce should rotate every API key and switch to an official SDK.
How to Trade LIT on Bitrue
LIT is listed on Bitrue, giving traders a regulated venue to react to Lighter news without writing their own signing code.

The process takes only a few minutes.
- Create an account and complete KYC: Register on Bitrue and verify your identity to unlock full trading features.
- Fund your account: Deposit crypto or buy USDT with a supported payment method.
- Browse the markets: Search for the LIT/USDT pair on the spot or futures market.
- Place a market or limit order: Use a market order for instant execution or a limit order to set your preferred price.
- Decide on self custody: Keep LIT on Bitrue for active trading or move it to a personal wallet for long term holding.
Beginners can buy LIT on Bitrue through the spot market, where there is no leverage or liquidation risk.
Experienced traders can then consider LIT futures with strict position sizing, since volatility around security news can move fast.
Conclusion
The Lighter DEX hack shows how a small coding mistake outside the protocol can still cost millions.
An attacker used reused nonces to rebuild a trader's API keys, then routed 10.39 million USDC out through a public pool.
Lighter's contracts held, Guardian mode helped return about 5 million USDC, and new API protections are on the way.
For traders, the lesson is to use official tools, protect every key and choose venues with strong security practices.
Bitrue offers a regulated way to trade LIT and other major assets, with spot, futures and AI strategies on one platform.

FAQ
How Did Lighter Get Hacked?
An attacker recovered a trader's API keys from public signatures because the trader's own signing code reused nonces.
How Much Was Stolen in the Lighter Hack?
About 10.39 million USDC was withdrawn through the affected trader's account on November 16, 2026.
Did Lighter Recover Stolen Funds?
Lighter's Guardian mechanism helped return about 5 million USDC to the affected trader, while no recovery of the withdrawn $10.39 million has been announced.
Was the Lighter Protocol Hacked?
No, Lighter said its protocol, smart contracts and infrastructure were not affected.
Why Did LIT Token Drop Today?
LIT fell more than 10% as traders reacted to the exploit and the temporary withdrawal freeze.
Disclaimer: The views expressed belong exclusively to the author and do not reflect the views of this platform. This platform and its affiliates disclaim any responsibility for the accuracy or suitability of the information provided. It is for informational purposes only and not intended as financial or investment advice.
Disclaimer: The content of this article does not constitute financial or investment advice.





