Update, 17 November 2026, 05:47 UTC: Lighter reopened withdrawals on the evening of 16 November, between about 16:41 and 18:31 UTC going by the publication times of CoinDesk and TokenPost. In a post-mortem relayed by Crypto Briefing and TokenPost, the project says one trader’s API keys were rebuilt from public signatures, because signing code outside its official SDKs reused nonces, and that its Security Council returned about $5 million in USDC to that trader. Lighter has confirmed no total for the loss, which outside counts put between $10.4 million and $15.5 million, and it has not named the trader.
Lighter, the blockchain, dove gli utenti scambiano token direttamente dal proprio wallet senza affidare la custodia dei fondi a una società.">swap perpetui) sono derivati che replicano pool di un market maker automatico divergono, rispetto a tenere semplicemente gli stessi token. Diventa definitiva al prelievo.">il prezzo di un'attività con leva ma senza scadenza. Un funding tra long e short, regolato ogni poche ore, tiene il contratto vicino al prezzo spot o all'indice.">perpetual futures exchange built as a zero-knowledge rollup on Ethereum, suspended all withdrawals and the creation of new pools on Monday 16 November 2026. In a post on X at 11:02 UTC, the project said it was investigating “a security incident that appears to involve a single compromised external party”. It gave no amount. TokenPost and Crypto Briefing report a suspected drain of about $15.48 million in USDC from two market-maker accounts, a tally Lighter has not confirmed.
Lighter withdrawals stayed frozen for most of Monday. At 11:50 UTC, 48 minutes after the statement, the project had posted nothing further on X: no loss figure, no named party, no reopening time, no word on repayment. Withdrawals reopened in the evening, after the explanation set out below. Trading did not stop. According to Crypto Briefing, ETH perpetuals kept trading and users could still open and close positions. They could not take money out.
Lighter’s post-mortem: reused nonces, rebuilt API keys and about $5 million returned
Lighter published a post-mortem later on 16 November. Crypto Briefing, which summarised it at 19:09 UTC, reports that the affected accounts signed their orders with code written outside Lighter’s official SDKs, and that this code used the same cryptographic nonce more than once. A nonce is a number meant to be used a single time in a signature. Use it twice, and someone holding both signatures can work back to the private key. That, according to the post-mortem, is how the attacker rebuilt the trader’s API keys: from signatures that were public.
An earlier update from Lighter, quoted by Altcoin Buzz, put it more briefly: “Our investigation indicates that today’s incident was caused by a leaked API key for a specific trader’s account.” CoinDesk reported at 16:41 UTC that Lighter had linked the affected accounts to market makers’ APIs. Neither the trader nor any firm behind the accounts is named in these reports.
With the keys in hand, the attacker created a public pool from the victim’s account, bought shares in it from a separate account, moved the victim’s funds into the pool and redeemed the shares, Crypto Briefing writes.
The pause came from Guardian, a smart-contract mechanism of Lighter that was triggered by the suspicious activity and stopped withdrawals, according to Crypto Briefing and Altcoin Buzz. Lighter’s Security Council then returned about $5 million in USDC to the affected trader, both outlets report. TokenPost words it another way: Lighter “has helped affected traders recover about 5 million USDC”. No report says how that money was recovered or where it came from. CoinDesk wrote at 16:41 UTC that the Council was preparing a contract upgrade.
When did the exchange reopen? At 16:41 UTC CoinDesk still described withdrawals as suspended and expected back by the end of Monday. At 18:31 UTC TokenPost reported Guardian mode closed, withdrawals restored and every pending request being processed. The reopening falls between those two times, some five and a half to seven and a half hours after the 11:02 UTC statement. No report gives the minute.
Two changes are already in place, per Crypto Briefing and TokenPost: a transfer into a public pool now needs a wallet signature, and API key signatures are no longer public. Lighter also plans IP allowlists, permissions that can be set key by key, limits on the markets a key may trade and monitoring for reused nonces. It is contacting the affected accounts and revoking the related keys. Traders who sign with custom or third-party software are told to rotate their keys and move to the official SDKs.
The amount is the gap that remains. Lighter has confirmed no total. Bitquery, an analytics firm cited by CoinDesk, traced $10.39 million in USDC leaving Lighter’s Ethereum contract; other researchers count up to $15.5 million across two market-maker accounts, and Lighter has not confirmed a second withdrawal. Taking away the roughly $5 million returned leaves about $5.4 million on the first count and about $10.5 million on the second. That is arithmetic on unconfirmed figures, not a number from Lighter.
What Lighter’s first statement said, and what it left out
That first statement is two sentences long. The first describes the incident and points outside the project, to one external party that was compromised. The second sets out the response: “As a precaution, we have temporarily suspended all withdrawals and pool creation while we investigate the circumstances and assess the full impact.”
Nothing in the post says the rollup, its contracts or its matching engine were breached, and nothing in it says they were not. Outlets go further than the post does. TokenPost reported at 11:21 UTC that the exchange said the incident “did not result from an inherent protocol vulnerability”, and Crypto Briefing wrote at 11:30 UTC that Lighter ties the problem to a single compromised external address, not to a flaw in its protocol. Neither outlet says where Lighter made those remarks, and they are not in the X post, the only statement on the project’s account at 11:50 UTC. Lighter has since said it in its own words, in the update quoted by Altcoin Buzz: “The Lighter protocol and smart contracts are unaffected.”
The freeze covers two things: withdrawals and the creation of new pools. Lighter’s status page, as it stood at 11:50 UTC on Monday, read “All services are online”, with the mainnet, the API, the front end and transaction sending all marked operational. It carried no entry for the freeze. Its latest entry, a network upgrade, was marked resolved the day before, on 15 November at 13:20 UTC. The page had not changed on 17 November at 05:45 UTC: all services online, and no entry for the freeze or for Guardian.

