- LIT has recovered most of its post-exploit losses but stalls below its moving averages.
- Lighter traced the breach to a trader’s custom signing software, and its smart contracts were not touched.
- The Security Council froze withdrawals and recovered part of the funds before reopening the exchange.
- The rebound now depends on whether buyers can clear a narrow resistance band just above the current price.
The LIT price climbed back to around $3.00 on Tuesday, up almost 14% in 24 hours, after Lighter, the decentralized perpetual futures exchange behind the token, reopened deposits and withdrawals and published a postmortem explaining the November 16 exploit, which drained roughly $10.4 million in USDC from a single trader’s account. The bounce has wiped out most of the sell-off that dragged LIT to $2.33 on OKX during the incident. Even so, the token is still about 6% lower than a week ago, with a market value of around $752 million, and it is now pressing against a resistance band that has held prices down since the middle of last week.
Deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council.
More details on what happened: https://t.co/HLIw6E7UdO https://t.co/rYf8oXx7Du
— Lighter (@Lighter_xyz) November 16, 2026
Sellers defend the $3.05 line
On the four-hour chart, LIT climbed back above $2.80 and $2.95 in a single push on Monday evening, then stalled at $3.04, just under the 50-period exponential moving average (EMA) at $3.05. On this timeframe that average reflects roughly the last eight days of trading, so a price below it means LIT is still trading weaker than its recent norm. The 200-period EMA, which covers about a month, sits higher at $3.25 and is still pointing down.
The Fibonacci levels on the chart measure the drop from the November 7 high near $3.57 to Monday’s low. At $2.99, the LIT price has won back a little more than half of that decline. The 0.618 level at $3.09 marks the point where it would have recovered almost two-thirds, and together with the 50-period EMA it creates a tight ceiling between $3.05 and $3.09.
Momentum improved quickly but has started to cool. During the sell-off the Relative Strength Index (RSI) fell below 30, a zone that usually means selling has run ahead of itself. It has since rebounded to about 52, roughly neutral, and has flattened over the last few candles. The candle that carried the crash also printed the heaviest four-hour volume of the month, bigger than any of the rebound candles, which means the buying so far has not matched the force of Monday’s panic.
A four-hour close above $3.09 would bring the 200-period EMA at $3.25 into reach, with the 0.786 level at $3.30 just behind it. If $2.95 fails, the next support sits at $2.80, and below that $2.62, where buyers first stepped in on Monday.
How a reused nonce opened the door
Lighter’s postmortem, titled Signing Safely on Lighter: Lessons from November 16, found that the affected accounts signed their orders with custom software instead of Lighter’s official software development kits (SDKs). Every digital signature relies on a nonce, a one-time random number that must never repeat. The custom software reused it, and anyone who collects two signatures made with the same nonce can work out the private key behind them using public data alone.
With the keys in hand, the attacker closed the victim’s open positions, created a public liquidity pool from the compromised account and bought nearly all of the pool’s shares through a second account. It then moved the victim’s balance into the pool and redeemed the shares, turning an API trading key into a withdrawal. Each step went through as a properly signed action. That is why Lighter says its smart contracts and core protocol were unaffected, and why its official SDKs, which generate nonces safely, were not exposed.
$10.4 million out, $5 million recovered
Blockchain analytics firm Bitquery traced 10,393,057 USDC leaving Lighter’s Ethereum settlement contract at 10:11 UTC on November 16. A second account holding about $5.09 million was also exposed, and early reports added the two together to reach $15.5 million, a total Lighter has never confirmed. The exchange switched on Guardian Mode, an emergency mechanism that freezes withdrawals, and its Security Council used the pause to recover roughly $5 million tied to the attacker’s second withdrawal attempt and return it to the affected trader. That recovery does not reverse the first $10.39 million, which had already left the platform.
Within minutes, the stolen USDC had been swapped into about 5,750 ETH. Bitquery then tracked 1,920 ETH split across twelve wallets of 160 ETH each, routed through the LI.FI bridge aggregator to Hyperliquid and spent on roughly $3.46 million of XMR1 tokens. Another 3,845 ETH remained in the wallet Lighter flagged as the attacker’s, 0xb3ff…e387, at the time of Bitquery’s 11:55 UTC snapshot. Upbit and Bithumb, two of South Korea’s largest exchanges, suspended LIT deposits and withdrawals as a precaution on November 16.
What Lighter changes for API traders
Two fixes are already live. Transfers into public pools now require a wallet signature, which an API key alone cannot provide, and API key signatures are no longer public, removing the raw material the attacker used to rebuild the keys. Lighter also plans IP allowlists for API keys, configurable key permissions and limits, and automated monitoring for nonce reuse. It has told developers running custom signers to rotate their keys and switch to the official SDKs.
Market makers and trading bots are likely to feel these changes most, since they are the accounts most inclined to write their own signing code for speed. Permission and limit controls would cap how much a single stolen key can move, which tackles the size of Monday’s loss more directly than either of the patches already shipped. For LIT holders, the practical question is whether those automated clients stay through the transition, since much of a perpetual exchange’s volume comes from them.
Bitquery also flagged a separate theft of about $6.45 million from a Safe wallet on the same day, plus a Kava-related exploit two days earlier. In both cases funds were routed through LI.FI into XMR1 on Hyperliquid. The firm cautioned that similar transaction patterns do not prove a single actor was behind all three incidents, and no link to the Lighter attacker has been established.


