Lighter loses over $10M after attacker abuses compromised API keys

Editorial illustration: Metallic spheres flow from a glass reservoir through a gold valve beneath two keys, into a circular pool and out through a curved pipe into a tray.

In brief

  • Lighter's postmortem says an attacker used compromised API keys to move funds into a public pool.
  • Bitquery traced a 10.39 million USDC withdrawal; Lighter says its smart contracts were unaffected.
  • Lighter restored deposits and withdrawals and returned about $5 million USDC to the affected trader.
  • Cointelegraph's analysis argues each credential needs a mandate covering markets, order sizes and aggregate exposure.

How the funds moved

Lighter's own account doesn't describe a code bug. Per the postmortem cited by Cointelegraph, compromised API keys were enough to push funds into a public pool and then redeem shares through a separate account. The exchange said its protocol and smart contracts weren't affected.

By Lighter's account, the code held and the keys didn't.

The on-chain trail is visible, too. Bitquery traced a withdrawal of 10.39 million USDC, according to Cointelegraph's report.

What Lighter has changed

Lighter has since restored deposits and withdrawals and returned about $5 million in USDC to the affected trader, Cointelegraph reported. It's also tightened the route the attacker used. Transfers into public pools now require wallet signatures, and API-key signatures are no longer public.

More is planned. The exchange said it intends to add IP allowlists and configurable permissions for individual keys (so a single credential wouldn't carry blanket access).

Cointelegraph's case for wider limits

The Cointelegraph analysis argues the lesson sits outside the smart contracts. Security reviews, it said, need to look past contract vulnerabilities, because a credential's real risk depends on what balances it can reach and what transactions and exposures it can create.

Its proposed answer is a mandate for each credential. That mandate would spell out accessible accounts, permitted markets, order sizes, pricing tolerances and aggregate exposure. Under that model, moving capital into a shared pool (or expanding a key's limits) can require separate authorization rather than riding on the original key.

The analysis also put a condition on second signatures. One only adds meaningful protection, it argued, when the approval process independently evaluates the transaction's financial effect, not just whether a valid signature showed up.

For defi venues that let traders plug in API keys, that's a broader checklist than withdrawal controls alone.

Frequently asked questions

How were funds taken from Lighter?

According to Lighter's postmortem as reported by Cointelegraph, an attacker used compromised API keys to move funds into a public pool and redeem shares held through another account. Bitquery traced a withdrawal of 10.39 million USDC. Lighter said its protocol and smart contracts were unaffected.

What has Lighter changed since the incident?

Lighter now requires wallet signatures for transfers into public pools and has made API-key signatures non-public. It plans IP allowlists and configurable permissions for individual keys. The exchange has also restored deposits and withdrawals and returned about $5 million in USDC to the affected trader.

What controls does the Cointelegraph analysis recommend for API credentials?

The analysis suggests a mandate for each credential specifying 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. It argues a second signature adds meaningful protection only when its approval process independently evaluates the transaction's financial effect.