A $15.48 million tally across two market-maker accounts
The figure is not Lighter’s. It comes from on-chain analysis relayed by news outlets, and the first reports carried no address and no transaction hash. Lighter has still not confirmed it. TokenPost describes “a suspected $15.48 million drain from two market maker accounts”: account No. 714710 lost $10.39 million and account No. 714723 lost $5.09 million. ChainCatcher gives the same two accounts and amounts and rounds the total to about $15.5 million. Market makers are firms that quote buy and sell prices all day, and they keep large balances on the venues where they work.
Lighter has not named the owner of the two accounts. Its first statement did not say whether the “external party” was a market maker; by 16:41 UTC, CoinDesk reported, Lighter had linked the affected accounts to market makers’ APIs. Per TokenPost, the money that left was swapped into ether through CoW Protocol. Crypto Briefing adds that the South Korean exchanges Upbit and Bithumb halted LIT deposits and withdrawals as a precaution.
| Time (UTC, 16 November) | What happened | According to |
|---|---|---|
| About 10:15 | LIT starts falling from about $2.74 | Bybit spot, 15-minute candles |
| 10:30 to 10:45 | LIT touches $2.33, its low of the morning | Bybit spot |
| 11:02 | Lighter announces the freeze on withdrawals and pool creation | Lighter on X |
| 11:21 | A suspected $15.48 million drain from two accounts is reported | TokenPost |
| 11:30 | Trading said to continue; Upbit and Bithumb said to have halted LIT transfers | Crypto Briefing |
| 11:50 | Status page shows all services online; no follow-up on X | Lighter status page, Lighter on X |
| 16:41 | Withdrawals still suspended, expected back by the end of Monday; $10.39 million traced by Bitquery | CoinDesk |
| 18:31 | Guardian mode closed, withdrawals restored, pending requests being processed | TokenPost |
| 19:09 | Post-mortem summarised: reused nonces, about $5 million in USDC returned to the trader | Crypto Briefing |
Leaked API keys and a pool with no fee: what analysts reconstructed, and what Lighter confirmed
How does money leave an account whose trading keys are not supposed to be able to send funds to anyone else? The explanation that circulated on Monday morning was a reconstruction, not a finding. ChainCatcher traces it to the research of a South Korean trader it does not name, forwarded by the analyst posting as 0xTria, founder of Predicts.guru. Its conclusion: an API key leak at two large market-maker accounts, and no hack at the level of the protocol. Lighter had confirmed none of it in public at that point.
In that account, the attacker got hold of the API keys of the two accounts. An API key lets trading software place and cancel orders for an account without a person clicking. On Lighter, ChainCatcher writes, such a key cannot send funds to a third party. Transfers between accounts that sit under the same Ethereum address are another matter: they need no signature.
The rest follows from that gap, as the analysts tell it. The attacker closed the open positions of the two accounts, then created a public pool with a 0% fee from the victim’s account, so that the system treated the pool as the victim’s own. About $10,000 was enough to hold 99.99% of the pool’s shares. The victim’s USDC then went into the pool in batches of about $1 million and was redeemed. TokenPost describes the same path, from the closed positions to the 0% fee pool and the $1 million redemptions, and adds that Lighter “has not confirmed the exact cause”.
Lighter’s post-mortem, as Crypto Briefing relays it, confirms the outline: stolen keys, a public pool created from the victim’s account, shares bought from another account, the victim’s funds moved in and redeemed. No contract was broken; a feature was used with keys that were not the attacker’s. One point changes. The keys did not leak in the usual sense: they were rebuilt from public signatures. The 0% fee, the $10,000 stake and the $1 million batches come from the analysts alone.
LIT fell as low as $2.33 before the statement
The market moved before Lighter spoke. On Bybit’s spot market, LIT held near $2.74 until about 10:15 UTC, slid to $2.52 within fifteen minutes and hit a low of $2.33 in the 10:30 to 10:45 UTC candle, about 15% below where it started. It was back at $2.61 by 11:00 UTC, two minutes before the statement, and traded near $2.60 at 11:50 UTC. CoinDesk put it at $2.62 at 16:41 UTC, just under 9% lower over 24 hours.
Over 24 hours LIT was down 14.63% in the market snapshot of 11:44 UTC, the second-largest fall in that snapshot. The backdrop did not help: ETH traded near $1,806 in the same snapshot, and the Fear and Greed index stood at 10, deep in extreme fear.
DefiLlama counted about $743.4 million locked on Lighter at 10:35 UTC, against $759.1 million at midnight UTC and $777.3 million a day earlier. The Ethereum part stood at $534.1 million, down from $550.2 million at midnight, with $112.3 million on Robinhood Chain and $97.1 million on zkLighter. That reading was taken about 20 minutes after the token began to fall and may reflect the outflows only in part. With withdrawals shut at the time, the figure could not show how many users would have left if they could.

