0x7874cda67874…7874cda9
Lighter Halts Withdrawals After API Key Hijack of Two Market Makers
Lighter halted withdrawals after attackers hijacked API keys of two market makers, draining USDC in $1 million increments. Withdrawals expected to resume by end of November 16.

Outputs
Lighter attributed the incident to hijacked API keys of two market makers, not a protocol vulnerability.
Withdrawals are expected to resume by the end of November 16 after contract upgrades.
The attacker withdrew USDC in increments of approximately $1 million and converted funds to ETH via CoW Protocol.
Lookonchain reported the attacker moved funds to HyperLiquid and bought XMR.
$LIT fell 7.4% to $2.5 following the attack allegations.
Lighter, the decentralized derivatives exchange, has halted withdrawals after attackers hijacked API keys belonging to two market maker organizations, the platform's team said in an official statement. The team was explicit that the incident did not stem from a security vulnerability in the protocol itself. Withdrawals are expected to resume by the end of November 16, following completion of contract upgrades.
The company also confirmed that Guardian mode has been enabled in the smart contract to prevent potential further losses. A wallet believed to belong to the attacker has been identified, and the community has flagged the address.
The distinction the team drew matters for practitioners. A compromised protocol means broken cryptography or contract logic, a systemic event. Compromised API keys at third-party market makers mean the failure sat in operational security outside Lighter's contracts — a different threat model, a different remediation path, and a materially different set of counterparties reviewing their key management this week.
How did the attacker move the funds?
On-chain analyst MLM published an initial reconstruction of the exploit. The attackers first compromised the market makers' API keys, then closed the open positions in the affected accounts. Next, they created a zero-fee public liquidity pool and withdrew USDC from the system in increments of approximately $1 million each.
The withdrawn funds were then converted to Ethereum (ETH) through the CoW Protocol, a batch-auction settlement system. According to on-chain analytics platform Lookonchain, the attacker subsequently moved the stolen capital to HyperLiquid and used it to purchase XMR, the privacy-focused cryptocurrency long associated with difficult-to-trace transfers.
The routing tells its own story. Closing positions first suggests deliberate account preparation rather than a smash-and-grab. Incremental withdrawals near the $1 million mark indicate an attempt to stay below thresholds that trigger faster scrutiny. The final hop into a privacy coin via an intermediary exchange layer is a laundering pattern that compliance teams and forensic investigators will recognize.
What does this change for market makers and users?
For market makers operating on decentralized exchanges, the incident reframes API key security as a first-order operational risk, comparable in consequence to a contract exploit even when the protocol itself is sound. Expect internal reviews of key rotation, withdrawal permissions and IP restrictions.
For users, the immediate consequence is the withdrawal freeze through the end of November 16. The team's framing — a contract upgrade as the gating item for resumption — signals that the remediation involves code changes, not merely a key revocation. Guardian mode, meanwhile, now stands as the live control standing between the attacker and any residual access.
Market reaction
The platform's native token, $LIT, came under selling pressure following the attack allegations. The token fell 7.4% within hours, dropping to $2.5. The decline reflects repricing of operational risk rather than any change to token mechanics.
What comes next
The near-term checkpoints are concrete: completion of the contract upgrade, reactivation of withdrawals by the end of November 16, and continued on-chain tracking of the flagged attacker wallet as it moves through HyperLiquid and into XMR. Whether the community flagging and the Guardian-mode controls contain further losses will determine whether this incident remains a market-maker security failure or escalates into a broader confidence event for the exchange.
via cryptonews.net (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles