Fact-check findings

No source the reviewer could reach confirms or contradicts the claim.

1. #4[unverifiable][awaiting moderator]in section: Alleged Premeditation: the decimalsValue Parameter Change

   “Security researchers characterized the renunciation as an attempt to disguise the premeditation.”

   reviewerSecurity researchers characterized the renunciation as an attempt to disguise premeditationCryptoTimes returned 403 (blocked), but other cited sources do not attribute this view to named security researchers.
   citedwww.cryptotimes.io/2026/06/20/pancakeswa…what-went-wrong/
2. #10[unverifiable][awaiting moderator]in the timeline

   “After the decimalsValue change, the OLPC contract owner renounced ownership by transferring control to a dead address, making the parameter permanent and the contract appear decentralized and immutable.”

   reviewerTimeline dates for decimalsValue change and renunciation are '2026-05'Renunciation occurring after the change is supported by AMBCrypto, but the month 2026-05 and the dead-address detail are not established, and the cited URL lacks them. 46 days before June 20 is about May 5, so the change date is consistent.
   citedcryptonews.net/news/security/33038552/
3. #11[unverifiable][awaiting moderator]in section: Market Impact and Token Price Volatility

   “As of June 24, 2026, no regulatory body (SEC, CFTC, DOJ or an equivalent international authority) had publicly announced an investigation, charges or enforcement action related to the exploit”

   reviewerNo regulatory or law-enforcement action as of June 24, 2026A negative claim; I found no contrary reporting. The review is being done in November 2026, so the as-of date is stale by months.
   citedbitcoinworld.co.in/pancakeswap-olpc-labu…ack-1-1-million/

The cited evidence supports part of the claim but not all of it.

1. #3[partially supported][awaiting moderator]in the summary

   “a sequence security researchers and reporting outlets characterize as an alleged premeditated rug pull disguised as an external exploit”

   reviewerSecurity researchers and reporting outlets characterize the incident as an alleged premeditated rug pullSearch results show outlets and social media commentary raising suspicion, but none confirmed intent. The attribution to 'security researchers' is not clearly sourced, and the cited CryptoNews article does not frame it as a rug pull. The hedging 'alleged' helps.
   citedcryptonews.net/news/security/33038552/
2. #5[partially supported][awaiting moderator]in the timeline

   “the attacker deposited 633.4 ETH into Tornado Cash and sent 0.0221 BNB and 0.0411 ETH to dead addresses.”

   reviewerTornado Cash received 633.4 ETH after bridging to EthereumTornado deposit confirmed. Dead-address amounts appear in FX Daily Report but not in the CryptoNews source cited on this entry. One search snippet claimed no Tornado use was detected, which conflicts with the other reports.
   citedcryptonews.net/news/security/33038552/
3. #7[partially supported][awaiting moderator]in section: Security Researcher and PancakeSwap Response

   “it fell to $3.89 before spiking to $4,190 (a reported 6,839% increase) and then corrected rapidly”

   reviewerOLPC fell to $3.89, spiked to $4,190 (6,839%) then correctedFigures exist in one source only. The causal explanation (burn reduced supply causing the spike) is the page's own inference.
   citedfxdailyreport.com/pancakeswap-olpc-labub…million-exploit/

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in the summary

   “On June 20, 2026, an attacker drained approximately $1.11 million from the OLPC/LABUBU liquidity pool on PancakeSwap V2 (BNB Chain)”

   reviewerAbout $1.11M drained from OLPC/LABUBU PancakeSwap V2 pool on BNB Chain on June 20, 2026Multiple outlets agree on amount and event.
   citedwww.kucoin.com/news/flash/bnb-chain-olpc…ted-1-11m-stolen
2. #2[confirmed][no action needed]in the summary

   “About 46 days earlier, the OLPC contract owner had changed the decimalsValue parameter from 1 to an extremely large integer and then renounced ownership”

   reviewerOwner changed decimalsValue from 1 to a huge number about 46 days before the exploitChange and later renunciation supported. The exact renunciation date is not given in the sources I could read.
   citedambcrypto.com/bnblabubu-exploit-drains-1…ismatch-details/
3. #6[confirmed][no action needed]in section: Exploit Mechanism: Reserve Desynchronization

   “another puts the net gain after costs at approximately $960,000”

   reviewerNet gain reported at about $960,000 vs 1,115,903 USDTFigure appears in cited FX Daily Report; AMBCrypto does not carry it.
   citedfxdailyreport.com/pancakeswap-olpc-labub…million-exploit/
4. #8[confirmed][no action needed]in section: Regulatory and Law Enforcement Status

   “It occurred amid approximately $60.03 million in total crypto losses in June 2026, per DeFiLlama data cited in reporting, including a $32 million Humanity Protocol exploit and the drainage of 1,158 ETH from Aztec Network.”

   reviewerJune 2026 crypto losses of $60.03M including $32M Humanity Protocol and 1,158 ETH AztecMatches AMBCrypto.
   citedambcrypto.com/bnblabubu-exploit-drains-1…ismatch-details/
5. #9[confirmed][no action needed]in section: Fund Movement and Laundering via Tornado Cash

   “PancakeSwap issued a public statement: 'Our initial investigation has confirmed that there are no issues with PancakeSwap's smart contracts.'”

   reviewerPancakeSwap statement that its contracts are not affectedQuote corroborated by search results. Note the CryptoNews article, an earlier report, said PancakeSwap had not yet issued a statement.
   citeden.bloomingbit.io/feed/news/114666