45,850 reported operators on file$42.1M+ partner-reported funds returnedVetted, masked recovery-partner networkExplore the Claim Journeys →
Skip to content

Victims have reported GKJ159 through Google Search complaints. The case is classified as a fake forex broker and was opened on the SARFund registry once corroboration thresholds were met.

Across the verified submissions, three red flags repeat: the broker operated through impersonated KYC documents, used unregulated celebrity endorsements, and required upfront deposits routed through obscure custodial wallets. None of these are unique to GKJ159 — they are the structural fingerprint of this scam typology.

Channels through which GKJ159 has been reported include Google Search complaints, Telegram channel testimonials, and TrustPilot complaints. SARFund cross-references new submissions against existing reports before adding evidence to the case file.

What evidence helps most

Transaction hashes (the on-chain proof of your deposit), screenshots of the broker dashboard, KYC documents you submitted, and full conversation history with any account manager. These four pieces let the partner build a defensible chain of custody.

Redaction policy

SARFund publishes the existence and status of each case but withholds operationally sensitive details. The recovery partner identity, exact victim count, recovered amount, and tagged wallet addresses are released only to verified claimants once the claim form is submitted and matched.

If you deposited with GKJ159, your case may already be on file. Submit your evidence to be matched and connected privately with the recovery team handling this matter.

SARFund does not guarantee recovery. All recovery actions are conducted by independent partners. Submission is free. SARFund is an intermediary case registry, not a recovery firm.

In association withAFI Anti-Fraud InitiativeNCFA National Cyber Forensic Association
🛡 Not sure about a broker? Check it against the SARFUND registry of 45,850+ reported scam brokers before you deposit.Check the registryFile a claim