User checklist

Evidence priorities

Capture URLs, transaction hashes, wallet addresses, payment requests, support chats and identity claims before anything changes.

URLs Wallets Tx hashes Screenshots Timeline

Evidence checklist

Evidence typeWhat to save
Website and appFull URL, login URL, app store link, domain spelling, screenshots of homepage and payment page.
ContactsTelegram/WhatsApp handles, email addresses, phone numbers, social profiles and display-name changes.
Payment trailWallet addresses, transaction hashes, exchange withdrawal receipts, payment timestamps and requested amounts.
Promises and pressureGuaranteed returns, unlock tax, liquidity fee, recovery promise, deadline pressure and threat wording.
Account stateDashboard balance screenshots, withdrawal block messages, KYC requests and support ticket numbers.
Your actionsWhen you joined, what you clicked, what wallet you connected, which approvals you signed and what you revoked.

Incident summary template

FieldWhat to write
Incident typeFake exchange, recovery scam, wallet drainer, clone domain, fake support, romance/investment scam or unknown.
Main service/domain/contactExact website, app name, handle, email, phone number and the route that led you there.
Money movementCoin, chain, amount, transaction hash, destination address, exchange used and date/time.
Trigger eventFailed withdrawal, tax demand, account freeze, recovery offer, malicious approval, seed phrase request or support-channel switch.
Current riskRemaining funds at risk, wallet still connected, approvals still open, documents shared or ongoing pressure messages.
Reports already filedIC3, FTC, Chainabuse, exchange support, wallet provider, local police or regulator references.

Evidence by scam type

ScenarioMost useful evidenceLikely next route
Fake exchange / withdrawal taxDashboard URL, withdrawal error, tax/unlock message, support chat, deposit tx hash, destination wallet, account screenshots.Warning checker, exchange report, IC3/FTC or local regulator.
Recovery scamOriginal loss summary, recovery promise, fee request, claimed agency/company, wallet address, proof of contact, payment demand.FTC/CFTC guidance, IC3, warning checker and evidence kit.
Wallet drainerSuspicious URL, signed transaction/approval hash, token contract, spender address, wallet popup screenshots and approval review result.Transaction lookup, Revoke.cash profile, wallet provider report.
Clone domain / fake supportExact domain, copied brand page, chat widget, Telegram/WhatsApp/email handle, requested action and screenshots.Binance Verify when relevant, service profile, Chainabuse and warning checker.
Romance or investment pitchFirst contact profile, investment promise, scripts, payment sequence, pressure language and all wallet addresses.IC3/FTC, local cybercrime report, warning checker.
Fake token / airdropContract address, token page, claim URL, wallet prompt, social post/ad and explorer links.Transaction lookup, wallet-drainer wiki, Chainabuse.

Timeline template

  1. First contact: where the conversation began and which profile or ad led to the service.
  2. Registration: domain, app, account ID and the first screenshot of the dashboard.
  3. Deposit: coin, chain, amount, wallet address, exchange receipt and transaction hash.
  4. Problem: failed withdrawal, frozen account, tax demand, recovery offer or support-channel switch.
  5. Current state: last message, last domain seen, remaining funds at risk and what has already been reported.

Before you submit a report

  1. Put the incident summary at the top so a reviewer can understand the case in one minute.
  2. Attach raw links and screenshots, but keep private keys, seed phrases, passwords and full ID documents out of public reports.
  3. Use exact timestamps with timezone when possible. If not, write the local time and country.
  4. Keep wallet addresses and transaction hashes in plain text so exchanges and investigators can copy them.
  5. Separate facts from assumptions: "I sent 0.5 ETH to this address" is stronger than "they stole everything."
  6. Save a local copy before submitting because some portals do not show the full report after it is sent.

Where to report

GoalWhere to reportAttach
Cybercrime reportFBI IC3 or the relevant national cybercrime portalTransaction hashes, wallet addresses, website URLs, communication records.
Consumer/regulator warningFTC, CFTC, FCA, SEC/Investor.gov or local financial regulatorOffer language, company claims, warning-list matches and payment demands.
Exchange reportThe exchange used to send fundsWithdrawal receipt, transaction hash, destination address and scam narrative.
Wallet or abuse platformWallet provider support, Chainabuse or chain-specific abuse channelsWallet addresses, chain, transaction hash and screenshots.
Public review or CryptoRescue tipOnly after saving evidence and avoiding doxxing/private dataSanitized domain, pattern, dates and source links.

What not to do

  • Do not pay a recovery fee, validator charge, gas top-up, unlock tax or investigator deposit.
  • Do not share seed phrases, private keys, one-time codes, ID documents or remote-access sessions with a recovery contact.
  • Do not delete chats after reporting. Export or screenshot them first.
  • Do not publish private personal data when posting a public warning.
  • Do not assume a domain is safe because the name is absent from one warning list.

Update log

  1. 3 Jun 2026Published with source tracking and reader-safety context.
  2. CorrectionsIf a source changes or a claim needs clarification, this page can be updated from the editorial desk.