mt logoMyToken
ETH Gas
Tiếng việt

Lighter Reopens Withdrawals After Nonce-Reuse Error Exposes Trader API Keys

sưu tầmcollect
đăng lạishare

TL;DR

  • Lighter says deposits and withdrawals have resumed after its November 16 incident.
  • Bitquery observed a roughly $10.4 million USDC withdrawal; the venue reports about $5 million returned to traders.
  • The reported root cause involved nonce reuse in unofficial signing code, not a confirmed smart-contract exploit.

Decentralized derivatives venue Lighter says deposits and withdrawals have resumed following a November 16 security incident that initially froze access. The latest explanation points to unsafe signing code used by affected trader accounts, not an announced compromise of the protocol’s smart contracts. That distinction is central to the incident: a cryptographic error in an external trading integration can expose account authority even when a venue’s core software behaves as designed.

The on-chain withdrawal was substantial

Blockchain analytics firm Bitquery traced a withdrawal of 10,393,057 USDC from a Lighter-related Ethereum contract on November 16. The funds were converted into ether, and investigators followed part of the subsequent movement through multiple wallets. Those observations establish a visible transfer trail, but they are not the same thing as a complete, audited final-loss figure. Earlier reports also cited higher possible amounts covering more than one account, which Lighter had not confirmed at the time. The safe description is an observed approximately $10.4 million USDC outflow and an incident whose recovery accounting may evolve.

Why nonce reuse can reveal a key

According to Lighter’s reported postmortem, some affected accounts used unofficial or custom signing code that reused one-time cryptographic values, known as nonces. Reusing these values with the wrong signature scheme can allow an attacker to derive secret signing material from information that was supposed to be public. Once an API signing key is compromised, apparently authorized instructions can be sent through normal account capabilities. This is not a conventional stolen-password story, and it underscores why teams should use well-tested official signing libraries rather than copy cryptographic routines into trading bots.

For related context, see our earlier report on the Unocoin wallet incident .

The pause and partial recovery

Lighter activated its Guardian safeguard during the incident, temporarily restricting withdrawals and related activity while its Security Council acted. The exchange says roughly $5 million USDC was returned to affected traders and that Guardian mode was subsequently deactivated. Its official announcements channel states that deposits and withdrawals are back to normal, with pending requests being processed. That $5 million figure should not be described as full recovery of the separately observed $10.4 million transfer. The remaining exposure and final accounting need a detailed reconciled report.

Security changes traders should understand

The venue says it has changed how API signatures are exposed and now requires wallet signatures for transfers into public pools. Further planned controls include IP allowlists, scoped permissions, per-key limits and monitoring for repeated nonces. For a trader using custom automation, the immediate lesson is to audit signing code, rotate uncertain keys and understand what each API credential can authorize. Smart-contract audits remain important, but they cannot substitute for secure key handling in external client software.

Nonce-reuse vulnerabilities are particularly serious because digital signatures rely on the uniqueness and secrecy of certain temporary values. If an attacker can infer a private key from flawed signatures, simply restarting a user interface or changing a password may not fix the exposed credential. The scope depends on which keys were affected and whether they could authorise actions beyond trading. Users should follow the protocol team's specific revocation and key-rotation instructions rather than assuming that reopening withdrawals means every associated security risk has ended.

For related context, see our earlier report on the Kava Lend exploit .

This is now a restoration-and-root-cause story, not simply a withdrawal-halt headline. The strongest follow-up will be a fully reconciled account of losses, recovered funds and the effectiveness of the new controls under live trading conditions.

Reporting sources: Lighter official announcements feed · Bitquery transaction investigation · CoinDesk initial incident coverage

Written by the News Desk and edited by Samuel Rae.

Tuyên bố từ chối trách nhiệm: Bản quyền của bài viết này thuộc về tác giả gốc và không đại diện cho MyToken(www.mytokencap.com)Ý kiến ​​và vị trí; vui lòng liên hệ với chúng tôi nếu bạn có thắc mắc về nội dung
community_x_prefix
X(https://x.com/MyTokencap)
community_tg_prefixcommunity_tg_name
(https://t.me/mytokenGroup)
Đọc liên quan