← UPCXreviewed 2026-11-02 · 12 claims checked
Fact-check findings
What an automated fact-checker found when it re-read UPCX 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.
- #2[disputed][awaiting moderator]in the summary
“Despite listing on a Japanese FSA-licensed exchange just 11 days prior, no recovery of stolen funds was reported.”
reviewerBitTrade listing was 11 days before the April 1 exploitThe page's own dates (March 27 listing, April 1 exploit) give 5 days. The announcement date (March 17) is 15 days prior, so 11 matches neither.Proposed correction (not yet applied)Despite listing on a Japanese FSA-licensed exchange just 5 days prior, no recovery of stolen funds was reported. - #3[disputed][awaiting moderator]in section: Japan FSA Compliance and Pre-Hack Timeline
“The listing occurred on March 27, 2025 — just 11 days before the April 1 exploit.”
reviewerListing occurred March 27, 2025, 11 days before the exploitDate correct, day-count arithmetic wrong.Proposed correction (not yet applied)The listing occurred on March 27, 2025 — just 5 days before the April 1 exploit.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #5[unverifiable][awaiting moderator]in section: Root Cause — Missing Multisig Controls
“Smart contract audits by CertiK and Cyberscope did not identify or flag this key management risk.”
reviewerCertiK and Cyberscope audits did not flag the key management riskCould not confirm pre-hack audits by either firm or what they covered. The CertiK page dates appear to postdate the hack. - #8[unverifiable][awaiting moderator]in section: Post-Exploit Status and Recovery
“No public bounty offer, recovery negotiation, or law enforcement coordination was announced.”
reviewerNo bounty, negotiation or law enforcement coordination was announcedA negative claim; searches found no announcement either way, and no coverage dated after April 2025 on the funds. - #9[unverifiable][awaiting moderator]in section: ZachXBT Flag and Risk Assessment
“On-chain investigator ZachXBT has flagged UPCX.”
reviewerZachXBT has flagged UPCXSearch found no link between ZachXBT and UPCX, and neither cited source mentions him. Cyvers was the detector. - #11[unverifiable][awaiting moderator]in section: Team and Background
“Key executives include Yutaka Imaizumi (CEO), Joerg Alexander (CTO), and Dr. Jason Nye (CSO).”
reviewerTeam: Yutaka Imaizumi (CEO), Joerg Alexander (CTO), Dr. Jason Nye (CSO), backgrounds verifiableThe only cited source blocked the fetch; not scored.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Root Cause — Missing Multisig Controls
“The attack was enabled entirely by the absence of multisig or MPC controls on the most privileged protocol functions.”
reviewerThe attack was enabled entirely by missing multisig/MPC controlsInference, not confirmed fact; 'entirely' overstates Halborn's hedged analysis.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“UPCX is a blockchain payment protocol that suffered a $70 million exploit on April 1, 2025, when an attacker compromised an administrative private key and used it to push a malicious smart contract upgrade, draining 18.4 million UPC tokens from management accounts.”
reviewerUPCX suffered a roughly $70M exploit on April 1, 2025 involving 18.4M UPC tokensCore incident facts match Halborn and multiple outlets. Halborn hedges the key compromise as 'likely', which the page states flatly. - #6[confirmed][no action needed]in section: April 2025 Exploit — $70M Private Key Compromise
“The exploit was first detected by on-chain security firm Cyvers. UPCX immediately halted transactions and launched an investigation.”
reviewerExploit was first detected by Cyvers; UPCX halted transactionsSupported. 'First' and 'immediately' are not explicitly stated. - #7[confirmed][no action needed]in section: Post-Exploit Status and Recovery
“the stolen tokens remained in a single Ethereum wallet unmoved at the time of initial detection.”
reviewerStolen tokens remained in a single wallet at initial detectionMatches contemporaneous Cyvers reporting. - #10[confirmed][no action needed]in section: Protocol Overview
“UPCX listed on BitTrade, a Japanese FSA-licensed exchange, on March 27, 2025, signaling regulatory engagement in Japan.”
reviewerBitTrade listing went live March 27, 2025Date confirmed by a syndicated press release and BitTrade notice. - #12[confirmed][no action needed]in section: Post-Exploit Status and Recovery
“By July 2025, a press release reported staking activity surpassing 975,000 tokens, suggesting partial resumption of operations”
reviewerJuly 2025 press release reported staking above 975,000 tokensRelease exists and is dated July 15, 2025. It is a project-issued promotional release.
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.