Lighter Resumes Trading After Nonce-Reuse Bug Leaked API Secrets
How the Nonce-Reuse Error Worked
Decentralized derivatives exchange Lighter has restored deposit and withdrawal functions following a security incident on November 16. The breach stemmed from a nonce-reuse error that temporarily exposed trader API keys. The platform confirmed the fix and returned to normal operations.
Breaking news:
The incident began when a software flaw allowed repeated nonce values to be used in API requests. This error made it possible for attackers to intercept and reuse authentication tokens. Lighter identified the root cause and deployed a patch within hours of detection.
What Traders Should Check Now
In secure API communication, a nonce is a one-time value that prevents replay attacks. When the same nonce is reused, an attacker can capture a valid request and resend it later. Lighter's bug allowed exactly this. Traders using the API found their keys exposed during the window of the flaw. The exchange stated that no funds were lost, but the exposure was real.
Users of Lighter's API should rotate their keys immediately. Even if no funds were stolen, compromised keys remain a risk if not refreshed. The exchange recommends generating new key pairs and updating trading bots. This step ensures that any captured old keys become invalid.
Did Lighter lose any customer funds in the incident? No. The exchange confirmed that no customer funds were lost. The issue was limited to API key exposure, not a direct drain of balances.
Frequently Asked Questions
How long did the outage last? Deposits and withdrawals were paused during the fix window. Normal operations resumed once the nonce-handling code was corrected and tested.
Should I change my API keys even if I wasn't using the API? Yes. If your account had API keys enabled, rotate them regardless of usage. This eliminates any risk from keys that may have been captured during the bug window.
More stories: