Lighter Crypto Exchange Traders Hacked: Keys Computed From Public Signatures, $5M Returned

November 17, 2026:

Lighter Crypto Exchange Traders Hacked: Keys Computed From Public Signatures, $5M Returned

Lighter, the Ethereum-based perpetual futures exchange backed by Founders Fund and Ribbit Capital, froze all withdrawals at 6:02 a.m. ET on Monday, November 16, after researchers estimated about $15.5 million in USDC left two market-maker accounts. Lighter’s postmortem later traced the “leaked” API key to something subtler: attackers computed the private keys from public signatures, because custom signing software outside Lighter’s official SDKs reused cryptographic nonces.

Anyone who runs trading bots with homemade or third-party signing code should treat that as a warning: a reused nonce exposes the key to any observer who sees the signatures, from the moment a second such signature is published, not from the moment of theft. Lighter has told users of custom or third-party signing tools to rotate their API keys and switch to the official SDKs.

Withdrawals Reopened Monday After Security Council Returned About $5 Million

Lighter’s first public statement said it was investigating an incident that “appears to involve a single compromised external party,” and it named neither the party nor an amount. The dollar figures came from on-chain researchers. The analyst 0xTria, relaying work by Korean blockchain observers, put the losses at about $10.39 million from account #714710 and about $5.09 million from account #714723. Lighter’s own updates refer to one affected trader and have not confirmed the combined estimate.

The withdrawal came about an hour before Lighter’s first statement, and the attacker’s wallet reportedly received about $10,000 through a relay roughly 30 minutes before the main withdrawal. Withdrawals reopened later Monday after Lighter’s Security Council returned about $5 million in USDC to one affected trader, Guardian mode was switched off, and pending withdrawal requests began processing. Public reporting does not say which of the two accounts received the money, and the amount is about a third of the researchers’ estimate.

Most of the rest remains unrecovered. Trackers saw the attacker swap about $10.39 million of USDC for ETH through CoW Swap and split it into batches of about 160 ETH; crypto.news put the swap at about 5,400 ETH and bithub.pl at about 5,760 ETH. A stablecoin issuer can freeze its token at an address, but ETH has no issuer to do that, so conversion into ETH removes the main freeze lever. Bithub.pl, citing on-chain sleuths and not Lighter, also reported that part of the money went to Hyperliquid to buy Monero, a privacy coin that is harder to trace. Lighter has not published a confirmed total loss or said whether it will cover the shortfall.

Reused Nonces Let Attackers Compute Private Keys From Public Signatures

A digital signature is built from a private key plus a secret one-time number, the nonce, that must be fresh every time. If the same nonce signs two different messages, observers can recover the private key from the two signatures. Third-party NautilusTrader documentation for its Lighter integration describes Schnorr signatures over the ECgFp5 elliptic curve with Poseidon2 hashing, and an open-source library for that curve lets the caller supply the nonce. Reports on Lighter’s postmortem do not name the signature scheme or say exactly how the unofficial code repeated its nonces.

The algebra is short. In the older ECDSA scheme, two signatures with the same nonce share a value, and subtracting one signature from the other cancels the private key out of the equation, leaving the nonce, from which the private key follows. The failure is old and well documented. Researchers recovered Sony’s PlayStation 3 signing key in December 2010 because Sony’s per-signature value was static, and a flaw in Java’s random number generator let attackers recover keys from Android Bitcoin wallets in August 2013. A 2026 peer-reviewed paper by Vincent Jacquot and Benoit Donnet, presented at Financial Cryptography and Data Security, reports the first confirmation that attackers actively exploit nonce reuse on both Ethereum and Bitcoin. The standard defense, RFC 6979, derives each nonce deterministically from the private key and the message, so a faulty random number generator cannot repeat one.

The word nonce can mean two different things on an exchange like this: a sequential counter that orders transactions and is not secret, and the secret per-signature number. The postmortem concerns the second kind. The attack also needed a second ingredient: the signatures had to be visible. Lighter’s fixes include making API-key signatures private, which is consistent with its statement that attackers derived keys from signatures visible on the blockchain.

That points to a larger problem than one leaked key. Nonce reuse hands the key to any observer from the moment the second signature appears, so the exposure began before the theft. Lighter has not said how long the keys were derivable, how many accounts ran the same signing code, or who wrote it. OnchainLens claimed the exposed key belonged to Abraxas Capital, a London fund; that claim is unconfirmed, and Lighter has not named any victim.

How Did Attackers Move USDC Out Through Zero-Fee Public Pools?

Lighter’s postmortem and the on-chain reconstruction agree on the broad sequence. Using the derived keys, the attacker controlled a victim account and created a public liquidity pool with zero fees. A separate account bought nearly all of the pool’s shares, which researchers priced at about $10,000 for roughly 99.99% ownership. The hijacked account then moved USDC into the pool, reportedly in tranches of about $1 million, and the attacker redeemed the shares and left with the cash. OnchainLens also reported that the attacker first closed the victim’s open positions.

