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

Victims have reported Zignalor through direct victim submissions through SARFund. The case is classified as a pig-butchering romance scam and was opened on the SARFund registry once corroboration thresholds were met.

The reports cluster around three operational signatures: the platform demanded “tax” or “verification” fees before withdrawal, blocked withdrawal requests, and promised guaranteed returns. SARFund treats this combination as sufficient grounds to maintain an active case file pending recovery action.

Reports have surfaced via direct victim submissions through SARFund and Reddit victim threads, with corroborating threads on Quora question threads. Victim accounts converge on identical timelines and identical withdrawal-blockade tactics.

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 Zignalor, 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