Lighter Pauses Withdrawals After Security Incident; Analysts Tie Reported $15.48M Loss to API Keys
Lighter suspended withdrawals and pool creation while it investigates a security incident tied to a compromised external party. Analysts link a reported, still unconfirmed $15.48 million loss from two market-maker accounts to leaked API keys.

Table of Contents
News summary: Lighter, a perpetual futures exchange built as a zero-knowledge (ZK) rollup on Ethereum, said on November 16, 2026, that it is investigating a security incident that "appears to involve a single compromised external party." As a precaution, it suspended all withdrawals and the creation of new pools. Blockchain analysts and several crypto media outlets reported that about $15.48 million was taken from two market-maker accounts, most likely through leaked API keys. Lighter has not confirmed that figure or the exact method as of 15:10 Tehran time (11:40 UTC).
This article separates three things: what Lighter has officially said, what we could check ourselves on public blockchain data and Lighter's public API, and what is still only a claim from analysts or media.
What Lighter has officially said
Lighter's only public statement so far is a post on its official X account (@Lighter_xyz), published at 11:02:33 UTC (14:32 Tehran):
"We are actively investigating a security incident that appears to involve a single compromised external party. As a precaution, we have temporarily suspended all withdrawals and pool creation while we investigate the circumstances and assess the full impact."
Three points are worth noting. First, Lighter calls this a "security incident", not a protocol hack. Second, it points to "a single compromised external party", which suggests the problem started outside Lighter's own systems. Third, it gives no dollar amount, no names of affected accounts, and no timeline for reopening withdrawals. Some outlets wrote that Lighter "stressed" the protocol had no built-in vulnerability. Lighter's published post does not say that, so we treat it as the outlets' reading, not a quote.
What we checked ourselves
We looked at public Ethereum data (via the Blockscout explorer) and Lighter's own public API. These checks back up the main reported figures, but they do not explain how the keys were leaked.
A $10.39 million withdrawal. At 10:11:47 UTC (13:41 Tehran), 10,393,056.79 USDC left Lighter's main Ethereum contract (labelled "Lighter: ZkLighter" on the explorer) for an external wallet that analysts link to the attacker. Transaction:
0x5b6f27ded0e9a66ef6fa107083e28db9914e46d7635cc5112d760b9cb2f958c9. This matches the $10.39 million reported for account #714710.Quick swaps through CoW Protocol. Starting at 10:13 UTC, the same wallet sent USDC in chunks of 1, 2, 5 and 2 million (plus smaller amounts) to the CoW Protocol settlement contract and got ETH back. This fits reports that the funds were turned into ether.
About $15.47 million in "pool profit". Lighter's public API shows an account (#769455) with no trading volume, about $40,000 of pool deposits, and roughly $15.47 million in cumulative pool profit. The figure was about $10.38 million at the 10:00 UTC data point and about $15.47 million at 11:00 UTC. This lines up with the reported total of $15.48 million.
Victim accounts emptied. Accounts #714710 and #714723 show no open positions. Their remaining collateral is about $1,040 and $511.
We could see only one large USDC withdrawal to Ethereum. We could not independently trace the remaining roughly $5.1 million, or the reported route through Hyperliquid. The attacker's wallet also received many look-alike "address poisoning" transfers and fake tokens. These are a common scam to trick people into copying the wrong address. We are not publishing or linking any attacker address.
How the attack reportedly worked (analysts' account)
The step-by-step explanation below comes from on-chain analysts, including MLM and 0xTria as quoted by Wu Blockchain, plus Lookonchain as cited by Crypto Briefing and independent X users. Lighter has not confirmed it.
The attacker got API keys belonging to two large market-maker accounts.
Using those keys, the attacker closed the accounts' open positions, so the balances became USDC.
The attacker created a new public pool with a 0% fee under the victim's control, then deposited about $10,000 to own roughly 99.99% of the pool's shares.
The victim account's USDC was moved into that pool in batches of about $1 million.
The attacker redeemed the pool shares, withdrew the USDC, and swapped it for ETH through CoW Protocol. Cointelegraph and TokenPost later reported that some funds were moved to Hyperliquid to buy Monero (XMR), a privacy coin.
Reports say the two pools were opened at around 09:40 and 10:25 UTC. On-chain, the attacker's wallet deposited 10,200 USDC into Lighter at 10:21:35 UTC, which fits the "about $10,000 per pool" description.
Analysis: why an API-key leak is different from a smart-contract exploit
An API key lets software, such as a trading bot, act on an exchange account without the owner signing every action by hand. Market makers depend on them: they place and cancel thousands of orders a minute, so they cannot approve each one with a wallet.
In a smart-contract exploit, the attacker abuses a bug in the protocol's code, and every user's funds can be at risk. In an API-key compromise, the attacker steals one customer's credentials and acts as that customer. The damage is usually limited to the accounts those keys control. That is why many analysts said "Lighter was not hacked."
The picture is not that simple, though. Lighter's own developer documentation says an API key can trade, run "secure withdrawals" (which only go back to the account's original Ethereum address), and make "same-owner transfers" without a wallet signature. Transfers to a different owner and fast withdrawals do need that signature. If the analysts are right, the attacker used a public pool tied to the victim's own address to get around that limit. In other words, the design let a trading credential become a way to move money out. Some analysts argue this makes the incident partly a platform-design issue, not only the market makers' failure. Lighter's suspension of pool creation fits that concern, but the company has not said this.
Timeline (November 16, 2026)
UTC | Tehran | Event | Status |
|---|---|---|---|
~09:40 | ~13:10 | First 0%-fee public pool reportedly opened on a victim account | Analyst claim |
10:11:47 | 13:41:47 | 10,393,056.79 USDC leaves Lighter's Ethereum contract | Verified on-chain |
10:13–10:46 | 13:43–14:16 | USDC swapped for ETH via CoW Protocol in chunks | Verified on-chain |
10:15–10:45 | 13:45–14:15 | LIT/USDT on Bybit falls from $2.7437 to a low of $2.3279 | Bybit data |
~10:25 | ~13:55 | Second pool reportedly opened | Analyst claim |
11:02:33 | 14:32:33 | Lighter announces investigation; pauses withdrawals and pool creation | Official |
11:09:39 | 14:39:39 | Upbit suspends LIT deposits and withdrawals | Official notice |
11:10:41 | 14:40:41 | Bithumb suspends LIT deposits and withdrawals | Official notice |
11:22 | 14:52 | Reports that funds were moved to Hyperliquid to buy XMR | Media report |
11:30 | 15:00 | Upbit issues a "caution" notice on LIT | Official notice |
How exchanges reacted
South Korea's two largest exchanges acted within minutes of Lighter's post. Upbit suspended LIT (Ethereum network) deposits and withdrawals at 20:09 Korea time (11:09 UTC). It cited "circumstances indicating a security incident" and Article 17 of the enforcement decree of Korea's Virtual Asset User Protection Act. Upbit said the pause would last until it confirms that transfers are stable. At 20:30 Korea time (11:30 UTC), Upbit also published a caution notice (유의 촉구) warning that LIT's price may become more volatile. Bithumb posted its own LIT deposit and withdrawal suspension at 20:10 Korea time (11:10 UTC). Both notices cover deposits and withdrawals of LIT, not trading.
Market impact
The selling started before the official announcement. On Bybit's LIT/USDT market, the 10:15 UTC 15-minute candle opened at $2.7437. The next candle hit $2.3279, about 15% lower. That was around the time the large USDC withdrawal appeared on-chain and community analysts began posting about it. LIT then partly recovered. CoinGecko listed LIT at $2.58 (USD) at 11:39 UTC (15:09 Tehran), down 14.3% over 24 hours. Earlier reports gave different intraday drops, from "more than 7%" (Crypto Briefing) to "more than 17%" (Wu Blockchain), depending on when the price was checked. This is context, not a price forecast.
For context on how fast leverage-heavy derivatives venues can move, see our report on Aster's 24% spike and 32% crash.
What users should do and what to watch
Do not rush. Withdrawals are paused for everyone. Reports say Lighter's separate deployment on Robinhood Chain has no public-pool function, but Lighter has not commented on that.
Review your API keys. If you use bots or third-party tools on any exchange, revoke keys you don't need, keep separate keys for each workload, and use read-only tokens for dashboards. Lighter's documentation recommends read-only tokens for tools and AI agents.
Watch for recovery scams. After incidents like this, fake "refund" sites and direct messages often appear. Trust only Lighter's official channels.
Watch for: Lighter's post-mortem, any confirmed loss figure, any compensation plan, when withdrawals and pool creation reopen, and any change to what API keys are allowed to do.
Leaked credentials, rather than code bugs, are behind a growing share of losses. In a similar case this month, Proxima's users were drained after private keys leaked through monitoring logs. In another, Luxor confirmed a breach of its Commander tool behind a Bitcoin hashrate hijack.
Background: what is Lighter?
Lighter is a decentralized exchange for perpetual futures. It runs as an Ethereum Layer 2: orders are matched off-chain, and the results are proven with zero-knowledge circuits and settled on Ethereum. User funds sit in its Ethereum contract. Lighter also offers spot markets and "public pools", where users can deposit funds into a strategy run by a pool operator. Its native token is LIT, which trades on Lighter and on centralized exchanges such as Bybit, Upbit and Bithumb.
FAQ
Was Lighter hacked?
Lighter says the incident "appears to involve a single compromised external party." Analysts point to leaked market-maker API keys rather than a bug in Lighter's contracts. Some also say Lighter's transfer and pool permissions made the theft possible. A final cause has not been confirmed.
How much was lost?
About $15.48 million has been reported by Crypto Briefing, TokenPost and Wu Blockchain, citing analysts. Lighter's public API data and an on-chain $10.39 million withdrawal back this up, but Lighter has not confirmed a figure.
Are regular users' funds affected?
According to reports, only two market-maker accounts lost funds. Every user's withdrawals are paused for now, though.
When will withdrawals reopen?
Lighter has not given a date.
Sources
Lighter (@Lighter_xyz), official X post, Nov 16, 2026, 11:02 UTC: x.com/Lighter_xyz/status/2122284181422284986
Crypto Briefing, "Lighter faces suspected $15.48 million drain from two market maker accounts", Nov 16, 2026, 06:13 EST: cryptobriefing.com
TokenPost, Nov 16, 2026, 06:20–06:29 EST: drain report, Hyperliquid/Monero report, Upbit/Bithumb report
Wu Blockchain on X, Nov 16, 2026, 11:10 UTC: x.com/WuBlockchain/status/2122286282734973246
Cointelegraph on X, Nov 16, 2026, 11:22 UTC: x.com/Cointelegraph/status/2122289158450512357
Upbit notices No. 6782 and 6783, Nov 16, 2026, 20:09 and 20:30 KST: upbit.com notice 6782, notice 6783
Bithumb notice, Nov 16, 2026, 20:10 KST: feed.bithumb.com/notice/1655678
Lighter Docs, "API keys" (permissions table): docs.lighter.xyz
Price data: Bybit public API (LITUSDT 15-minute candles) and CoinGecko, retrieved Nov 16, 2026, 11:39–11:40 UTC.
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





