BTCBTC$65,084+1.39%|
ETHETH$1,824.16+1.25%|
USDTUSDT$0.99924-0.00%|
BNBBNB$594.0500+1.11%|
USDCUSDC$0.99957-0.00%|
XRPXRP$0.97430+2.46%|
SOLSOL$73.9200+4.35%|
TRXTRX$0.30566+0.78%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$69.6900+6.47%|
ZECZEC$952.7500+10.31%|
XMRXMR$520.1000+3.72%|
DOGEDOGE$0.05957+1.91%|
LEOLEO$9.2800+0.88%|
USDSUSDS$0.99985-0.00%|
WBTWBT$62.8600+1.11%|
LINKLINK$9.3300+2.61%|
ADAADA$0.15530+2.72%|
XLMXLM$0.14092+2.82%|
USDEUSDE$0.99935+0.01%|
DAIDAI$1.0000-0.02%|
NEARNEAR$3.2700+4.22%|
BCHBCH$212.7900+4.07%|
RAINRAIN$0.00550444-10.86%|
LTCLTC$45.3300+2.41%|
CCCC$0.08312-0.70%|
UNIUNI$5.4400+7.02%|
AVAXAVAX$7.2600+2.56%|
XAUTXAUT$3,847.38-0.23%|
SUISUI$0.74041+3.72%|
BTCBTC$65,084+1.39%|
ETHETH$1,824.16+1.25%|
USDTUSDT$0.99924-0.00%|
BNBBNB$594.0500+1.11%|
USDCUSDC$0.99957-0.00%|
XRPXRP$0.97430+2.46%|
SOLSOL$73.9200+4.35%|
TRXTRX$0.30566+0.78%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$69.6900+6.47%|
ZECZEC$952.7500+10.31%|
XMRXMR$520.1000+3.72%|
DOGEDOGE$0.05957+1.91%|
LEOLEO$9.2800+0.88%|
USDSUSDS$0.99985-0.00%|
WBTWBT$62.8600+1.11%|
LINKLINK$9.3300+2.61%|
ADAADA$0.15530+2.72%|
XLMXLM$0.14092+2.82%|
USDEUSDE$0.99935+0.01%|
DAIDAI$1.0000-0.02%|
NEARNEAR$3.2700+4.22%|
BCHBCH$212.7900+4.07%|
RAINRAIN$0.00550444-10.86%|
LTCLTC$45.3300+2.41%|
CCCC$0.08312-0.70%|
UNIUNI$5.4400+7.02%|
AVAXAVAX$7.2600+2.56%|
XAUTXAUT$3,847.38-0.23%|
SUISUI$0.74041+3.72%|
News/Wallets & Security

Lighter Exploit Exposes API Keys as $10.39M USDC Is Withdrawn; Platform Restores Withdrawals

Decentralized derivatives exchange Lighter reopened withdrawals after a security incident involving compromised trader API keys. Unsafe third-party signing software reportedly reused cryptographic nonces, exposing private keys. Blockchain investigators traced 10.39 million USDC leaving the platform, while Lighter's Security Council recovered approximately $5 million for an affected trader.

Pankajj Purohit
By Pankajj Purohit
Lighter Exploit: $10.39M USDC Drained, Withdrawals Resume

Key Takeaways

  • $10.39 million confirmed on-chain: Bitquery identified a withdrawal of 10,393,057 USDC from Lighter's Ethereum settlement contract on November 16.
  • API key compromise: Lighter attributed the incident to unsafe third-party signing code that reused cryptographic nonces.
  • Core protocol unaffected: Lighter stated that its smart contracts, infrastructure, and official SDKs were not compromised.
  • Withdrawals restored: Deposits and withdrawals resumed after the Security Council deactivated Guardian Mode.
  • Approximately $5 million returned: Lighter reported returning funds to an affected trader during its emergency response.
  • Final losses uncertain: A separate estimate of $15.5 million remains unconfirmed, and the total unrecovered loss has not been publicly established.

Lighter Exploit: How Reused API Keys Led to a Multimillion-Dollar Security Incident

