Evaluate an Unexpected Message Offering Wallet Help
An unexpected helper may know your public error report, address or recent transaction. That knowledge does not prove authority to access your wallet or solve the problem they describe.
Separate recognition from authentication
An impersonator can repeat details from a public post and use familiar branding to make a reply feel official. MetaMask’s spoofing guidance describes attackers using support requests as opportunities to approach users. Evaluate the sender through an independently obtained channel, not a badge screenshot or a verification link in the message. This page does not name an official RunixCoin support account, so do not treat a matching display name as confirmation.
Identify what the helper wants you to do
Write the proposed action in plain language: reveal recovery words, install software, sign a payload, connect to another site or send a payment. A claim such as “synchronize your wallet” does not explain any of those permissions. For a display or quote error, public read-only observations should come first. Decline instructions that require account-control material or unexplained authorization merely to inspect a public balance.
Do not continue a pressured conversation
Urgency, a countdown or a threat of permanent loss can make normal checking feel inconvenient. Pause and leave the message thread while you independently inspect the relevant transaction or product documentation. Do not open attachments to prove that a sender is legitimate. If preserving a record, save a sanitized description privately and avoid publishing malicious links as clickable recommendations. Blocking or reporting a sender through the messaging platform does not itself revoke any permission previously granted.
Keep the product limit visible
RunixCoin’s public Base form provides estimates and has no swap execution. An unsolicited claim that you must sign to repair a completed public-form trade conflicts with that inspected scope. If you already interacted with a suspicious request, distinguish whether you only read a message, exposed an address, signed something or submitted a transaction; those events need different investigation. Do not send additional funds or secrets to a second stranger promising to undo the first interaction.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.