What is happening?
A caller claims your computer, phone, router, or account is infected or compromised, then tries to get remote access, payment, or credentials.
What are they trying to get?
Fear of hacking
What should I do?
Block
What should I not share?
Passwords, Remote access permissions, Payment details, Verification codes
How do I verify?
End the call before installing anything.
Fake Tech Support Remote Access Scam
A caller claims your computer, phone, router, or account is infected or compromised, then tries to get remote access, payment, or credentials.
Best next step
Block the caller and never grant remote access from an unsolicited phone call.
Scam anatomy
Goal
A caller claims your computer, phone, router, or account is infected or compromised, then tries to get remote access, payment, or credentials.
Main pressure
Fear of hacking
Recommended action
Block
Risk tier
critical
Pressure meter
This playbook relies on the risk tier, pressure tactics, and red flags below to describe caller pressure.
How this scam works
- The caller pretends to represent a known technology company, security team, or internet provider.
- They claim your device is infected, hacked, or sending errors.
- They ask you to install remote access software or visit a support link.
- Once connected, they may request payment, steal data, or pressure you to reveal passwords.
What the caller may say
Scam script decoder
They say
“We detected a virus from your device.”
What it means
Fear tactic used to justify remote access or payment.
They say
“Download this support app while I guide you.”
What it means
They may be trying to control your device.
They say
“Do not close the window or your files may be lost.”
What it means
Pressure tactic to keep you from stopping the session.
Pressure tactics
Red flags
- Unexpected support call from a company you did not contact.
- Caller asks you to install remote access software.
- Caller asks for passwords, codes, or payment to fix an issue.
- Caller refuses to let you verify independently.
What not to share
Safe response scripts
How to verify safely
- 1End the call before installing anything.
- 2Do not give remote access to your device.
- 3Open the official website or app of the company yourself.
- 4Run your own trusted security tools if needed.
- 5Change passwords if you already shared credentials or installed software.
When FilterCalls detects this pattern
Recommended protection flow
FilterCalls typically recommends
Block
Safe response
“I do not accept remote support from unsolicited calls. I will contact support through official channels.”
Do not share
Verify through
- 1End the call before installing anything.
- 2Do not give remote access to your device.
Safe callback rule
Never verify the caller using the number that contacted you. Use an official app, official website, statement, saved contact, or a number you already trusted before the call.
Protect someone else
If this call could target a parent, grandparent, coworker, or friend, share the safe response and verification steps. A short pause can prevent a fast mistake.
Decision scenarios
This playbook relates to: possible impersonation, possible robocall.
Related scam call playbooks
Bank OTP Scam
A caller pretends to be from your bank and pressures you to share a one-time password, PIN, card detail, or account verification code.
Open playbookDelivery OTP Scam
A caller claims a package is delayed, blocked, or needs a small fee, then asks for a code, payment, address confirmation, or link click.
Open playbook