Getting a scary message about 'your computer is infected' or a stranger asking to 'quickly remote in' is a common pain. You want to help an elderly relative, fix your own machine, or accept help from a vendor — but you don’t want to hand co…
Getting a scary message about 'your computer is infected' or a stranger asking to 'quickly remote in' is a common pain. You want to help an elderly relative, fix your own machine, or accept help from a vendor — but you don’t want to hand control to a scammer. This guide explains what a tech support scam looks like and, step‑by‑step, how non‑technical users can prevent being tricked into granting dangerous remote access.
What is a tech support scam — in plain English
A tech support scam is when someone pretends to be a legitimate technician (from Microsoft, your ISP, your bank, etc.) to get you to run diagnostics, install software, or give remote access to your computer. The goals vary: steal passwords, install malware, run cryptojackers, or coerce payments. Scammers use phone calls, pop‑up web pages, or phony support emails to create urgency and fear.
They often ask you to install remote control software (TeamViewer, AnyDesk, Chrome Remote Desktop, or something less common) and then ask you to show bank accounts, hand over authentication codes, or pay for 'fixes' via wire transfer, gift cards, or cryptocurrency. The underlying risk isn't the software itself — it's who is on the other end and what permissions you give them.
How scammers contact you and common red flags
Scammers have a few typical approaches. Recognizing the red flags is the fastest way to stop a scam before it starts. If any of the following happen, stop and verify before proceeding.
Before you grant remote access: a simple verification checklist
If someone asks to remote into your machine, follow this short checklist. Each item is something you can do without technical knowledge.
Check official support channels. Look for notices on the company’s website or social media if there’s a widespread issue. For general remote‑access safety and how remote access works in practice, see our guide on how-remote-access-works and the practical steps in how-to-give-someone-remote-access. Safe ways to give someone access — limit scope and time
If you decide to allow a legitimate technician or a trusted friend to help remotely, choose a method that minimizes risk. The key rules are: use temporary sessions, watch what they do, and revoke access immediately after.
Use reputable tools and avoid unknown executables: If a caller insists you download a specific program, verify that program’s name and website independently. Prefer mainstream, vetted tools (Quick Assist, Chrome Remote Desktop, TeamViewer, AnyDesk). If you want a self‑hosted option to avoid third‑party servers, see our self‑hosted remote desktop guide. Record the session if possible: If you’re comfortable, use your phone to record the screen and audio. This creates a timestamped record of what occurred.During the session — what to watch and what to do
Stay actively involved while someone is controlling your machine. You don’t need technical skills to do the following:
toolbars, 'optimizers', or crypto‑mining software, end the session and uninstall anything they placed. Do not accept remote control to "boost" performance; that’s a classic scam move.
Check task manager and downloads folder: After any install, look for unfamiliar executables in Downloads and unfamiliar startup entries. If you see new items, take note of filenames for later scanning.Limit file transfers: Avoid sending documents with passwords or personal data. If a file needs to be shared, use a secure, reputable file transfer service and remove the file after the issue is resolved.After the session — clean up and lock things down
Scammers sometimes wait until after a session to extract value. Do these steps immediately after a legitimate session — especially if it was with someone new to you.
If you discover you were scammed — steps to recover
If you believe you gave access to a scammer, act quickly. The faster you respond, the better the outcome.
Tools and choices — what’s safer for non‑technical users?
There’s no perfectly safe tool — safety comes from process. That said, some options are friendlier to non‑technical users because they default to temporary access and clear consent.
Self‑hosted solutions: If you or your family are comfortable with a more technical setup, self‑hosting remote access eliminates reliance on third‑party relay servers. See our self‑hosted remote desktop guide for details and trade‑offs. If you want a lightweight, non‑commercial option to try, consider tools that allow short‑lived sessions or require local approval for every connection. For those wanting to try GoDesk, you can get the app at /download and review pricing and self‑hosting options at /pricing. We don’t claim one tool fits every case — pick what you understand and can verify.
Quick checklist you can print or read aloud
If you didn’t request support, hang up and call the company back via their official website.Never pay via gift card or wire transfer on the spot.Use built‑in one‑time tools (Quick Assist, Chrome Remote Desktop) where possible.Generate session codes yourself and share them only after verification.Watch the session, record it if you can, and uninstall remote tools when done.Change passwords and scan for malware after the session.Final thoughts
Tech support scams rely on urgency and confusion. A calm, simple verification process — verify identity, use one‑time codes, limit permissions, and clean up afterward — protects non‑technical users in most cases. If you’re managing support for family members, write down the steps above or keep this page handy so a trusted helper can follow a known process.
For a safe walkthrough on how to share remote access correctly, pair this advice with our step‑by‑step how to give someone remote access guide. When you’re ready to try a tool you trust, download GoDesk at /download or compare pricing and hosting options at /pricing.