The Lighter exploit has raised fresh concerns about cryptocurrency trading security after an attacker gained access to a trader's API keys and moved more than $10 million in USDC from the decentralized derivatives platform.

The incident occurred on November 16, 2026, when suspicious activity involving accounts connected to Lighter triggered an emergency response.

Lighter, an Ethereum Layer 2-based perpetual futures trading platform, temporarily suspended withdrawals and new pool creation while investigating the incident.

The company later explained that the attack did not originate from a vulnerability in its core blockchain protocol.

Instead, the affected trader had been using custom or third-party software to generate cryptographic signatures for trading operations.

That software repeatedly used values that should have been unique for every signature.

The mistake exposed the private API keys associated with the trader's account, allowing an attacker to gain unauthorized control over certain account functions.

Blockchain intelligence company Bitquery subsequently traced a withdrawal of 10,393,057 USDC from Lighter's Ethereum settlement contract.

The incident highlights an increasingly important security challenge for decentralized finance: even when a protocol's smart contracts operate correctly, weaknesses in connected applications, signing software, and account permissions can expose users to significant financial losses.

What Happened During the Lighter Security Incident?

The incident unfolded over several hours on November 16.

Early reports suggested that large market-maker accounts had been compromised.

Lighter responded by activating its Guardian Mode security mechanism, which temporarily restricted withdrawals and new pool creation.

The platform initially attributed the incident to a compromised external party and said its protocol and smart contracts were unaffected.

Further investigation identified the underlying problem as unsafe cryptographic signing software.

According to Lighter's subsequent explanation, the affected accounts used signing code outside its official software development kits.

That external code reused cryptographic nonces, making it possible to recover private API keys from publicly observable signatures.

The attacker then used the compromised account permissions to move funds through Lighter's pool functionality.

By the time the platform suspended withdrawals, blockchain investigators had already identified a substantial transfer leaving its Ethereum settlement contract.

Later that day, Lighter announced that deposits and withdrawals had returned to normal following the deactivation of Guardian Mode.

The company also reported that approximately $5 million had been returned to an affected trader.

However, the full financial impact remains uncertain because not every reported loss has been independently confirmed.

How Did Nonce Reuse Expose Lighter's API Keys?

The technical cause of the incident involves a cryptographic concept known as a nonce.

A nonce is a value intended to be used only once in a particular cryptographic operation.

Digital signature systems rely on carefully generated values to ensure that private keys cannot be reconstructed from public signatures.

In certain signature schemes, reusing the same secret nonce across different messages can expose enough mathematical information for an observer to recover the signing key.

That is what Lighter says happened in this incident.

The affected trader's external signing software generated signatures using repeated nonce values.

Because the relevant signatures were publicly observable, the attacker could analyze them and recover the associated private API keys.

This did not require the attacker to break Ethereum's cryptography or compromise Lighter's underlying smart contracts.

Instead, the vulnerability arose from incorrect use of an otherwise secure cryptographic mechanism.

Why API key security matters in DeFi

API keys allow trading software to interact with an exchange without requiring users to manually authorize every action.

Professional traders and market makers commonly use them for automated strategies, order management, and position monitoring.

These systems can execute large numbers of transactions with minimal human intervention.

However, an API key with broad permissions can become dangerous if compromised.

An attacker may be able to place unauthorized trades, change positions, or access account functions permitted by the key.

The Lighter incident demonstrates that API keys should be treated as sensitive financial credentials, even when they do not directly authorize external withdrawals.

How Did the Attacker Withdraw Funds Without a Wallet Signature?

One of the most significant aspects of the incident was the way the attacker allegedly converted limited trading permissions into an opportunity to withdraw funds.

Under Lighter's normal permission structure, API keys can perform trading operations and transfer funds between certain accounts associated with the same wallet.

However, transferring assets directly to another wallet owner requires a wallet-level signature.

That restriction is intended to prevent a compromised trading API key from being used for unrestricted withdrawals.

The attacker reportedly found a way around this separation through Lighter's public pool system.

A public pool created by an account was treated as a sub-account belonging to that account.

This allowed certain transfers into the pool to be authorized using API-level permissions.

