Markets
BTC $55,782 -9.78% ETH $1,561 -10.03% BNB $511 -10.37% XRP $0.8710 -10.07% SOL $65.44 -9.88% LINK $8.06 -8.99% BTC $55,782 -9.78% ETH $1,561 -10.03% BNB $511 -10.37% XRP $0.8710 -10.07% SOL $65.44 -9.88% LINK $8.06 -8.99% TOTAL $1.96T BTC.D 57.2%

Exchanges & Trading

A $10 Million Drain Shows Where DEX Permission Design Fails

Compromised API keys moved funds into a shared pool and redeemed them from another account, exposing risk that withdrawal limits alone cannot stop.

More than $10 million was siphoned out of a decentralised perpetual futures exchange this month without a single smart contract being broken, in an incident that puts API permissions rather than withdrawal controls at the centre of exchange security.

According to the exchange’s postmortem, an attacker used compromised API keys to move funds into a public pool and then redeem shares held through a second account. On-chain analysis traced a withdrawal of 10.39 million USDC. Lighter said its protocol and smart contracts were unaffected — the loss came from how credentials were configured and what they were allowed to reach.

The venue now requires wallet signatures for transfers into public pools, has made API-key signatures non-public and plans IP allowlists plus configurable permissions for individual keys. Deposits and withdrawals have been restored, and about $5 million in USDC has been returned to the affected trader.

The episode matters because the industry’s standard security checklist is built around withdrawals: whitelist addresses, require a second approval, cap daily outflow. That framing assumes an attacker’s goal is to walk funds off the platform. Here the value moved from one account’s control into a pool, then out through a route that looked like a normal redemption, with no withdrawal request that a limit would have caught.

The lesson is that a credential’s real risk is set by the balances it can reach, the transactions it can initiate and the exposures it can create — not only whether it can withdraw. Trading permissions on a perpetual exchange can also be a way to transfer value, through position size, leverage, internal transfers and shared liquidity pools.

The remedy the exchange describes is a mandate for each key: which accounts it can touch, which markets it can trade, order size ceilings, pricing tolerances and aggregate exposure, with separate authorisation required to move capital into a shared pool or raise those limits. Additional signatures only help if the second approver independently evaluates the financial effect of a transaction rather than rubber-stamping a request.

For traders, the practical question to ask any venue is not whether withdrawals are gated but how many paths exist from a stored key to money leaving. For exchanges, the incident is a reminder that pool mechanics designed for capital efficiency create transfer routes that permission reviews tend to miss until someone uses them.

Share this article

Viber uses viber://forward?text= when the app is installed.