📝 Fake poker-support messages: protect your account information

Do not send a login code or password in response to an unexpected message. Verify the sender through a channel you already know. Names, profile pictures and logos can be copied. The origin of the contact and what it asks you to do matter more.

This applies to poker-related messages and to email, apps and other accounts. The article does not assess a particular website; it addresses attempts to access your information.

Examine the request, not just the logo

A phishing message may claim that an account has a problem, request confirmation of information, or urge you to open a link immediately. The FTC recommends contacting a company through a known genuine website or number rather than using the suspicious message's contact details.

Beyond asking whether a message looks official, ask why someone in a conversation needs a code sent to your device, and why you must act before checking calmly.

A message that deserves a pause

This is a fictional example, not a message from a named platform:

“We are support. There is a problem with your account. Send the verification code within two minutes to prevent a suspension.”

It combines claimed authority, time pressure and a request for access. You do not need to argue or prove your identity to the sender. End the exchange and independently open the contact method you know.

You can ask genuine support whether there is an actual issue with your account. Do not include the code in your question or reveal it in a screenshot.

What should stay out of a conversation?

Do not hand a password or login code to a person requesting it. The FTC's guidance on impersonated support explains how a verification code can be used to take over an account.

Entering a code into a trusted login process you initiated differs from sending it to another person. In the latter case, the recipient may be able to complete the process elsewhere.

Review screenshots before sharing them. They may expose an email address, phone number, recovery code or another person's information. Share only what is needed to explain the problem, with unnecessary details concealed.

If you already shared information

Stop sharing more. Reach the security settings through the app or website you know. If you exposed a password, change it and any reused passwords on other accounts. Review active sessions and end unfamiliar ones if the service supports this. Contact genuine support about possible unauthorized access.

If a link or attachment downloaded suspicious software, avoid entering more sensitive information until you can assess the device. The FTC's phishing-response guidance recommends updating security software and scanning for malware.

Record what happened and when, and retain the original message for the genuine support channel. Reporting a problem does not require publishing private information.

Related reading

• Poker terminology and digital safety
• Understanding probability
• Passwords and recovery
• Unknown apps and permissions

FAQ

Does a familiar logo establish the sender's identity?

No. Verify through an independent channel you already trust.

Should I share a code if the sender knows my name?

No. Knowing your name does not entitle someone to your login secrets.

Can a screenshot help support?

Yes, but review it first, hide secrets and unnecessary information, and send it through a verified channel.

Do these checks guarantee that an account is safe?

No. They reduce exposure to phishing; they are not a security certification for a platform.