A useful scam or security report helps readers verify the risk and protect themselves without exposing victims or making unsupported accusations. Follow this checklist before posting.
Immediate safety steps
• Stop interacting with the suspicious site, account, contract, extension, bot, or application.
• Do not share a seed phrase, private key, password, authentication code, API secret, or recovery file.
• Revoke suspicious token approvals and active sessions using official tools you independently verified.
• Move remaining assets only if you understand the risk and can use a known-safe device and destination.
• Preserve evidence before deleting messages or reinstalling software.
What to include
1. A factual title naming the product, domain, account, address, or campaign involved.
2. Date, time, network, application version, and affected platform.
3. A chronological description of what happened.
4. Official links, transaction hashes, contract addresses, repository issues, or security advisories when available.
5. Screenshots with names, email addresses, IP addresses, balances, and other private data removed.
6. The exact warning signs and practical steps other users can take.
7. Whether the incident was reported to the provider, exchange, wallet team, hosting company, or relevant authority.
What not to include
• Seed phrases, private keys, passwords, full API keys, session tokens, or recovery codes.
• Unredacted identity documents, private conversations, personal addresses, or financial records.
• Guesses about a person’s identity or intent presented as fact.
• Requests for vigilante action, harassment, hacking, doxxing, or retaliation.
• Referral links, recovery-service promotions, or guaranteed fund-recovery claims.
Choose the right prefix
Use Scam Alert for a specific documented threat. Use Guide for general prevention material and News for a sourced, time-sensitive security update.
Evidence standard
A blockchain transaction proves that a transaction occurred; it does not automatically prove who controlled an address or why the transaction happened. Clearly separate direct evidence, third-party reporting, and your interpretation.
If funds or accounts are at immediate risk, use official support and incident-reporting channels first. A forum thread can warn the community, but it is not a substitute for professional legal, security, or financial assistance.
Immediate safety steps
• Stop interacting with the suspicious site, account, contract, extension, bot, or application.
• Do not share a seed phrase, private key, password, authentication code, API secret, or recovery file.
• Revoke suspicious token approvals and active sessions using official tools you independently verified.
• Move remaining assets only if you understand the risk and can use a known-safe device and destination.
• Preserve evidence before deleting messages or reinstalling software.
What to include
1. A factual title naming the product, domain, account, address, or campaign involved.
2. Date, time, network, application version, and affected platform.
3. A chronological description of what happened.
4. Official links, transaction hashes, contract addresses, repository issues, or security advisories when available.
5. Screenshots with names, email addresses, IP addresses, balances, and other private data removed.
6. The exact warning signs and practical steps other users can take.
7. Whether the incident was reported to the provider, exchange, wallet team, hosting company, or relevant authority.
What not to include
• Seed phrases, private keys, passwords, full API keys, session tokens, or recovery codes.
• Unredacted identity documents, private conversations, personal addresses, or financial records.
• Guesses about a person’s identity or intent presented as fact.
• Requests for vigilante action, harassment, hacking, doxxing, or retaliation.
• Referral links, recovery-service promotions, or guaranteed fund-recovery claims.
Choose the right prefix
Use Scam Alert for a specific documented threat. Use Guide for general prevention material and News for a sourced, time-sensitive security update.
Evidence standard
A blockchain transaction proves that a transaction occurred; it does not automatically prove who controlled an address or why the transaction happened. Clearly separate direct evidence, third-party reporting, and your interpretation.
If funds or accounts are at immediate risk, use official support and incident-reporting channels first. A forum thread can warn the community, but it is not a substitute for professional legal, security, or financial assistance.