Lighter incident involves API key leak, not a hack, affecting over $15M

iconKuCoinFlash
Share
AI summary iconSummary
Lighter faced a $15.5M incident tied to API key leaks, not a hack, according to Blockbeats. On November 16, @0xTria revealed that attackers drained funds from two major market maker accounts. The attacker closed positions, created a 0% fee pool with $10K, and gradually transferred $1M blocks of USDC into the pool. Account #714710 lost $10.39M, and account #714723 lost $5.09M. Traders are advised to monitor altcoins amid rising volatility in the Fear & Greed Index.

BlockBeats news, on November 16, Predicts.guru founder @0xTria shared a research finding by a Korean trader stating that Lighter is not experiencing a protocol-level hack, but rather an API key leak from two large market maker accounts.


Analysis reveals that the attacker closed the victim’s position, created a public pool with 0% fees from the victim’s account, deposited approximately $10,000 to secure 99.99% of the shares, and then batch-transferred the victim’s USDC into the pool in $1 million increments before redeeming it. Although API keys on Lighter cannot send funds to others, transfers between accounts on the same L1 address require no signature, and the pool created by the victim was treated as their own account.


The total affected funds amount to approximately $15.5 million: $10.39 million from #714710 and $5.09 million from #714723.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.