According to Lighter's reconstruction, the attacker used the compromised API keys to transfer funds into a public pool after acquiring pool shares through another account.

The attacker then redeemed those shares to extract the funds.

The process exposed an important weakness in the interaction between account permissions and pool ownership.

Although the API key could not directly authorize an ordinary external withdrawal, it could reportedly perform operations that ultimately transferred economic control of the assets.

Lighter subsequently introduced additional restrictions.

Transfers to public pools now require wallet-level signatures, and API signatures are no longer publicly exposed in the same way.

These changes are intended to reduce the risk of similar attacks.

Bitquery Traces 10.39 Million USDC Leaving Lighter

Blockchain intelligence company Bitquery independently examined the movement of funds associated with the incident.

Its investigation identified a withdrawal of 10,393,057 USDC from Lighter's Ethereum contract at approximately 10:11 UTC on November 16.

The funds were transferred to an Ethereum wallet associated with the suspicious activity.

Within minutes, the wallet converted most of the USDC into Ether through CoW Swap.

Bitquery reported that approximately 10.36 million USDC was exchanged for roughly 5,752 ETH in a series of transactions.

The rapid conversion is notable because USDC is a centrally issued stablecoin whose issuer, Circle, has the technical ability to freeze certain token balances.

ETH does not have an equivalent issuer-controlled freezing mechanism.

Moving funds from USDC into ETH can therefore make recovery more difficult through issuer intervention alone.

However, the transaction sequence does not establish the attacker's identity or ultimate intentions.

The funds were subsequently divided across additional wallets, with some transferred toward Hyperliquid.

Why Did Funds Move to Hyperliquid and XMR1?

Bitquery identified further transfers involving Ethereum wallets and the Hyperliquid trading ecosystem.

In one documented sequence, 1,920 ETH moved through twelve wallets associated with transactions leading to Hyperliquid.

The accounts then purchased XMR1, a token referencing Monero.

Monero is a cryptocurrency known for privacy-focused transaction features, but XMR1 on Hyperliquid should not automatically be treated as native Monero.

The distinction matters because different tokens can have different custody arrangements, redemption mechanisms, and technical characteristics.

The movement through multiple wallets and trading venues complicated the transaction trail.

However, blockchain investigators were still able to follow significant portions of the activity using publicly available transaction data.

Bitquery also cautioned that some relationships between wallets were inferred from transaction patterns rather than conclusively established ownership information.

The investigation therefore supports the identification of suspicious fund movements but does not prove who controlled every associated address.

Was $15.5 Million Stolen From Lighter?

Several early reports suggested that approximately $15.5 million had been affected across two large trading accounts.

That estimate combined the confirmed 10.39 million USDC withdrawal with another reported amount of approximately $5.09 million.

However, the second amount was not independently confirmed as having left Lighter's Ethereum settlement contract during Bitquery's initial investigation.

This creates an important distinction between three figures:

10.39 million USDC: The withdrawal independently identified through Ethereum transaction analysis.

Approximately $15.5 million: A broader estimate circulated by researchers and market participants, which Lighter had not confirmed as its final loss.

Approximately $5 million: Funds Lighter's Security Council reportedly returned to an affected trader.

These figures should not be added together or subtracted mechanically.

The relationship between the returned funds and the reported affected balances has not been fully explained.

As a result, the total unrecovered loss cannot be established from the available information.

For accurate reporting, the 10.39 million USDC figure is best described as a verified on-chain withdrawal rather than a confirmed final loss.

Lighter Reopens Withdrawals After Activating Guardian Mode

Lighter activated Guardian Mode as part of its emergency response.

The mechanism allowed the platform's Security Council to temporarily restrict withdrawals and new pool creation while investigating the compromised accounts.

The intervention was intended to prevent additional suspicious withdrawals and protect remaining assets.

According to the incident timeline, the initial 10.39 million USDC withdrawal occurred before the emergency restrictions were activated.

This means Guardian Mode did not prevent the first major transfer.

However, the mechanism may have helped limit further movement of funds.

Later on November 16, Lighter confirmed that deposits and withdrawals had returned to normal.

The platform also reported that approximately $5 million had been returned to an affected trader during the response.

