Practical route: project contacts, our contacts, what to attach.
Report without feeding the attacker
Screenshot, clone username, link — to platform support/mods. Don’t attach seeds, full backups, passwords. Don’t publish a “how the hack worked” guide useful to copycats.
Block the clone. Warn close contacts briefly. You can notify a catalog about a dead/malicious storefront via its report channel — without key secrets.
---
A decision glossary for “report”
When chat says “report”, translate into actions: what to open, what to verify, what not to sign. “Where to write if you find a scam or catalog bug” is a headline; decisions live in the preview and wallet choice.
Frame: Practical route: project contacts, our contacts, what to attach. Anything demanding a seed, prepaid “access”, or an “activation transfer” falls out of frame automatically.
Anchor words: pin, favorites, dust, spender, limit. If the talk has only urgency — you’re in someone else’s script.
Safety contour before any “report” click
Device updated from normal sources. Wallet client too. Seed not in chats. Experimental balance separated. Not “paranoia before report” — a table you can work on.
Public Wi‑Fi, foreign PC, screen share — bad background. Move large size to another moment. The topic can wait.
Entry checks: lookalikes next to “report”
Two candidates beat one. Pin reference beside a feed link. Character by character. Aloud. Icons and “online” don’t count. One letter is enough error cost.
After verify — favorites. Don’t return to global brand search. Clones queue there specifically for “report”.
Action, preview, aftercare
An action on “report” without a readable preview is a lottery. State the operation type. Shrink size until it’s boringly clear. Dust. History. Balance.
After: revoke extra approve, delete temporary bookmarks, ensure you didn’t leave a session on a foreign device. The catalog may have helped find the entry; cleanup is yours.
Long distance: “report” without season drama
Seasons come and go. Habits stay. Weekly short review: favorites, junk tokens, updates. Once a season — a careful look at seed backup without publishing words.
If “Where to write if you find a scam or catalog bug” feels long — that’s intentional. Short taps already belong to attackers. Your edge is a slow Confirm and a calm refusal.
A 48-hour mini-diary after “report”
Hour 0: action done or canceled. Hour 1: history and balance. Evening: favorites and approvals. Tomorrow: don’t chase FOMO with a new amount “to break even”. At 48 hours: note what worked in your verification process.
The diary is boring — therefore useful. Seasons teach impulse; diaries teach repeatable safe steps.
How “report” links to other ecosystem habits
Even when today’s focus is “Where to write if you find a scam or catalog bug”, seed hygiene, username anti-phishing, wallet separation, and exchange memo care still matter. You don’t need to learn everything at once. You need to not break the base while handling the special case “report”.
Leave TON Web Search as an entry map. Maps can be closed. Keys and limits cannot.
“report” practice: three kill-switches
First kill-switch — source. If the entry for “Where to write if you find a scam or catalog bug” didn’t come from the pin or your favorites, you’re already in a higher-risk zone. Second — wallet: experimental for new, main for known and verified. Third — size: dust before volume. Three switches close most everyday failure stories around “report”.
Reminder frame: Practical route: project contacts, our contacts, what to attach. Don’t turn the frame into a “hurry” slogan. Refusing also counts as being on time.