Tonight’s tea-room chat is about something serious—Lighter has had an incident.
Just saw the news: perpetuals platform Lighter may have suffered a security incident. The bottom line: its smart contracts weren’t compromised. An API key for a trader’s account was leaked, and the attacker used it to siphon off around 10.39 million USDC.
$LIT briefly dropped more than 17%. It’s now hovering around $2.67, down nearly 9% in 24 hours, with almost $200 million in contract trading volume—the market is genuinely spooked.
The attacker’s approach was pretty “professional” (to quote SlowMist’s Cos): some of the stolen funds were converted to ETH and moved around in smaller amounts, while some have already been used to buy 2,240 Monero (XMR) through Hyperliquid. The laundering operation is already underway. Upbit and Bithumb have suspended LIT deposits and withdrawals.
The latest update from the team: the protocol and smart contracts themselves are unaffected. Withdrawals are still paused, and they’re aiming to upgrade the contracts and restore withdrawals as much as possible by the end of today. One more update: PANews says the leak may be linked to market maker Abraxas Capital—but “may be” is the key phrase here. Let’s wait for confirmation.
In plain English: with a key leak, you’re protecting against “people,” not “code.” Even the biggest platform can be exposed through one leaked API key. If you trade contracts, it’s definitely worth checking your API permissions tonight.
Do you usually disable withdrawal permissions for your API keys? Or… have you never even thought about it?
Just saw the news: perpetuals platform Lighter may have suffered a security incident. The bottom line: its smart contracts weren’t compromised. An API key for a trader’s account was leaked, and the attacker used it to siphon off around 10.39 million USDC.
$LIT briefly dropped more than 17%. It’s now hovering around $2.67, down nearly 9% in 24 hours, with almost $200 million in contract trading volume—the market is genuinely spooked.
The attacker’s approach was pretty “professional” (to quote SlowMist’s Cos): some of the stolen funds were converted to ETH and moved around in smaller amounts, while some have already been used to buy 2,240 Monero (XMR) through Hyperliquid. The laundering operation is already underway. Upbit and Bithumb have suspended LIT deposits and withdrawals.
The latest update from the team: the protocol and smart contracts themselves are unaffected. Withdrawals are still paused, and they’re aiming to upgrade the contracts and restore withdrawals as much as possible by the end of today. One more update: PANews says the leak may be linked to market maker Abraxas Capital—but “may be” is the key phrase here. Let’s wait for confirmation.
In plain English: with a key leak, you’re protecting against “people,” not “code.” Even the biggest platform can be exposed through one leaked API key. If you trade contracts, it’s definitely worth checking your API permissions tonight.
Do you usually disable withdrawal permissions for your API keys? Or… have you never even thought about it?