The incident illustrates both the benefits and trade-offs of emergency controls in decentralized finance.

Such mechanisms can help protect users during an active security incident.

At the same time, they introduce governance questions about who has authority to suspend platform operations and under what circumstances those powers can be exercised.

For traders, understanding these arrangements is an important part of evaluating the risks associated with a decentralized exchange.

How Did the Lighter Incident Affect the LIT Token?

The security incident also affected market sentiment surrounding Lighter's native token, LIT.

According to CoinDesk's November 16 reporting, LIT fell more than 10% during the initial market reaction, briefly dropping below $2.48 before recovering to approximately $2.62.

These figures represent prices observed during the incident, not current market quotations.

The decline illustrates how security concerns can influence investor confidence even when a platform says its underlying smart contracts remain secure.

For token holders, the immediate concern was uncertainty about the scale of the incident, the possibility of further losses, and how quickly normal operations could resume.

The temporary withdrawal suspension also introduced concerns about access to funds.

However, a short-term token price decline does not establish that the platform has suffered permanent operational damage.

Longer-term confidence will depend on the effectiveness of Lighter's security changes, transparency about the incident, and its ability to prevent similar failures.

What Security Changes Is Lighter Introducing?

Following the incident, Lighter outlined several measures intended to strengthen API security.

The first involves restricting access to API signatures so that sensitive signing information is no longer publicly exposed in the same manner.

The second requires wallet-level authorization for transfers into public pools, addressing the permission gap reportedly used during the attack.

Lighter has also outlined plans to introduce additional protections, including IP allowlists, configurable permissions for individual API keys, rate limits, and improved monitoring.

These measures address different parts of the security problem.

IP allowlists can restrict where authorized API requests originate.

Per-key permissions can reduce the actions available to a compromised credential.

Rate limits can make certain forms of automated abuse more difficult.

Monitoring can help identify suspicious activity and potentially revoke exposed credentials before further damage occurs.

However, no single protection guarantees complete security.

For example, IP allowlists may provide limited protection if an attacker compromises infrastructure operating from an approved address.

Similarly, permission limits must be carefully designed to prevent attackers from combining individually permitted operations into an unintended withdrawal path.

The Lighter incident demonstrates why security controls should be evaluated not only individually but also in combination.

What Should Lighter Traders and API Users Do Now?

The most immediate recommendation from Lighter is for users of custom or third-party signing software to rotate their API keys.

Users who cannot verify that their signing implementation generates cryptographically secure, unique nonces should consider switching to Lighter's official SDKs.

This is particularly important for automated trading systems and market-making operations.

Developers should also review the permissions granted to API keys and avoid providing broader access than their applications require.

Where supported, separate keys should be used for different functions.

Traders should review recent account activity for unexpected transfers, pool operations, and position changes.

For larger trading operations, monitoring unusual transactions can provide an additional layer of protection.

More generally, the incident reinforces the importance of reviewing third-party tools before connecting them to financial accounts.

A decentralized exchange can have audited smart contracts while still exposing users to risks through external trading software.

Bitnxt readers can explore related topics through its cryptocurrency security news, crypto wallet resources, and cryptocurrency exchange coverage.

Why the Lighter Exploit Matters for the Wider DeFi Industry

The Lighter incident highlights a security challenge that extends beyond any individual trading platform.

Decentralized finance applications increasingly depend on complex combinations of smart contracts, automated trading systems, external APIs, wallets, and third-party software.

Each component introduces its own security assumptions.

A protocol may correctly enforce its documented rules while an attacker exploits unexpected interactions between those rules.

In this case, the reported problem involved both insecure external signing software and an account-permission structure that allowed a compromised API key to interact with public pools.

That combination is especially important.

The initial cryptographic failure exposed the credentials, but the available permissions determined how much damage those credentials could cause.

This suggests that protecting private keys is only one part of the solution.

DeFi platforms must also design authorization systems that limit the financial consequences of credential compromise.

For professional traders, this becomes increasingly important as automated strategies manage larger balances and interact with multiple protocols.

The incident also demonstrates the value of blockchain transparency.