Here the accounts diverge. Lighter says its protocol, smart contracts, infrastructure and official SDKs were unaffected and puts the blame on externally written signing code. Researchers cited by crypto.news say the weak point also lay in a protocol rule: transfers between accounts tied to the same Layer 1 address needed no extra signature, and a pool created by a compromised account counted as that account’s own property. Lighter has since changed that rule: transfers into public pools now require a wallet signature. A similar share-capture pattern appeared in this month’s ACryptoS exploit, where the project says a missing input check let tiny deposits mint most vault shares.

Security Council Return of Funds Shows Who Can Change Lighter’s Contracts

According to Lighter, suspicious activity triggered its Guardian mechanism, a contract feature that paused withdrawals, and its Security Council later returned the $5 million. Lighter had said recovery would require a contract update by the Security Council, and it hoped to reopen withdrawals the same day. Reports do not say where the returned $5 million came from or how the update worked.

That power is the center of an old argument in decentralized finance. Charlie Lee has argued that an exchange cannot be called decentralized if it can freeze customer funds. Research from ETHBEAT, formerly L2BEAT, dated May 22, 2026, gives Lighter’s side of the trade-off: collateral sits in Ethereum contracts, and if the operator fails to process a forced transaction within 14 days, anyone can trigger an escape mode and withdraw by zero-knowledge proof. The same research rates Lighter as Stage 0, meaning the team controls the contract upgrade path, and notes the operator holds API keys and the matching engine offchain.

LIT Token Price Fell Up to 17% Intraday; Korean Exchanges Reportedly Paused Transfers

Reports of the peak decline in Lighter’s LIT token vary with the outlet and the hour. Crypto Economy reported a drop of more than 7%, bithub.pl reported a drop of up to 13%, and crypto.news reported more than 17% at one point before a partial recovery to between $2.50 and $2.66. Cryptopolitan put LIT at $2.53, down from $2.75.

South Korean exchanges Upbit and Bithumb reportedly suspended LIT deposits and withdrawals; the suspensions rest on media reports, and no exchange notice has been cited. Upbit listed LIT in its won market and Bithumb also listed LIT against won earlier this year.

Lighter Announced Plan to File for CFTC Derivatives License Weeks Before Exploit

Lighter said on October 21 that it planned to file for a U.S. Commodity Futures Trading Commission derivatives license in November, with the stated goal of becoming the first on-chain perpetuals exchange with CFTC approval. The LIT token jumped on the announcement. Whether Lighter has filed is not reported in coverage of the exploit. Founder and CEO Vladimir Novakovski, a Harvard graduate and former Citadel engineer, leads a company that raised $68 million last year at a $1.5 billion valuation in a round led by Founders Fund and Ribbit Capital, with Robinhood participating. Lighter also has a partnership with Robinhood Wallet that gives eligible users access to perpetual futures, and launched an EVM development network in October. No lawsuit or regulatory action over the incident has been reported.

Market Makers Running Custom Signers Should Rotate Keys and Move to Official SDKs

Lighter’s own advice is the most direct action available: users of custom or third-party signing tools should rotate their API keys and move to the official SDKs. Lighter publishes Go signing code in a public lighter-go repository. Planned protections include IP allowlists, configurable API-key permissions and automated monitoring for reused nonces. Published audits by zkSecurity examined Lighter’s zero-knowledge circuits and exit mechanism, which are separate from signing code that traders write themselves.

Custom signers sit outside the official SDKs, so their safety depends on each firm’s own code. Four questions decide the risk. Does the signer reuse or predict any nonce, or does it derive nonces deterministically in the RFC 6979 style? Are signatures public? Have the keys been rotated since the incident? And does the exchange monitor for repeats? Lighter’s new safeguards now depend partly on firms moving to the official SDKs, because its own fix list tells custom-tool users to switch.


Frequently Asked Questions

Is it safe to withdraw from Lighter now that withdrawals have reopened?

Withdrawals reopened Monday, Guardian mode is off, and pending requests are processing. Lighter says its protocol, smart contracts, infrastructure and official SDKs were unaffected. Lighter has not published a confirmed total loss, and ETHBEAT research says users can exit by zero-knowledge proof if the operator fails to process a forced transaction within 14 days.

How did attackers get Lighter users’ API keys?

According to Lighter, the keys were not taken from a database. The affected accounts used custom signing software that reused nonces, and an attacker derived the API private keys from signatures visible on the blockchain.

Could other Lighter accounts still be exposed?

Possibly. Any account that signed with the same flawed code and has not rotated its keys remains derivable by anyone holding the signatures, which is why Lighter told custom-tool users to rotate keys. Lighter has not said how many accounts used such code.

Will Lighter cover the unrecovered losses?

Lighter has not said. It returned about $5 million in USDC to one affected trader, and the researchers’ $15.5 million estimate has not been confirmed by the exchange.

Source link