Lighter's $10M-plus API key exploit shows crypto security must go beyond withdrawal controls
Key Takeaways
- •An attacker exploited compromised API keys to siphon 10.39 million USDC from decentralized perpetual futures exchange Lighter by moving funds into a public pool and redeeming shares through another account.
- •Lighter stated that its protocol and smart contracts were unaffected, indicating the exploit targeted operational credentials rather than on-chain code.
- •The exchange has already implemented mandatory wallet signatures for public pool transfers and made API-key signatures non-public, while IP allowlists and configurable permissions for individual keys remain planned.
- •Lighter restored deposits and withdrawals and returned roughly $5 million in USDC to the affected trader, leaving about half of the stolen funds unrecovered as of the report.
- •The incident demonstrates that security assessments must consider the financial consequences a credential's permissions allow, since API keys with trading powers can still cause losses even when withdrawal controls function as intended.

A recent incident in which more than $10 million was siphoned out of decentralized perpetual futures exchange Lighter has underscored the shortcomings of focusing security solely on withdrawal controls.
According to Lighter's postmortem, an attacker used compromised API keys to move funds into a public pool and redeem shares held through another account. On-chain analytics firm Bitquery traced a withdrawal of 10.39 million USDC. Cointelegraph previously reported that the exchange paused withdrawals after the incident, and Lighter said its protocol and smart contracts were unaffected.
Exchange response
Lighter now requires wallet signatures for transfers into public pools and has made API-key signatures non-public. It also plans to introduce IP allowlists and configurable permissions for individual keys. Of those measures, the wallet-signature requirement and the move to non-public API-key signatures are already in force, while the IP allowlists and configurable permissions remain planned rather than implemented, making their rollout a concrete development to watch.
The exchange has since restored deposits and withdrawals and returned about $5 million in USDC to the affected trader — roughly half of the 10.39 million USDC taken. The remainder had not been returned as of the report.
Lessons beyond smart contracts
The incident highlights how cybersecurity reviews need to look past smart contract vulnerabilities. It is equally important to consider the gap between the permissions a system grants and the financial consequences those permissions allow.
The real risk involving a credential depends on the balances it can reach, the transactions it can initiate and the exposures it can create. Whether it is permitted to withdraw assets, and to which destinations, are just two of many factors. As Lighter put it in its postmortem: “A key that can trade can still lose you money if someone else holds it.”
Exchanges and trading platforms commonly issue API keys so that automated software can place orders without a person signing each transaction, giving such credentials direct trading powers. This means users need to establish a clear mandate for each credential. Such a mandate can specify accessible accounts, permitted markets, order sizes, pricing tolerances and aggregate exposure. Moving capital into a shared pool or expanding those limits can require separate authorization.
The same logic applies to additional signatures. A second signature adds meaningful protection when its approval process independently evaluates a transaction's financial effect.
Source: Cointelegraph