Loading post from X…
View post on X
What Was Returned
The roughly 5 million $USDC figure comes from Lighter, which said its Guardian safeguard paused withdrawals and allowed the Security Council to return those funds. Earlier, the platform had described the recovery target as funds involved in an additional withdrawal attempt. This was a council-led recovery during the pause, not an announced voluntary repayment by the attacker.
Separately, Ethereum transaction records show that about 10.39 million $USDC had already left Lighter’s contract at 5:11 a.m. ET. It went to the wallet that Lighter subsequently identified as believed to be associated with the attacker. The platform’s latest account does not announce recovery of that earlier withdrawal.
How the Keys Leaked
Lighter attributed the incident to unsafe signing code used by the affected accounts rather than its official software development kits. It said its protocol, smart contracts and infrastructure were unaffected.
According to Lighter, the accounts’ code reused a signing nonce—a secret, one-time value used to generate a digital signature. Reusing that value let the attacker calculate the private API keys from publicly visible signatures. Lighter said its official signing tools generated those values safely and were not affected.
The stolen keys could not directly withdraw funds to somebody else’s wallet. But, Lighter said, a public pool created by an account counted as that account’s own sub-account, allowing an API key to transfer funds into it. The attacker bought pool shares through a separate account, moved the trader’s funds into the pool without creating additional shares, then redeemed the shares and withdrew the proceeds.
Lighter said it had changed that permission: transfers into a public pool now require a wallet signature, so an API key alone is insufficient. It also said it had made API-key signatures non-public.
For traders using custom or third-party signing software, Lighter advised rotating all API keys and switching to an official signing toolkit if they were unsure whether their code had reused a signing nonce. It said further protections, including restrictions on which servers may use a key and configurable permissions and limits for each key, were being added.
Updated Nov. 16 to reflect Lighter’s announcement that deposits and withdrawals had returned to normal, its reported fund recovery and its explanation of the compromised keys.