Lighter stated that a leak of API keys resulted in users' funds being stolen, and approximately 5000000 USD USDC has been recovered.
BIBIBI
AT A GLANCE
Lighter stated that the attacker used a repeated signature nonce to reverse-engineer the API key and steal funds, and the report headline claimed that approximately 5000000 USD USDC has been recovered.
Article
Lighter issues a security incident statement: User funds were stolen due to an API key leak, and approximately 5000000 USD USDC has been recovered
PANews November 17 report, Lighter officially released a security incident statement stating that an attacker stole funds by obtaining traders' leaked API keys. This incident was not caused by vulnerabilities in the Lighter protocol, smart contracts, or infrastructure, but rather by affected accounts using unofficial signing code and reusing signature nonces (Nonces), allowing attackers to reverse-engineer API private keys from public signature data. Lighter stated that the affected accounts reused Nonces in their signing code, enabling attackers to calculate the relevant API keys without accessing the accounts or Lighter system, and use the leaked keys to create public liquidity pools, transfer account funds, and redeem withdrawals. After the incident occurred, Lighter's smart contract Guardian mechanism detected abnormal...
PANews relayed Lighter's official security incident statement on November 17.
02
Lighter stated that the affected accounts used unofficial signed code and reused signature nonces, enabling attackers to reverse-engineer the API private key from public signature data.
03
Lighter stated that the attacker used the leaked key to create a public funding pool, transfer account funds, and redeem withdrawals.
04
Lighter stated that this incident was not caused by any vulnerabilities in its protocols, smart contracts, or infrastructure.
05
The report title states that approximately 5000000 USD USDC has been recovered, but the provided text does not elaborate on the relevant details.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
According to Lighter, the problem lies in the unofficial signature code used by the affected accounts: reusing Nonce allows attackers to calculate the API private key from the exposed signature data, and then transfer funds using that key. This is the official explanation for the cause, not an independent verification conclusion.
Why it matters to readers
This incident demonstrates that, according to the official account, even without access to accounts or platform systems, attackers can exploit issues with signed code to obtain keys and steal funds; whether the funds can be recovered still depends on a comprehensive assessment of the handling procedures.
Do not interpret “non-platform vulnerabilities” as meaning that there is no risk to account funds. This explanation involves unofficial signed codes and the repeated use of Nonce; the term “recovered” in the title does not mean that it has been returned to users.
Risks and unknowns
The text is cut off at the description of the Guardian mechanism detection event, and the subsequent detection and handling process is incomplete.
Approximately 5000000 USD USDC has been recovered, but it is only mentioned in the title. The method of recovery, where the funds went, and whether they were returned to the user are not specified.
The number of affected accounts, total losses, and whether there is still unrecovered money are not specified.
The judgment on the cause of the incident and non-platform vulnerabilities comes from the Lighter statement; there is no independent verification information in the provided materials.
Related Developments
Loading event timeline…
Related concepts
API Key
A credential that allows a program to access an account’s API; its executable scope is determined by permissions such as reading, trading, transferring, or withdrawing.