0x58e19c1558e1…58e19c12
Lighter’s $15.5M Outflow May Involve Leaked Market Maker Keys
An analysis links Lighter’s roughly $15.5 million outflow to leaked API keys from two market-maker accounts, describing a 0% fee pool and a same-address transfer path.

Outputs
About $15.5 million was affected in the reported Lighter outflow.
Account #714710 lost about $10.39 million, while account #714723 accounted for about $5.09 million.
The attacker reportedly deposited about $10,000 to secure 99.99% of a public pool with 0% fees.
Victims’ USDC reportedly entered the pool in increments of roughly $1 million before redemption.
BlockBeats reported the analysis on November 16.
About $15.5 million left decentralized derivatives exchange Lighter in an incident that an analysis linked to leaked API keys for two large market-maker accounts, BlockBeats reported on November 16.
The report cited Predicts.guru founder 0xTria, who in turn cited analysis by an unnamed Korean trader. 0xTria said the incident “may have stemmed from leaked API keys” for the accounts, rather than an exploit of Lighter’s protocol itself.
How did the attacker move the funds?
According to the analysis, the attacker first closed positions in the affected accounts. The attacker then created a public pool with 0% fees in the victims’ names.
After depositing about $10,000, the attacker secured 99.99% of the pool shares. The attacker then moved the victims’ USDC into the pool in increments of roughly $1 million and redeemed it. That sequence turned the pool’s dominant share into the mechanism for extracting the balances, according to the analysis.
No direct, unrestricted transfer authority through the API keys was required. Lighter’s API keys cannot directly transfer funds to other users, BlockBeats said. The report instead pointed to two account-level rules:
- Transfers between accounts linked to the same Layer 1 address reportedly did not require a separate signature.
- A pool created by a victim account was treated as owned by that account.
The attacker appears to have combined those permissions with the leaked credentials. The same-address rule allowed funds to move between linked accounts without another signing step, while account-linked pool ownership made the attacker’s 99.99% share redeemable against the victims’ USDC.
How much was affected?
The analysis assigned most of the estimated loss to account #714710 and the remainder to account #714723:
- Account #714710: about $10.39 million.
- Account #714723: about $5.09 million.
- Combined estimate: roughly $15.5 million.
The figures cover funds affected through the two accounts. They do not represent a protocol-wide user balance or a loss attributed across all Lighter pools, because the report identified the issue as two compromised market-maker accounts operating through a linked account structure.
What does the API-key theory change?
It changes where the immediate security response sits. If the report’s account is correct, an attacker did not need to exploit Lighter’s protocol; leaked API credentials may have supplied enough authority to close positions, establish the pool and trigger the redemption path.
For Lighter, restricting what API keys can do may not prevent losses if linked-account permissions and pool ownership can recreate a transfer route. For market makers, the episode shows why operators must assess the consequences of account relationships, not merely the direct transfer permissions attached to an API credential.
The report did not identify the market maker, the Korean trader or the two accounts by an off-chain name. It also presented no evidence of a protocol exploit, limiting conclusions about the attack’s motive, the extent of the credential exposure or whether other linked accounts face the same risk.
If Lighter leaves same-address transfers without a separate signature and the treatment of pools created by a linked account unchanged, compromised API credentials retain the reported route from position closure to redemption, the mechanism behind roughly $15.5 million in losses.
via en.bloomingbit.io (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,514 articles