Bitget App
Trade smarter
Buy cryptoMarketsTradeFuturesEarnSquareMore

News

Stay up to date on the latest crypto trends with our expert, in-depth coverage.

banner
Flash
14:22
Hyperliquid completes USDH-denominated market settlement on HyperCore
Hyperliquid announced that markets denominated in USDH on HyperCore have completed settlement. Users need to handle their remaining USDH assets, including converting USDH to USDC on the HyperCore spot order book and HyperEVM, withdrawing USDH from Borrow/Lend products, and repaying borrowed USDH by purchasing the USDH/USDC trading pair.
14:03
SlowMist’s Cosine Questions the LABUBU “Theft” Incident on BNB Chain: Key Parameters Appear to Have Been Abnormally Modified
According to Odaily, SlowMist founder Cosine analyzed that there are suspicious aspects to the approximately $1.1 million capital loss incident that occurred in the OLPC / LABUBU liquidity pool on BNB Chain. The theft was caused by a severe imbalance in the OLPC/LABUBU trading pair, and the reason for the imbalance was an "exploit" in OLPC that was taken advantage of. In the _update function, under certain conditions, it was possible to burn OLPC in the amount of value * decimalsValue. Normally, decimalsValue is 1, but about 46 days before the attack, the owner changed it to an extremely large value: 7326680472586200649. A few days later, the OLPC owner renounced ownership, making the owner address the zero address. Today, the attacker took advantage of this excessive decimalsValue to trigger a Pair reserve burn, allowing them to obtain a large amount of LABUBU with a small amount of OLPC. The attacker ultimately exchanged 1.115 million USDT at a low cost. The suspicious point lies in the setting of decimalsValue—why would the OLPC owner set it to such a massive value?
13:58
PancakeSwap Responds to OLPC/LABUBU Liquidity Pool Attack, Platform Contracts Have No Vulnerabilities
According to ChainCatcher, in response to rumors about an attack on the BNB Chain OLPC/LABUBU liquidity pool, PancakeSwap officially issued a statement saying that the platform is aware of the security incident. After a preliminary investigation, PancakeSwap has confirmed that there are no security vulnerabilities in its own smart contracts. The project team is still thoroughly investigating the full cause of the incident and will promptly update the public with the latest findings as more information is obtained. Meanwhile, PancakeSwap reminds users that any information related to this incident should be based solely on official announcements from PancakeSwap.
News