
$LIT news
Every $LIT story, instantly, with how the price moved after each one.
Top stories
- Lighter just got drained 10mil usdc. Yikes. jpegtrader
- Good afternoon lads It seems that Lighter is getting exploited. It is what it is. On an unrelated note, Haiparlicuid lost it's 200D EMA/MA combo and retested it from the bottom Not great Lord TradfiDrake
- 🚨 On-Chain Update: Tracking tools have flagged notable activity on wallet 0xb3fffca23d4444eE73349825ACD84f7b5020e387 👀 📊 Following a 10.39M USDC withdrawal from Lighter (@Lighter_xyz ) and an ETH swap via CoW Protocol, the address executed multiple 160 ETH transfers to wallets closely resembling its previous destinations—a pattern often associated with Address Poisoning attempts. ⚠️ Note: The nature of these transfers remains unconfirmed and may represent routine wallet management rather than a loss of funds. As always, verify full addresses carefully before transacting. 🔍 $LIT COINOTAG NEWS
- 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. Lighter
- [ ZOOMER ] LIGHTER TO APPLY FOR A US LICENSE NEXT MONTH, SAY THEY WILL INTEGRATE INTO ROBINHOOD'S US OFFERING ONCE APPROVED: INVESTOR CALL zoomer
- Ruh Roh SM17
- The perpetual futures market just got a new ticker. ⚡ The 21shares Lighter ETP (ticker: LIHT) is now live on Xetra. Lighter (LIT) is a high-performance decentralised exchange specialising in perpetual futures across crypto, equities, FX, and commodities, with an economic model that directs exchange revenue toward token buybacks. Meet LIHT: no crypto wallets. No seed phrases. Just physically backed, exchange-traded exposure to Lighter. Read the full press release: 21shares
- BITHUMB flagged $LIT for caution trading. COINOTAG NEWS
- Wooha, what's going on with lighter? $LIT -20% sk1337le
- $LIT nuked…one after another: - ostium - drift - arcus - lighter one of the most profitable perp dexes got exploited…a16z backed very bad optics arndxt
Latest
- UPDATE: Lighter said deposits and withdrawals resumed after its Security Council switched off Guardian Mode, and that the council returned about $5 million in USDC to the affected trader. Lighter traced the API key leak to signing code outside its official SDKs and said its protocol and smart contracts were unaffected. The Block
- #Lighter Incident Breakdown: Nonce Reuse in Custom Signing Code Enabled API Private Key Recovery 1️⃣ Affected Accounts An attacker derived the API private keys for two trading accounts on Lighter and used them to move funds out of those accounts. Approximately $15.48M was reportedly affected, with around $5M in USDC recovered and returned to the affected trader by the Lighter Security Council. Reported affected accounts: Account 1: Lighter Account ID: 714710 Associated onchain address: 0x0d1D09312665D31Ed68231b88079a245E0458F6F Amount affected: ~$10.39M Account 2: Lighter Account ID: 714723 Associated onchain address: 0x66Cf2f85115CC20bF439720927C1f93De9672068 Amount affected: ~$5.09M 2️⃣ Root Cause The affected accounts used insecure, unofficial signing code that reused cryptographic signing nonces across different transactions. This allowed the attacker to derive the API private keys from publicly available signatures. Lighter said its protocol, smart contracts, and official SDKs were unaffected. The attacker moved the funds through the following sequence: Create a public pool using the compromised account → Mint pool shares to an attacker-controlled account → Transfer the victim’s funds into the pool, increasing its net asset value (NAV) without issuing corresponding shares to the victim → Redeem the attacker’s shares and withdraw the funds. 3️⃣ Funds Withdrawn The attacker withdrew approximately 10.39M USDC from Lighter and swapped the proceeds for ETH. Onchain tracing identified part of the proceeds moving through multiple wallets to buy XMR1 on Hyperliquid. XMR1 should not be conflated with native Monero ($XMR). The available evidence does not establish that these purchases drove up Monero’s price. 4️⃣ Reported Attacker Account and Address Lighter Account ID: 769455 Associated onchain address: 0xb3fffca23d4444eE73349825ACD84f7b5020e387 🛡️ Security Recommendations ▪️ Use Lighter’s official Python, Go, or TypeScript SDKs, or its Agent Kit. Avoid implementing your own signing logic. ▪️ Let the official signer handle cryptographic signing nonces. Never reuse a signing nonce or substitute timestamps, counters, weak random values, or cached values. Signing nonces are distinct from transaction nonces. ▪️ If your code may have reused signing nonces, revoke and replace all related API keys immediately. Fixing the code alone isn’t enough. ▪️ Enable IP allowlisting and per-key permissions and limits as they become available. Separate permissions for trading, transfers, pool creation, and redemptions wherever supported. ▪️ Lighter now requires wallet signatures for transfers into public pools and no longer exposes API signatures publicly. GoPlus Security 🚦
- Lighter Security Incident Update: Approximately 5M USDC Returned to Affected Trader, Withdrawals Resumed Lighter said in its November 16 security incident report that an attacker exploited nonce reuse in unofficial signing code used by certain trading accounts to derive API private keys from public signatures. The attacker then created a public pool through a compromised account, transferred funds into the pool, and extracted assets by redeeming pool shares through an attacker-controlled account. Lighter confirmed that its protocol, smart contracts, infrastructure, and official SDKs were unaffected. The incident triggered its smart contract-based Guardian mechanism, temporarily pausing withdrawals and allowing the Security Council to return approximately 5 million USDC to the affected trader. Withdrawals have since resumed, with pending requests being processed. Lighter has implemented wallet signature requirements for public pool transfers and made API key signatures non-public. It also plans to introduce IP allowlists, per-key permissions and limits, and proactively monitor and revoke API keys at risk from nonce reuse. Wu Blockchain
- Signing Safely on Lighter: Lessons from November 16 TLDR • On the morning of November 16 (UTC), an attacker gained control of a trader’s API keys and withdrew funds from them. • The Lighter protocol, smart contracts and infrastructure were not affected. • The API keys leaked through the accounts’ own signatures. The affected accounts used unsafe signing code other than the official Lighter SDKs, and that code reused signing nonces, which made the private keys recoverable from public data. • The official Lighter SDKs generate nonces safely and were not affected. If you trade programmatically or run agents on Lighter, please use the official SDKs. • We’re adding further protections, including IP allowlists and configurable limits per API key, so that a leaked key can do far less damage. Fund recovery Our smart contract Guardian was triggered by the anomaly, which temporarily paused withdrawals and allowed ~5MM USDC to be returned to the affected trader by the Lighter Security Council. Guardian mode has now been disabled. Withdraws are now unpaused and all pending withdrawals are being processed. What is nonce reuse? Every transaction on Lighter is authorized by a signature from an API key. Each signature uses a one-off random value called a nonce, which must be unique and unpredictable every time. Signatures are public. If the same nonce is used with the same key to sign two different transactions, anyone can calculate the private key from those two signatures. After that the key is exposed, and needs to be rotated. This issue isn’t specific to Lighter - the above applies to Bitcoin and Ethereum signatures as well. How it happened 1. Key leak. The affected accounts’ signing code had been reusing nonces. Because signatures are public, the attacker could calculate those accounts’ API keys from public data. They needed no access to the accounts or to Lighter’s systems. 2. Moving the funds. An API key can send funds to its own account’s sub-accounts, and a public pool the account creates counts as one. The attacker used the leaked key to: • Create a public pool from the affected account. • Mint pool shares in a separate, attacker-controlled account. • Transfer the affected account’s funds into the pool, increasing NAV without minting pool shares. • Redeem their shares and withdraw. What else a leaked key could be used for An API key can’t withdraw funds to anyone else’s wallet. Withdrawals only ever go to the account owner’s own wallet. But a key that can trade can still lose you money if someone else holds it. Besides the pool route above, the main risks are: • Trading against you. Someone holding your key could place orders from your account that trade against their own orders at bad prices, moving value from you to them. This works best in thinly traded markets, where there are few other orders in the way. • Taking on risky positions. They could open large or highly leveraged positions in your account, exposing it to heavy losses or liquidation. What we’re doing • IP whitelists for API keys, so a key can only be used from the server you choose. • Permissions and limits you can configure per API key, such as which actions a key may take and which markets it can trade. • Monitoring signatures for nonce reuse, contacting affected accounts directly, and proactively voiding affected API keys. What we’ve done • Requiring a wallet signature to transfer funds to a public pool, so an API key alone can’t do this. • Making API key signatures non-public. Keep your keys safe • Sign with an official Lighter SDK (Python, Go, TypeScript or the Agent Kit). They generate every nonce with a cryptographically secure random number generator. • If you use your own or third-party signing code, never derive a nonce from a timestamp, a counter, a weakly seeded random number generator, the transaction’s contents or a cached value. Use a cryptographically secure random number generator for every signature. • Store keys securely and never share them or commit them to code repositories. • If you’re unsure whether your code has ever reused a nonce, rotate all of your API keys and switch to an official SDK. Our channels remain open for any questions and feedback from the community. Lighter
- UPDATE: Lighter said a leaked API key for one trader's account appeared to be behind the incident and that its protocol and smart contracts were unaffected. Withdrawals remain paused, with Lighter aiming to resume them by the end of the day. The Block
- It appears that Abraxas Capital is the market maker whose API keys on Lighter were leaked. Abraxas Capital is now closing short positions on Hyperliquid and withdrawing funds. Over the past 24 hours, its account value on Hyperliquid has dropped by $150M, while its short positions have shrunk to $70M. Lookonchain
- Update: 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. As a precaution, we have enabled Guardian mode on our smart contract. Our main priority is to recover funds involved in an additional withdrawal attempt by the attacker. This upgrade will be performed by the Lighter Security Council. Withdrawals remain temporarily paused. Our current target is to complete the contract upgrades and resume withdrawals by the end of today. We have identified the wallet believed to be associated with the attacker, which has also been flagged by the community: 0xb3fffca23d4444eE73349825ACD84f7b5020e387 Lighter
- ⚠️ Lighter Exploiter Report $10.4M USDC withdrawn from Lighter Main wallet: 0xb3fffca23d4444eE73349825ACD84f7b5020e387 Funds swapped to $ETH and being converted to $XMR1 (wrapped Monero) on Hyperliquid in batches: • $8.12M (4,484 ETH) 0xb3fffca23d4444eE73349825ACD84f7b5020e387 • $286k (558.9 XMR1) 0x5C239E7607975be5Cf44EC71d2cF1c66d878F746 • $285k (556.7 XMR1) 0xd8427872a4e9ddf00ee07f02c644447aa6b99926 • $284k (556.2 XMR1) 0xd1fd67c883466947e1f7dbf06f284cb2785b8c77 • $284k (555.1 XMR1) 0x8b3a5786d4503faeffa78e30c31a57bfda93b121 • $283k (553.7 XMR1) 0x26f3cc7d0c4fa5566f33cdbf8569b96f11cfc74e • $282k (551.8 XMR1) 0x63d09D9bD23C3Ed507771DB8Bdd65bF557fe968C • $290k (160 ETH) 0xb57c2a0a4b20d7ec73395dc23fe182e9e6830ab1 • $290k (160 ETH) 0xed762776faa72631083f02b0dc91593426634c14 The attacker deposited $20k into Lighter and withdrew $10.39M about 36 minutes later. Lighter released a statement and has paused withdrawals. Sharing this to help them act quickly Bubblemaps
- Lighter (LIT) Caution Notice Upbit
- THE BLOCK: Lighter is actively investigating a security incident that it said appeared to involve a single compromised external party. Lighter has temporarily suspended all withdrawals and pool creation as a precaution while it assesses the impact. $LIT The Block
- Lighter Suspected of User Account Drains; Temporarily Suspends Withdrawals and Liquidity Pool Creation Lighter said it is investigating a suspected security incident involving the compromise of a single external party and has temporarily suspended all withdrawals and liquidity pool creation. Blockchain analyst MLM reported that an address withdrew $10.39 million in USDC from Lighter and swapped it for approximately 5,750 ETH through CoW Protocol. Analyst 0xTria cited Korean community analysis suggesting leaked API keys belonging to two market makers may have enabled the transfers, rather than a protocol vulnerability. The two accounts reportedly involved approximately $15.48 million in total, while LIT briefly fell more than 17%. Wu Blockchain
- [Deposit/Withdrawal] Notice on temporary suspension of Lighter (LIT) deposits and withdrawals Bithumb
- Notice of Temporary Suspension of Lighter (LIT) Deposits and Withdrawals Upbit
- Suspected Drain of User Accounts on Lighter, Protocol Exploit Unconfirmed Lighter is suspected of suffering a security incident involving approximately $15.48 million across two market maker accounts. Blockchain analyst MLM reported that an address withdrew $10.39 million in USDC from Lighter and swapped it for approximately 5,750 ETH through CoW Protocol. Analyst 0xTria cited Korean community analysis suggesting leaked API keys, rather than a protocol vulnerability, may have enabled the transfers by exploiting an account-transfer mechanism that requires no additional signature. The incident has not been officially confirmed, while LIT briefly fell more than 17%. Wu Blockchain
Loading the $LIT page…