Skip to main content
AVOID.NET
← DCENT App Wallet Exploit (September 2026)reviewed 2026-10-27 · 9 claims checked

Fact-check findings

What an automated fact-checker found when it re-read DCENT App Wallet Exploit (September 2026) 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 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #1[disputed][awaiting moderator]in the timeline
    “DCENT App Wallet version 8.1.0 released — later identified as the last vulnerable release prior to which the signing vulnerability was present.”
    reviewerVersion 8.1.0 was the last vulnerable releaseThe sentence is self-contradictory: 8.1.0 is the first release outside the affected range, not the last vulnerable one.
    Proposed correction (not yet applied)
    DCENT App Wallet version 8.1.0 released — later identified by DCENT as the cutoff: addresses whose signing history predates 8.1.0 are potentially affected.
  2. #4[disputed][awaiting moderator]in section: Funds Tracing and Recovery Outlook
    “(4) whether any law enforcement action has been initiated”
    reviewerLaw enforcement action is an open, unconfirmed questionThe page contradicts itself, since the response section says DCENT is working with law enforcement.
    Proposed correction (not yet applied)
    (4) the outcome of the law enforcement investigation, which DCENT says it reported to Korean authorities on September 16

unverifiable

1 claim

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

  1. #3[unverifiable][awaiting moderator]in section: DCENT and IoTrust Company Response
    “use a built-in tool labeled 'Check if action is needed' to assess individual exposure”
    reviewerA tool labeled 'Check if action is needed' existsThe incident report confirms an in-app check was released on Sept 17, but the exact label was not found.

stale

1 claim

The claim was accurate when written but events since have overtaken it.

  1. #5[stale][awaiting moderator]in the summary
    “On September 15-16, 2026, attackers exploited a signing vulnerability”
    reviewerExploit occurred on September 15-16Later reporting says the draining ran about 10 days, not 1-2. Cryptobriefing is a single tier-2 source; the incident report itself gives no date range.
    Proposed correction (not yet applied)
    Beginning September 15, 2026, attackers exploited a signing vulnerability

partially supported

4 claims

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

  1. #2[partially supported][awaiting moderator]in section: DCENT and IoTrust Company Response
    “update the DCENT app to version 10.0.0 (the patched release)”
    reviewerVersion 10.0.0 is 'the patched release'The cited incident report does not mention 10.0.0. The FAQ supports 'v10.0.0 or later' only. Updating alone does not remediate; users are told to move funds to a new wallet.
  2. #6[partially supported][awaiting moderator]in the summary
    “On-chain analysis identified approximately 6,160 XRP Ledger addresses as potential victims, with roughly 9.3 million XRP tokens stolen on that chain alone”
    reviewerAbout 9.3 million XRP stolen across about 6,160 addresses on XRPLMatches the cited article, but a later figure is higher. The page already attributes the number to the XRPL intel account.
  3. #8[partially supported][awaiting moderator]in section: Hardware Wallet Distinction
    “the exploit targeted the mobile app's key-handling code, not the hardware devices' secure element”
    reviewerThe exploit targeted the mobile app's key-handling codeThe page states a mechanism as fact that DCENT has not disclosed. The page itself says the mechanism is undisclosed in the Vulnerability Details section.
  4. #9[partially supported][awaiting moderator]in the cited sources
    “https://web.archive.org/web/20260921123021/https://en.coin-turk.com/bill-miller-iv-sees-bitcoin-market-cap-undervalued-cites-us-deficit-risk/?rbsnp=1”
    reviewerArchive URLs for several Coin Turk and U.Today sources capture the cited articlessources_used[3], [4], [9] and [10] have archive_url values pointing to unrelated articles (Bill Miller, Ethereum ETF, Near TVL, Polymarket). The archives do not preserve the cited pages. I did not find correct archive URLs, so no replacement is proposed.

confirmed

1 claim

The cited evidence supports the claim as written.

  1. #7[confirmed][no action needed]in section: Attack Methodology and Timeline
    “Between 16:29 and 18:34 UTC, a total window of approximately two hours and five minutes, 1,552 wallets were drained for a combined 2,009,321 XRP, valued at over $2.8 million at the time of the attack.”
    reviewerWave 1 and wave 2 details of the XRPL attackMatches the source on all checked figures.
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.