What a frozen exchange means for its users
Lighter is a venue for perpetual futures, contracts with no expiry that let traders bet on a price with leverage. Its X profile describes custom zero-knowledge circuits for “verifiable matching and liquidations” on an Ethereum layer 2. Proofs of that kind show that trades were executed by the rules. They say nothing about who holds the keys to an account.
For a trader with collateral on the exchange, Monday was simple and uncomfortable: positions could be managed, money could not be taken out, and for hours nobody said for how long. Lighter’s post-mortem speaks of one trader’s keys and reports no breach of its protocol or contracts. It does not say who bears the part of the loss that the roughly $5 million does not cover. A decentralised exchange carries no deposit guarantee and no compensation scheme, in the United States, the United Kingdom or the European Union, so any repayment would be a decision of the project or of the firms concerned.
A stolen key and an operator freeze are different risks from a contract bug, and our map of DeFi risks treats them apart. A user’s funds can be locked without any code failing.
The freeze landed in a rough few days for DeFi venues: Kava Lend lost about $3.8 million to an exploit on Sunday, and the ASTER token crashed on Aster’s own exchange a few hours before Lighter’s freeze.
Still unknown: the total loss, the trader’s name, who covers the rest
Five things were missing from Lighter’s account at 11:50 UTC on Monday: the amount lost, the identity of the compromised party, the attacker’s address, the time withdrawals would reopen, and whether anyone would be made whole. The reopening is settled, and so is the cause as Lighter tells it. The total is not: Lighter has confirmed no figure. The trader is unnamed. About $5 million went back to that trader, and nothing published says whether more will follow, or who would pay it. CoinDesk reports that Lighter identified a wallet it believes is the attacker’s; how the Security Council got the $5 million back is not explained.
What Lighter still has to deliver comes next: the IP allowlists, the per-key permissions and the nonce monitoring are announced, not live. For LIT holders one date was already on the calendar before any of this: the vesting of 500 million LIT for the team and investors, estimated to begin on 27 December 2026.
