0x231ca522231c…231ca525

ConfirmedSecurity555 vB166 sat/vB3 min decode

Lighter’s $10.39 Million API-Key Incident Exposes Permission Risk

Bitquery traced 10.39 million USDC leaving Lighter after compromised API keys funded a public pool. The exchange restored transfers and began tightening credential permissions.

Lighter incident exposes risks beyond withdrawal controls
WitnessLighter incident exposes risks beyond withdrawal controlsPIX1861 / pixabay

By Tom Whitfield

An attacker withdrew 10.39 million USDC from decentralized perpetual futures exchange Lighter by using compromised API keys, according to Bitquery’s on-chain tracing and Lighter’s postmortem. Lighter said the incident did not affect its protocol or smart contracts.

How did compromised credentials move the funds?

Lighter’s postmortem said the attacker used compromised API keys to move funds into a public pool and redeem shares held through another account. The sequence placed the loss within the exchange’s permission system rather than a smart-contract vulnerability.

Bitquery traced a 10.39 million USDC withdrawal, confirming a loss above $10 million. Lighter said it has since restored deposits and withdrawals and returned about $5 million in USDC to the affected trader.

What controls has Lighter changed?

Lighter now requires wallet signatures for transfers into public pools. It has also made API-key signatures non-public, removing those signatures from public display.

The exchange plans IP allowlists and configurable permissions for individual keys. Those controls would limit where a key can operate and which actions it can initiate, but Lighter described both measures as planned rather than completed.

The immediate changes address two points in the incident: public-pool transfers and API-key signature visibility. The proposed allowlists and per-key permissions would extend that response to a credential’s operating scope, but Lighter lists both as future controls.

What can a trading API key actually do?

Lighter said: “A key that can trade can still lose you money if someone else holds it.” Its postmortem treats withdrawal rights and destination controls as only two elements of credential risk, alongside balances a key can reach, transactions it can initiate and exposures it can create.

The incident demonstrates why withdrawal restrictions alone do not capture a credential’s financial reach. Compromised keys enabled movement into a shared pool and redemption of shares through another account, while the underlying protocol and smart contracts remained unaffected.

For an exchange, that expands the security perimeter from contract code to the trading and administrative layer. A contract review tests code; a credential review tests the balances, transactions and destinations available to a key.

Lighter’s postmortem recommends a clear mandate for each credential. A mandate can specify accessible accounts, permitted markets, order sizes, pricing tolerances and aggregate exposure.

The analysis also recommends separate authorization when a key moves capital into a shared pool or expands those limits. That step separates routine trading authority from actions that redirect funds or increase account exposure.

A second signature adds meaningful protection when its approval process independently evaluates the transaction’s financial effect, the postmortem says. A confirmation process that does not make that evaluation would not provide the independent check described in the analysis.

What should traders verify now?

Traders should inventory each API key’s reachable balances, permitted markets, order limits, pricing tolerances, aggregate exposure and destination rights. They should also test whether a key can fund a public pool or redeem shares through a different account, the route used in this incident.

Lighter has restored deposits and withdrawals and returned about $5 million in USDC to the affected trader. The next control milestone is the rollout of IP allowlists and configurable per-key permissions; the postmortem provided no timetable, leaving the revised model unmeasured against another incident.

via cryptonews.net (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles