Fact-check findings
What an automated fact-checker found when it re-read DCENT Wallet against the sources the page cites. Only the most recent review is shown.
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.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #7[unverifiable][awaiting moderator]in the timeline
“IoTrust raises approximately $6 million USD in a funding round from L&S Venture Capital, KDB Capital, K-Run Ventures, SL Investment, and KB Investment.”
reviewerCompany funding: raised about 6.5 billion KRW (roughly $6M) from L&S Venture Capital, KDB Capital, K-Run Ventures, SL Investment and KB Investment; earlier 2.5 billion KRW.Medium returned 403 and no archive exists. The date 2021-01-01 is placeholder-precision and could not be checked. - #8[unverifiable][awaiting moderator]in section: Company Background — IoTrust Co., Ltd.
“The company has reported a user base of more than 700,000 worldwide as of 2026”
reviewerCompany background: founded January 2017 by Sangsu Baek and Minho Yoo; user base above 700,000 as of 2026; partners Klaytn and Flare.Cited background sources were blocked, so founding date, executives and user count were not checked.
stale
2 claimsThe claim was accurate when written but events since have overtaken it.
- #2[stale][awaiting moderator]in the summary
“As of the date of this investigation, no root cause, loss total, or number of affected users has been disclosed, and the incident remains active.”
reviewerAs of the investigation date no root cause, loss total, or number of affected users has been disclosed, and the incident remains active.Still true that no official root cause or loss total exists, but affected-version scope, a preliminary report, report counts and third-party loss estimates are now public. The statement omits these.Proposed correction (not yet applied)As of September 23, 2026, IoTrust had not published a loss total or confirmed a root cause, and had withheld technical details of the vulnerability. Third-party trackers (XRPL.to) reported about 2.0 million XRP leaving 1,552 wallets, and IoTrust had received 110 user reports by September 18. IoTrust stated that App Wallet versions earlier than 8.1.0 are in scope. The incident remains active. - #3[stale][awaiting moderator]in section: Disclosure Transparency and Information Gaps
“No on-chain analysis from third-party security researchers has been published as of this scan.”
reviewerDCENT App Wallet scope: no on-chain analysis by third-party researchers has been published.Superseded by reporting from Sept 23, 2026.Proposed correction (not yet applied)On-chain analyses by third parties (XRPL.to and XRPL Intel) have since been published, tracking about 2.0 million XRP leaving 1,552 wallets on September 15 UTC and a wider potential victim pool of 6,160 addresses and about 9.3 million XRP; neither establishes how the keys were obtained.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Disclosure Transparency and Information Gaps
“approximately $100 million was reported stolen across more than 5,500 accounts”
reviewerAtomic Wallet breach of June 2023: approximately $100 million stolen across more than 5,500 accounts.The cited Halborn source says over $35M and gives no account count. Higher estimates (about $100M) exist elsewhere, but the cited source does not support the figure, so the correction is optional and the citation should be changed. - #5[partially supported][awaiting moderator]in section: Disclosure Transparency and Information Gaps
“approximately $9.9 million was stolen via a trojanized APK”
reviewerBitKeep December 2022: approximately $9.9 million stolen via trojanized APK.Vector confirmed. The cited source says more than $8M, and I did not check the $9.9M figure against another source. - #9[partially supported][awaiting moderator]in section: Secondary Risk — Phishing and Social Engineering
“suggesting DCENT's App Wallet user base includes a material portion of XRP holders who may be targeted by XRP-themed phishing follow-ons”
reviewerXRP community was alerted, suggesting a material portion of App Wallet users hold XRP.The inference is speculative as written, but it is supported by later reporting that the losses were largely XRP. The edit is optional.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On September 16, 2026, IoTrust publicly disclosed that it detected abnormal asset transfers on its DCENT App Wallet and launched an emergency investigation”
reviewerOn September 16, 2026 IoTrust publicly disclosed abnormal asset transfers on the DCENT App Wallet and launched an emergency investigation.Date and announcement confirmed. The Crypto Times URL returned 403, but two other cited sources agree. - #6[confirmed][no action needed]in section: Active Security Incident — September 2026
“IoTrust stated that initial findings suggest the issue is limited to the App Wallet and that DCENT hardware wallets (the Biometric Wallet and Card Wallet) are not confirmed to be affected.”
reviewerHardware wallets not confirmed affected; shared mnemonic users are at risk.Consistent with sources. The article text says nothing specific about the Biometric or Card model names.