ME News reports that on April 1 (UTC+8), BlockSec detected a suspicious exploit targeting an unknown contract on BSC, potentially involving the LML/USDT staking protocol, resulting in approximately $950,000 in losses. Although the affected contract is not open-source, analysis suggests it may have a pricing design flaw: claimed rewards appear to be calculated based on TWAP/snapshot prices, while the attacker was able to sell the reward tokens at manipulated spot prices, profiting through price manipulation and reverse swaps. The attacker first inflated the LML price within the pool through a series of transactions, including paths that set the recipient address to address(0). Subsequently, they initiated a reward claim using previously deposited funds from controlled addresses, thereby qualifying for direct reward claims during the attack. (Source: Foresight News)
BSC Chain LML/USDT Staking Protocol Suffers Price Manipulation Attack, Losses Reach $950,000
KuCoinFlashShare






On-chain analysis reveals a price manipulation attack on a BSC chain LML/USDT staking protocol on April 1, 2026 (UTC+8). BlockSec reported a $950,000 loss after attackers exploited a pricing vulnerability. On-chain data shows the attackers inflated the LML price through abnormal transactions, including those sent to address(0), and then used controlled addresses to claim rewards during the attack window.
Source:Show original
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.