PeckShield: OLPC/LABUBU Pool on BNB Chain Exploited for About $1.1 Million

PeckShield: OLPC/LABUBU Pool on BNB Chain Exploited for About $1.1 Million

N
News Editor
2026-06-20 12:51:52
PeckShieldAlert said an OLPC/LABUBU pool on PancakeSwap on BNB Chain was exploited, causing a loss of about $1.1 million. The exploiter bridged the stolen funds to Ethereum, deposited 633.4 ETH into TornadoCash, and sent small amounts of BNB and ETH to a dead address.
PeckShieldAlertBNB ChainPancakeSwapOLPCLABUBUTornadoCashOn-chain SecurityExploit

Blockchain security monitoring account PeckShieldAlert reported that an OLPC/LABUBU liquidity pool on PancakeSwap on BNB Chain was exploited, resulting in a loss of approximately $1.1 million. The alert was posted on X at 12:46 on June 20, 2026. The post shown in the source recorded 7,587 views and 7 replies.

The entities named in the alert are OLPC/LABUBU, PancakeSwap, BNB Chain, Ethereum, TornadoCash, BNB and ETH. Foresight categorized the item as a homepage headline and summarized it as an attack on an OLPC liquidity pool on BSC, with about $1.1 million in assets stolen.

The exploited pool was on PancakeSwap

PeckShieldAlert stated: “An OLPC/LABUBU pool on PancakeSwap on #BNBChain has been exploited, resulting in a loss of ~$1.1M.” This sentence identifies the target of the exploit as the OLPC/LABUBU pool on PancakeSwap and gives the reported loss figure as about $1.1 million. The input does not include transaction hashes, contract addresses, the exploit method, or a technical breakdown of the vulnerability.

The headline uses the term BSC, while the source post uses BNBChain. Both references appear in the provided material in relation to the same reported incident. PancakeSwap is the trading venue named in the report, while OLPC and LABUBU are the tokens associated with the affected pool. No pool size, token price movement, or number of affected users is included in the provided information.

Stolen funds were bridged to Ethereum

According to PeckShieldAlert, the exploiter bridged the stolen funds to Ethereum. The source does not name the bridge used, the receiving address, the timing of each transfer, or the amount moved in each bridging transaction. The confirmed point from the report is that funds connected to the exploit were moved from the BNB Chain context into Ethereum.

The alert further said that the exploiter deposited 633.4 ETH into TornadoCash. TornadoCash is the only protocol specifically named in the disclosed fund-flow description. The reported action is a deposit of 633.4 ETH into TornadoCash, not any other type of transaction or conversion.

Small BNB and ETH amounts were sent to a dead address

PeckShieldAlert also said the exploiter sent 0.0221 BNB and 0.0411 ETH to a dead address. These figures are listed separately in the source post: 0.0221 BNB and 0.0411 ETH. The input does not provide the full dead address, and it does not explain why those amounts were sent there.

The disclosed fund movement therefore consists of three parts: the stolen funds were bridged to Ethereum; 633.4 ETH was deposited into TornadoCash; and 0.0221 BNB plus 0.0411 ETH were sent to a dead address. All three details come from the same PeckShieldAlert post on X.

Disclosure remains limited to the security alert

Within the information provided, there is no statement from PancakeSwap, OLPC, LABUBU or other named parties. The source material also does not include the exploiter’s identity, a confirmed exploit technique, recovery progress, or any compensation plan. The available record is limited to PeckShieldAlert’s security notification and Foresight’s headline treatment of the incident.

The confirmed facts are that an OLPC/LABUBU pool on PancakeSwap on BNB Chain was exploited, with an estimated loss of about $1.1 million; the exploiter bridged stolen funds to Ethereum; 633.4 ETH was deposited into TornadoCash; and 0.0221 BNB plus 0.0411 ETH were sent to a dead address.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
300

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.