Skip to content
Stay aware. Stay safe.Social-Engineering Defense
StopVerifyRespond
Vol. I · No. 124Tuesday, November 17, 2026Digital Edition · Free
← Case Stories

Susan Thought She Was Fixing a Virus

An illustrative scenario: a frightening pop-up sends Susan to a supposed support agent. When she allows remote access, a stranger gains control of her computer.

What happened

Susan sees a warning on her screen: “System infected. Call now.” She worries about her files and calls the number in the pop-up.

The person answering sounds calm and professional. They say her files are in danger and that remote access is needed immediately. The warning creates fear; the confident voice makes the proposed solution feel reassuring.

Susan clicks “Allow.” The supposed helper can now control her screen. That access could put her files, accounts, and private information at risk.

Susan is an illustrative character from our existing tech support script, not an identified victim. The scenario shows how a false warning can turn a desire to solve a problem into permission for a stranger to enter a device. A pop-up's phone number is not a verified support channel.

Susan wants the warning to go away and her computer to be safe. The caller offers a clear action at a stressful moment: allow access so the problem can be fixed. That combination makes the request feel helpful, even though Susan has not established who is on the other end of the call.

The caller's confidence is part of the pressure. A calm voice can make a frightening pop-up seem more credible, especially when the person repeats that delay will put files at risk. Susan is pushed to solve the apparent emergency before checking the source of the warning.

The “Allow” button is the turning point. It is a permission decision, not simply another step in reading the alert. Once Susan grants control, the supposed helper can interact with the computer. The story does not establish that files were stolen or that every account was accessed; it shows why granting that permission to an unverified person creates risk.

Afterward, the useful response is to regain control and check what happened. Ending access is the first step, followed by checking the device and protecting any information that was exposed. Susan should also use a genuine support channel if she still has a technical problem. The stranger's claim that the computer is infected does not establish the diagnosis, and continuing with the same caller does not establish a trustworthy repair.

Red flags

  • An unexpected warning that tells you to call a displayed number.
  • A claim that your files will be lost unless you act immediately.
  • A supposed support agent asking for remote access before you verify them.
  • Instructions to install unfamiliar software or share passwords.
  • Payment demands made through the warning or its phone contact.

How to protect yourself

A frightening alert deserves a calm check through a support channel you trust.

STOP before calling a pop-up's number, installing software, or allowing remote access. Do not let the warning decide who gets access to your device.

VERIFY by closing the alert and opening the software company's official support website yourself. At work, use your known helpdesk portal or company directory.

RESPOND by reporting the scam. If you allowed access, end the remote session and remove the software the caller told you to install. Update your security software and run a scan. Change exposed passwords from a different trusted device. If you paid, contact the card issuer or payment provider promptly and explain the scam. Ask about reversal or refund options; recovery is not guaranteed.

For a work computer, notify your genuine IT or security team.

Stay aware. Stay safe.