Lighter restored deposits and withdrawals after an attacker obtained trader API keys and used the exchange’s public-pool system to move account funds. The November 16 incident exposed a security boundary between Lighter’s protocol and the external software used to authorize activity on it: the company says its smart contracts, infrastructure and official software-development kits were not compromised.

Attributable Ethereum analysis by Bitquery identified one transaction carrying 10,393,057 USDC from Lighter’s settlement contract to a wallet the exchange associated with the attacker at 10:11 UTC on November 16. That is a verified on-chain withdrawal, not a final loss calculation. Lighter has not published a complete reconciliation of the affected accounts or all recovered funds.

Reused nonces exposed signing keys

Lighter’s postmortem attributes the key exposure to custom or third-party signing code used by the affected accounts. That code reused cryptographic nonces—the one-time values incorporated into signatures—making private API keys recoverable from publicly visible signatures.

The exchange said its official Python, Go, TypeScript and Agent Kit software generated nonces securely and was not affected. This remains a company finding rather than an independently reproduced examination of the affected signing code, which Lighter did not publish.

After recovering the keys, the attacker created a public pool from an affected account and acquired shares in that pool through another account under the attacker’s control. Funds were then transferred into the pool without corresponding shares being minted, increasing the value attributable to the attacker-held shares. The attacker redeemed those shares and withdrew the proceeds, according to Lighter.

That route matters because an API key could not send money directly to an unrelated wallet. It could, however, transfer funds among an account’s subaccounts, including a public pool created by that account. The incident therefore involved compromised credentials and the scope of actions those credentials could authorize, rather than a reported failure of the rollup’s core settlement logic.

Guardian intervention recovered a separate amount

Lighter said an anomalous transaction triggered its Guardian mechanism, temporarily pausing withdrawals. Its Security Council then returned approximately 5 million USDC to an affected trader before Guardian mode was disabled and pending withdrawals resumed processing.

The approximately $5 million figure should not be subtracted mechanically from the 10,393,057 USDC withdrawal. Independent reporting says it concerned an additional attempted withdrawal that did not complete on Ethereum, while Bitquery found only the 10.39 million-USDC transaction linked to the event during its observation window. Lighter has not stated a final net loss or explained whether more than one trader account was affected.

Bitquery read Ethereum activity through approximately 12:13 UTC on November 16. Its analysis found the receiving wallet swapped about 10.38 million USDC for approximately 5,764 ETH, but subsequent movements do not prove who controlled each destination. Its dataset also could not inspect the internal public-pool activity on Lighter’s rollup, leaving that portion dependent on the exchange’s account.

Controls changed after withdrawals reopened

Lighter now requires a wallet signature before funds can be transferred into a public pool, preventing an API key alone from using the route described in the postmortem. It also made API-key signatures non-public.

The exchange says it plans IP allowlists, configurable permissions and limits for individual keys, monitoring for nonce reuse and proactive revocation of affected credentials. It did not give implementation dates for those planned controls.

The verified event occurred November 16; Coinburn’s publication date is November 17 in America/New_York. The remaining questions are the final financial loss, the number of affected accounts, the Security Council’s exact recovery actions and whether Lighter will publish code or transaction records supporting its internal reconstruction.

Primary sourceLighter — Signing Safely on Lighter: Lessons from November 16 ↗

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.