← DxSalereviewed 2026-09-09 · 22 claims checked
Fact-check findings
What an automated fact-checker found when it re-read DxSale against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
2 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #3[disputed][awaiting moderator]in section: May 2026 Exploit: Legacy Locker Drain
“The exploit was first flagged publicly by blockchain security firm PeckShield.”
reviewerThe exploit was first flagged publicly by blockchain security firm PeckShield.Attribution of who flagged the exploit first is contested. rekt.news, a specialist DeFi-hack postmortem outlet with a detailed timeline, credits Tahax with the first public alert; two general crypto-news outlets credit PeckShield. The page picked one side of a live dispute without noting it.Proposed correction (not yet applied)The exploit was first flagged publicly by on-chain analyst Tahax, with blockchain security firm PeckShield separately publishing its own alert shortly after. - #21[disputed][awaiting moderator]in section: Broader DeFi Context
“Year-to-date crypto hack losses as of late May 2026 were reported to have exceeded $17 billion.”
reviewerYear-to-date crypto hack losses as of late May 2026 were reported to have exceeded $17 billion.Neither of the two sources cited for this section actually states a $17 billion year-to-date figure; both discussed figures around $52M (May) and $634M (April) only. Multiple independent DefiLlama-sourced reports put losses for the first five months of 2026 at roughly $840 million, and full H1 2026 at about $1.32 billion -- roughly 20x lower than the page's $17 billion claim. This appears to be a hallucinated or miscited figure, possibly conflated with a $17B 2025 crypto scam/fraud total reported elsewhere (a different, non-hack category).Proposed correction (not yet applied)Year-to-date crypto hack losses as of late May 2026 were reported to have exceeded $840 million.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #18[unverifiable][awaiting moderator]in section: Platform History and Rebranding
“The SALE governance token was launched on Ethereum in August 2020 and reached an all-time high price of approximately $2.08 on September 3, 2021.”
reviewerThe SALE governance token launched on Ethereum in August 2020 and reached an all-time high price of approximately $2.08 on September 3, 2021.Could not confirm the specific $2.08/Sept 3, 2021 figure against the cited CoinMarketCap source directly, and other price trackers disagree wildly with each other ($3.57, $71,496.60) and with the page. Low-cap/low-liquidity token ATH data is notoriously inconsistent across trackers; not enough to call this disputed with a specific correction, but it cannot be confirmed either.
stale
2 claimsThe claim was accurate when written but events since have overtaken it.
- #8[stale][awaiting moderator]in section: May 2026 Exploit: Legacy Locker Drain
“The DxSale team issued no public statement across any official communication channels following the incident.”
reviewerThe DxSale team issued no public statement across any official communication channels following the incident.Was accurate at the moment the May 29 news wave (this page's cited sources) went to press, but DxSale did in fact respond within roughly 24-48 hours. The page states this as an ongoing/current fact rather than a snapshot of the first day, which is now stale.Proposed correction (not yet applied)The DxSale team did not comment for roughly the first 24 hours, then issued statements on May 29 and May 30, 2026 asserting the exploit was isolated to its legacy v1 lock contract and that v2 and later lockers were unaffected and Certik-audited. - #22[stale][awaiting moderator]in the timeline
“PeckShield and Coinsult published on-chain analysis of the exploit; multiple crypto news outlets reported the incident; DxSale team issued no public statement.”
reviewerFollowing the drain (2026-05-29), PeckShield and Coinsult published on-chain analysis of the exploit; multiple crypto news outlets reported the incident; DxSale team issued no public statement.Same underlying defect as the sections[0] finding: accurate for the earliest hours of coverage, but DxSale did respond within roughly 1-2 days, which the timeline entry does not reflect.Proposed correction (not yet applied)PeckShield and Coinsult published on-chain analysis of the exploit; multiple crypto news outlets reported the incident; DxSale did not comment within the first 24 hours after the exploit.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #5[partially supported][awaiting moderator]in section: May 2026 Exploit: Legacy Locker Drain
“Additional BNB totaling approximately 3,400 BNB (roughly $1.2 million) was also sent to Binance deposit addresses, with remaining funds routed through multichain mixers to further obscure the trail.”
reviewerAdditional BNB totaling approximately 3,400 BNB (~$1.2 million) was also sent to Binance deposit addresses, separate from the 2,958 BNB tranche.Both BNB figures appear in reporting, but the implied BNB price is inconsistent between them (~$632/BNB for the 2,958 figure vs. ~$353/BNB for the 3,400 figure), and no source clarifies whether the page's framing of these as additive tranches is correct. The page presents them as cleanly additive without flagging this discrepancy.
confirmed
16 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: May 2026 Exploit: Legacy Locker Drain
“On May 28, 2026, an attacker exploited DxSale's legacy BNB Chain liquidity locker contracts, draining approximately $7.3 million from over 1,400 LP positions that had been locked since as far back as 2021.”
reviewerOn May 28, 2026, an attacker exploited DxSale's legacy BNB Chain liquidity locker contracts, draining approximately $7.3 million from over 1,400 LP positions locked since as far back as 2021.Core facts of the exploit (date, amount, position count, legacy 2021-era contracts) are consistently corroborated across independent outlets including a specialist DeFi-hack postmortem site (rekt.news). - #2[confirmed][no action needed]in section: May 2026 Exploit: Legacy Locker Drain
“The primary attacker-controlled wallet identified by investigators was 0xC4574DDEF299e7E563971e200433e592EeaaFA69.”
reviewerThe primary attacker-controlled wallet was 0xC4574DDEF299e7E563971e200433e592EeaaFA69.Address is consistent across every independent source checked. - #4[confirmed][no action needed]in section: May 2026 Exploit: Legacy Locker Drain
“Approximately 2,958 BNB (valued at roughly $1.87 million at time of exploit) was routed through two primary wallets before being deposited across multiple Binance addresses.”
reviewerApproximately 2,958 BNB (~$1.87 million) was routed through two primary wallets before being deposited across multiple Binance addresses.Matches cited reporting closely, including the two-wallet detail. - #6[confirmed][no action needed]in section: May 2026 Exploit: Legacy Locker Drain
“Approximately 20 hours before the main drain, the attacker's wallet received 104 BNB from Bybit, a pattern consistent with pre-exploit staging.”
reviewerApproximately 20 hours before the main drain, the attacker's wallet received 104 BNB from Bybit.Matches cited source exactly. - #7[confirmed][no action needed]in section: May 2026 Exploit: Legacy Locker Drain
“Among the notably affected pools were liquidity positions associated with the original SafeMoon project, with analysts reporting approximately $1.74 million in SafeMoon LP value withdrawn.”
reviewerSafeMoon LP positions were affected, with approximately $1.74 million in SafeMoon LP value withdrawn.Figure independently confirmed. - #9[confirmed][no action needed]in section: Technical Attack Mechanism
“Coinsult's assessment was: 'A privileged setFee plus a backdated lock turned locked deposits into a withdrawable balance.'”
reviewerWeb3 auditing firm Coinsult traced the drain to a privileged setFee call (fee reduced to 1 wei) plus a backdated lock-expiration timestamp of 68 seconds after the Unix epoch, quoted as: 'A privileged setFee plus a backdated lock turned locked deposits into a withdrawable balance.'Substantively accurate; the page drops the inner single quotes Coinsult placed around the word 'locked' but the wording and meaning are otherwise verbatim. - #10[confirmed][no action needed]in section: Technical Attack Mechanism
“A separate 2023 vulnerability disclosure by security firm Decurity had previously highlighted architectural risks in DxSale's locking mechanism that enabled unauthorized unlocking of LP tokens, suggesting the underlying class of vulnerability was known to the security research community prior to this exploit.”
reviewerA separate 2023 vulnerability disclosure by security firm Decurity had previously highlighted architectural risks in DxSale's locking mechanism enabling unauthorized unlocking of LP tokens.The prior-disclosure claim is confirmed by Decurity's own writeup, which independently corroborates the 'architecturally analogous' framing the page uses. - #11[confirmed][no action needed]in section: Alleged Insider Involvement
“Approximately 269 days before the May 28, 2026 drain — placing the initial event around early August 2025 — ownership of the legacy locker contract was silently transferred from the DxSale deployer wallet to a new wallet without any public announcement or migration notice to affected users or token teams.”
reviewerOwnership of the legacy locker contract was silently transferred approximately 269 days before the drain, then passed through approximately 80 intermediate wallets before reaching the attacker address.Independently corroborated by a specialist postmortem outlet. - #12[confirmed][no action needed]in section: Alleged Insider Involvement
“Eyeonchain investigators concluded the exploit involved 'someone with insider-level access,' possibly a former team member.”
reviewerOn-chain investigators, including analyst Tahax and the Eyeonchain analytics team, identified indicators consistent with insider involvement, with Eyeonchain concluding the exploit involved 'someone with insider-level access,' possibly a former team member.Quote matches cited source. - #13[confirmed][no action needed]in section: Alleged Insider Involvement
“Blockchain analysis identified a historical connection between the attacker's address and developer wallets, with the address allegedly having previously been used to channel funds to the main DxSale contract.”
reviewerBlockchain analysis identified a historical connection between the attacker's address and developer wallets, with the address allegedly having previously been used to channel funds to the main DxSale contract.Matches cited source, appropriately hedged with 'allegedly' by the page. - #14[confirmed][no action needed]in section: Alleged Insider Involvement
“Separately, screenshots circulating in the community showed that in August 2025, an individual allegedly advertised a service on DxSale's Telegram channel claiming insider team access and offering to unlock legacy LP positions from projects launched before late 2021 in exchange for a 20% fee — a service that, in retrospect, may have been an early phase of the eventual drain operation.”
reviewerIn August 2025, an individual allegedly advertised a service on DxSale's Telegram channel claiming insider team access and offering to unlock legacy LP positions from pre-2021 projects for a 20% fee.Matches cited source closely, including the 20% figure. - #15[confirmed][no action needed]in section: Team Anonymity and Disclosure
“DxSale's official documentation lists three founders — identified only by the single names Dennis, Hash, and Raphael — reachable via @dxsale.network email addresses.”
reviewerDxSale's official documentation lists three founders — Dennis, Hash, and Raphael — reachable via @dxsale.network email addresses, with no surnames or independently verifiable identities published; the documentation warns unsolicited DMs are likely from scammers.Directly confirmed against the primary source; the paraphrased scam warning in the page also matches the docs' actual wording in substance. - #16[confirmed][no action needed]in section: Team Anonymity and Disclosure
“The original team was described as comprising five members at launch (four engineers and one product manager) with claimed prior experience at S&P 500 companies in North America, but this has not been independently verified.”
reviewerThe original team was described as comprising five members at launch (four engineers and one product manager) with claimed prior experience at S&P 500 companies in North America.Cited source is a self-reported AMA recap (not independently audited), and the page correctly flags this as unverified team-provided information. - #17[confirmed][no action needed]in section: Platform History and Rebranding
“DxSale launched in August 2020 on the Ethereum network, positioning itself as the first end-to-end autonomous launchpad combining token presales with on-chain liquidity locking in a single flow.”
reviewerDxSale launched in August 2020 on Ethereum; expanded to BNB Chain in January 2021, Polygon in February 2021, and Avalanche/Fantom/Harmony/OKX Chain/xDai/HECO in May 2021; Version 2 launched March 2021, Version 3 in September 2021; Version 4 released and rebranded to DX App in January 2023.All dates and version milestones confirmed directly against the official docs page cited by the section. - #19[confirmed][no action needed]in section: Broader DeFi Context
“The DxSale exploit contributed to an estimated $52 million in total DeFi losses recorded for May 2026, according to data cited by multiple outlets.”
reviewerThe DxSale exploit contributed to an estimated $52 million in total DeFi losses recorded for May 2026.Confirmed by an independent outlet citing the same DefiLlama figure. - #20[confirmed][no action needed]in section: Broader DeFi Context
“This figure contrasts with April 2026, which saw approximately $634 million in crypto hack losses — cited as the highest monthly total in over a year per DefiLlama data.”
reviewerApril 2026 saw approximately $634 million in crypto hack losses, the highest monthly total in over a year per DefiLlama data.Confirmed against the cited source verbatim.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.