Although investigators could not establish every detail of the attack, public Ethereum transactions allowed them to identify a major withdrawal and follow substantial portions of the subsequent fund movements.

That visibility helped distinguish verified transfers from broader estimates circulating online.

Bitnxt Take: The Next DeFi Security Challenge Is Outside Smart Contracts

At Bitnxt, we believe the Lighter exploit illustrates a weakness that the cryptocurrency industry cannot afford to overlook.

For years, much of the discussion around decentralized finance security has focused on smart contract vulnerabilities.

Developers invest significant resources in contract audits, formal verification, and blockchain security testing.

Those measures remain essential.

However, the Lighter incident shows that secure smart contracts do not automatically guarantee secure user accounts.

The reported attack began with signing software that reused cryptographic nonces.

That failure occurred outside Lighter's core protocol.

But the consequences became much more serious because the compromised API keys could interact with account and pool functionality in ways that enabled funds to be extracted.

We believe this combination deserves more attention than the headline loss figure alone.

A professional trader may use several third-party applications to execute strategies, manage liquidity, and monitor positions.

Every additional integration can introduce security risks.

From our perspective, decentralized trading platforms should treat compromised API credentials as an expected threat rather than an exceptional event.

That means designing systems so that a leaked trading key cannot easily become a mechanism for transferring ownership of substantial funds.

We also think Lighter's emergency response raises an important governance question.

Guardian Mode allowed the Security Council to restrict withdrawals and help protect remaining assets.

That capability can be valuable during an active incident.

However, users should understand who controls such mechanisms and how their use is governed.

There is an unavoidable trade-off between unrestricted protocol operation and emergency intervention.

The industry needs greater transparency about those trade-offs.

Finally, we believe the difference between the verified 10.39 million USDC withdrawal and the unconfirmed $15.5 million estimate matters.

Security reporting should distinguish between observed blockchain activity, reported account exposure, recovered assets, and final financial losses.

Combining those figures without explanation can mislead readers.

Bitnxt's view is that the most important lesson from Lighter is not simply that an API key was compromised. It is that decentralized platforms must limit what attackers can accomplish after credentials are exposed.

That principle should influence how future DeFi trading systems are designed.

What Happens Next for Lighter?

Following the reopening of withdrawals, several questions remain unresolved.

The first concerns the final financial impact.

Lighter has not publicly established the total unrecovered loss or fully explained the relationship between the verified withdrawal and the funds returned to the affected trader.

The second concerns additional security improvements.

The company has announced changes to API signature visibility and pool-transfer authorization, alongside plans for more granular API controls.

Users will need further updates to determine when all proposed safeguards are implemented.

The third issue is whether other accounts using unsafe third-party signing software may be vulnerable.

Lighter has urged users to review their integrations and rotate credentials where necessary.

Finally, the movement of funds across Ethereum and other trading platforms may remain relevant to ongoing blockchain investigations.

For now, Lighter has restored normal deposit and withdrawal operations, but the complete financial and security consequences of the incident are still being assessed.

Conclusion

The November 16 Lighter exploit demonstrates how a failure in third-party cryptographic signing software can lead to substantial losses even when a decentralized exchange's core smart contracts remain unaffected.

Investigators identified a 10.39 million USDC withdrawal, while Lighter attributed the incident to reused signing nonces that exposed a trader's private API keys.

The platform temporarily suspended withdrawals, introduced additional security restrictions, and later restored operations.

Approximately $5 million was returned to an affected trader, although the total unrecovered loss remains uncertain.

For Bitnxt, the incident reinforces a broader lesson: decentralized finance security must extend beyond smart contract audits to include API permissions, external software, cryptographic signing practices, and emergency response systems.

As automated trading becomes more widespread, protecting these interconnected systems will be essential to maintaining trust in decentralized financial markets.

Suggest a correction or update

Spotted something missing, outdated or incorrect on this page? Tell us what needs updating and share an official source or supporting link so our team can verify it.

More Wallets & Security News

Share:

Bitnxt uses cookies to run the site, understand how it is used, and measure ads. You can accept or decline below, and change your choice any time in our Privacy Policy.