An unexpected warning says your device is infected and gives a number to call. The person who answers asks you to install a remote-access program, share your screen, or open a financial account while they watch. You may have begun by wanting an explanation of a warning. The proposed task is now much bigger: giving another person the ability to see or influence what happens on your device.
The FTC describes fake support warnings and requests for remote access. A technical-looking display or a confident diagnosis is not independent proof. For an unexpected contact, do not install their software or grant control. Seek device help through a manufacturer or another support provider you independently know and trust.
Name the new permission
A helpful distinction is explanation versus access. Someone can explain a public feature without viewing your paycard account. Viewing a screen can reveal information unrelated to the original question. Granting remote control can go further. You do not need to determine every technical capability of a proposed app before deciding that the requested access exceeds what you intended.
In a fictional example, a worker searches for help with an error message and reaches a page that displays a dramatic warning. A supposed technician asks the worker to open a financial app to check whether the infection affected money. The request joins two unrelated tasks: diagnosing a device and inspecting an account. The worker can stop both steps and find independent help without proving the warning was fabricated.
Do not use an account as a demonstration
A person may call an action a test, a simulation or a harmless training step. Those words do not make a real transfer fictional. Avoid opening financial accounts, moving money, or typing credentials while an unexpected person is watching or controlling the device. A real payment screen remains consequential even when someone says the amount will be reversed immediately.
An original rehearsal uses only words: identify the warning, the offered help, the requested permission, and the point at which you would stop. Do not install a remote-access application to practice refusing it. Do not create a fake login page. The learning goal is recognizing the boundary early enough that no live account is needed.
If access was already granted
Stop interacting with the suspicious contact. Seek trusted technical help to end the access and assess the device. If account information or money may be exposed, promptly reach the affected provider through a trusted route, using a different trusted device if needed. Explain that remote access or screen viewing occurred. Follow the provider’s protective process and trusted technical guidance; this article cannot establish that a device is clean.
A password change is only one possible part of recovery, and should not be performed in a setting the other person may still control. Do not resume contact because the caller claims they need to undo their work. After urgent protection, note the approximate time, program name if known, and accounts that were displayed. Read the exposure review and recovery-fee warning for the next decisions. This publication does not connect to devices or provide technical support.
Sources and reading boundaries
Sources checked October 7, 2026. This is a review date, not a policy effective date or an account test.
- FTC: Tech Support Scams: Unexpected support warnings, remote-access pressure and staged transfer to supposed officials. Review basis: Official source text reviewed through search-index retrieval; direct navigation may be unavailable.
- FTC: What To Do if You Were Scammed: Prompt payment-provider contact and recovery requests, account and identity recovery routes. No promise of reimbursement. Review basis: Official source text reviewed through search-index retrieval; direct navigation may be unavailable.