EL7.AI
CryptoMedium•16 November 2026•
3 min read

Lighter Helps Traders Recover 5 Million USDC and Reopens Withdrawals

Key Facts

1Lighter helped affected traders recover about 5 million USDC.
2LIT was priced at 2.629 dollars on November 16, 2026, down 7.20% on the day.
3LIT touched a daily low of 2.344 dollars on November 16, 2026.
4Binance said it allocated more than 6.34 billion dollars to cover stolen assets in an October hack.

Lighter helped affected traders recover about 5 million USDC and reopened withdrawals after an API key leak, according to a TokenPost report published on November 16, 2026. The platform said it had shut down Guardian mode, resumed withdrawals and begun processing all pending requests. This eased restrictions traders faced while withdrawals were suspended, but does not mean all funds lost in the incident have been recovered. Lighter linked the leak to a flaw in unofficial signing code used by affected accounts. It said the protocol, smart contracts and infrastructure were not affected.

Lighter said the attackers exploited repeated nonce values in the signing code used by affected accounts. According to TokenPost's account of the platform's statement, the attackers used public signing data to reconstruct API keys. This mechanism differs from extracting private keys; the report describes API keys being reconstructed from available signing data. The platform said the issue was tied to unofficial signing code, while its official software development kit was unaffected. Its assurance also covered the protocol, smart contracts and infrastructure, which it said were not affected by the incident.

For fund handling, Lighter required wallet signatures for transfers to a public fund pool and made API key signatures private. These changes target two areas related to key permissions: requiring a wallet signature when carrying out transfers to the pool, and limiting access to API key signatures. They follow the incident that the platform linked to nonce reuse in unofficial signing code. It also said it had begun contacting affected accounts and revoking the keys associated with them as part of its efforts to address the leak's impact on users.

In trading, the LIT token was priced at 2.629 dollars on November 16, 2026, down 7.20% on the day, after touching 2.344 dollars. In the previous session, November 15, the token fell 1.53%, according to Investing.com data. The price move places the reopening of withdrawals and traders' recovery of about 5 million USDC in the context of a market in which the token's daily decline was larger on November 16 than the previous day. The report does not identify a causal link between the price decline and the incident, but records LIT's movement in the session when TokenPost covered the resumption of withdrawals and security measures.

The Lighter incident is among the cryptocurrency platform security risks covered in other reports during the same period. In a report published by the Associated Press on October 30, 2026, about a hack that occurred in October, Binance said it had allocated more than 6.34 billion dollars in company funds to cover stolen assets. The report added that Binance worked with blockchain partners to freeze about 3 billion dollars in affected assets. This provides context on the scale of financial and coordination measures that may accompany hacks, while Lighter's announced response focuses on the funds it helped traders recover and controls on API keys.

Lighter said it plans to add IP address allowlists, permission controls and restrictions specifying which markets an API key can trade in. Its plan also includes monitoring repeated nonce values, contacting affected accounts and revoking the associated keys. These measures are the next stage after Guardian mode was shut down, withdrawals resumed and pending requests began being processed, according to TokenPost. The report did not give a specific timeline for implementing the planned controls. The announced measures therefore remain plans in progress, while the report confirmed that withdrawals had resumed and pending requests were being processed.