Чеклист пользователя
Приоритеты доказательств
Capture URLs, transaction hashes, wallet addresses, payment requests, support chats and identity claims before anything changes.
URLs
Wallets
Tx hashes
Screenshots
Timeline
Чеклист доказательств
| Evidence type | What to save |
|---|---|
| Website and app | Full URL, login URL, app store link, domain spelling, screenshots of homepage and payment page. |
| Contacts | Telegram/WhatsApp handles, email addresses, phone numbers, social profiles and display-name changes. |
| Платежный след | Адреса кошельков, хеши транзакций, квитанции вывода с биржи, время платежей и запрошенные суммы. |
| Promises and pressure | Guaranteed returns, unlock tax, liquidity fee, recovery promise, deadline pressure and threat wording. |
| Account state | Dashboard balance screenshots, withdrawal block messages, KYC requests and support ticket numbers. |
| Your actions | When you joined, what you clicked, what wallet you connected, which approvals you signed and what you revoked. |
Шаблон описания инцидента
| Field | What to write |
|---|---|
| Incident type | Fake exchange, recovery scam, wallet drainer, clone domain, fake support, romance/investment scam or unknown. |
| Main service/domain/contact | Exact website, app name, handle, email, phone number and the route that led you there. |
| Money movement | Coin, chain, amount, transaction hash, destination address, exchange used and date/time. |
| Trigger event | Failed withdrawal, tax demand, account freeze, recovery offer, malicious approval, seed phrase request or support-channel switch. |
| Current risk | Remaining funds at risk, wallet still connected, approvals still открыть, documents shared or ongoing pressure messages. |
| Reports already filed | IC3, FTC, Chainabuse, exchange support, wallet provider, local police or regulator references. |
Доказательства по типу скама
| Scenario | Most useful evidence | Likely next route |
|---|---|---|
| Fake exchange / withdrawal tax | Dashboard URL, withdrawal error, tax/unlock message, support chat, deposit tx hash, destination wallet, account screenshots. | Проверка предупреждений, exchange report, IC3/FTC or local regulator. |
| Recovery scam | Краткое описание исходной потери, обещание восстановления, запрос fee, заявленная организация/компания, адрес кошелька, доказательство контакта и запрос оплаты. | FTC/CFTC guidance, IC3, warning checker and evidence kit. |
| Wallet drainer | Подозрительный URL, хеш подписанной транзакции/approval, контракт токена, адрес spender, скриншоты popup кошелька и результат проверки approvals. | Transaction lookup, Revoke.cash profile, wallet provider report. |
| Домен-клон / fake support | Точный домен, скопированная брендовая страница, виджет чата, контакт Telegram/WhatsApp/email, запрошенное действие и скриншоты. | Binance Verify when relevant, service profile, Chainabuse and warning checker. |
| Romance or investment pitch | Профиль первого контакта, инвестиционное обещание, скрипты, последовательность платежей, давление в сообщениях и все адреса кошельков. | IC3/FTC, local cybercrime report, warning checker. |
| Fake token / airdrop | Адрес контракта, страница токена, URL claim, prompt кошелька, пост/реклама в соцсетях и ссылки explorers. | Transaction lookup, wallet-drainer wiki, Chainabuse. |
Шаблон таймлайна
- First contact: where the conversation began and which profile or ad led to the service.
- Registration: domain, app, account ID and the first screenshot of the dashboard.
- Deposit: coin, chain, amount, wallet address, exchange receipt and transaction hash.
- Problem: failed withdrawal, frozen account, tax demand, recovery offer or support-channel switch.
- Current state: last message, last domain seen, remaining funds at risk and what has already been reported.
Перед отправкой отчета
- Put the incident summary at the top so a reviewer can understand the case in one minute.
- Attach raw links and screenshots, but keep private keys, seed phrases, passwords and full ID documents out of public reports.
- Use exact timestamps with timezone when possible. If not, write the local time and country.
- Keep wallet addresses and transaction hashes in plain text so exchanges and investigators can copy them.
- Separate facts from assumptions: "I sent 0.5 ETH to this address" is stronger than "they stole everything."
- Save a local copy before submitting because some portals do not show the full report after it is sent.
Куда сообщить
| Goal | Куда сообщить | Attach |
|---|---|---|
| Cybercrime report | FBI IC3 or the relevant national cybercrime portal | Transaction hashes, wallet addresses, website URLs, communication records. |
| Consumer/regulator warning | FTC, CFTC, FCA, SEC/Investor.gov or local financial regulator | Текст предложения, заявления компании, совпадения в warning lists и требования оплаты. |
| Exchange report | The exchange used to send funds | Квитанция вывода, хеш транзакции, адрес назначения и описание скама. |
| Wallet or abuse platform | Wallet provider support, Chainabuse or chain-specific abuse channels | Wallet addresses, chain, transaction hash and screenshots. |
| Public review or CryptoRescue tip | Only after saving evidence and avoiding doxxing/private data | Очищенный домен, паттерн, даты и ссылки на источники. |
Чего не делать
- Не платите recovery fee, сбор валидатора, gas top-up, налог на разблокировку или депозит следователю.
- 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.
Журнал обновлений
- 3 июн 2026Опубликовано с отслеживанием источников и контекстом безопасности для читателя.
- ИсправленияЕсли источник изменится или утверждение потребует уточнения, страница может быть обновлена редакцией.