Newsroom

Lighter Halts Withdrawals After $15.5 Million Incident Tied to Leaked Trader API Key

17 November, 2026   /   News   /  AI   /   Tags:  lighter, leaked, withdrawals, upgrade, smart

Lighter Halts Withdrawals After $15.5 Million Incident Tied to Leaked Trader API Key

Decentralized perpetual futures platform suspends activity while investigating compromised market-maker credentials and preparing contract upgrades

Decentralized perpetual futures exchange Lighter temporarily suspended all withdrawals and the creation of new liquidity pools on November 16 following a security incident that drained an estimated $15.5 million in USDC from two market-maker accounts. The platform stated that the event stemmed from a leaked API key belonging to a trader account rather than any vulnerability in its core protocol or smart contracts.

Lighter initially described the matter as involving a single compromised external party. It later clarified that its investigation pointed to leaked credentials for a specific trader’s account. As a precaution, the exchange enabled Guardian mode on its smart contracts and said its Security Committee would carry out an upgrade. The team targeted completion of the upgrade and restoration of withdrawals by the end of the same day, while identifying recovery of funds linked to additional withdrawal attempts as its top priority.

How the Incident Unfolded

On-chain analysis indicated that the attacker gained access through API keys associated with two large market-maker accounts. Those keys permitted the closing of existing trading positions and conversion of holdings into USDC. The attacker then created a public liquidity pool with a zero fee under one of the compromised accounts, deposited a small amount of capital to secure nearly full ownership, transferred the victims’ USDC into the pool in successive batches, and redeemed the pool shares to extract the funds.

Researchers identified losses of approximately $10.39 million from one account and $5.09 million from a second, for a combined total near $15.5 million. The method exploited the platform’s handling of transfers between accounts linked to the same Layer 1 address, which do not require an additional wallet signature in the same way external transfers do.

Our investigation indicates that today’s incident was caused by a leaked API key for a specific trader's account. The Lighter protocol and smart contracts are unaffected.
Lighter

A wallet linked to the activity withdrew roughly $10.39 million in USDC from Lighter’s Ethereum Layer 1 settlement contract. The funds were rapidly swapped into approximately 5,400 to 5,764 ETH through CoW Swap. Portions were then split into smaller transfers of about 160 ETH each and moved across multiple addresses, with some directed toward Hyperliquid for purchases of XMR1.

Platform Response and Market Reaction

Lighter confirmed that its protocol and smart contracts remained unaffected. Withdrawals and new pool creation stayed suspended while the contract upgrade proceeded. The exchange has not publicly detailed how the API key was exposed, the precise changes included in the upgrade, or whether the affected trader accounts would receive reimbursement.

The native LIT token came under selling pressure after the reports surfaced. Prices fell more than 15 percent at points during the session, with trading levels later reported in the $2.50 to $2.67 range. Certain South Korean platforms, including Upbit and Bithumb, temporarily suspended LIT deposits and withdrawals in response.

Lighter continues to expand its derivatives infrastructure, including an EVM development network launched in October that supports smart-contract management of orders and asset movement between its Ethereum-compatible environment and Lighter Core. The platform also maintains a partnership that enables eligible users of Robinhood Wallet to access perpetual futures trading through its systems.

As of the latest updates, withdrawals had not yet resumed and the contract upgrade had not been confirmed complete. Recovery of remaining funds associated with the attacker’s subsequent attempts remained the stated priority.

Disclaimer
This article was generated by AI using information from multiple industry sources. It has not been reviewed or verified by a human editor and may contain inaccuracies, omissions, or misinformation. Readers are encouraged to independently verify any information before making decisions based on its content.
This article is for informational purposes only and does not constitute financial, legal, or investment advice. Cryptocurrency and related investments involve substantial risk, and past performance does not guarantee future results.