Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Person assessing a remote-support request and checking the official channel on a separate device

Support impersonation guide · 12 min

Respond to fake technical support without worsening the incident.

An alarming pop-up, apparently official call or chat message may ask you to install a support tool. Break the unverified channel first, then determine whether access, data or payment has been exposed.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Never use the number in an unexpected alert.
  • Check support inside the official app or a website opened separately.
  • If a remote session started, contact the IT team or a trusted professional promptly.
  • Separate installation, account access, data disclosure and payment to guide the response.

Step-by-step method

A reproducible path from question to conclusion.

  1. 1

    Stop the request

    Do not follow the link, call the displayed number or give a sign-in code or password. If already speaking to someone, end the call without arguing about their identity.

  2. Laptop, phone and notebooks on a desk — AI-generated photograph
    2

    Return to a known service

    Open the official application or website yourself, or use contact details already held. Ask whether a support case exists and whether the proposed process matches their normal practice.

  3. 3

    Establish what was granted

    Record whether you only saw an alert, opened a link, installed software, shared a screen, entered a code, sent a file or paid. Each action changes the checks required.

  4. A security key and phone for preparing account access — AI-generated photograph
    4

    Contain granted access

    If someone could control the device, ask the IT team or a trusted professional for help. End the unverified session, avoid using that device for sensitive password changes and have accounts and installed programs assessed.

  5. Editorial illustration: OSINT directory consultation desk
    5

    Protect accounts and payments

    From a trusted device, revoke relevant sessions and change affected credentials. If money or banking details were shared, contact the bank immediately through its official channel.

An on-screen warning does not identify its author

A web page can imitate a system warning and display a support number. A caller may name software you really use. Those details do not establish a mandate or prove a fault exists.

Start verification through a channel you select yourself. Do not authorise software installation or remote control merely because a screen says immediate action is required.

Establish the scope before restoring service

Seeing a message is different from opening a remote session. Record the time, installed tool, signed-in accounts, files opened and actions observed. A short timeline helps a professional find relevant traces.

Immediately deleting a program may remove useful evidence without proving the device is safe. Coordinate assessment with the responsible team, especially for a work device.

Re-establish a trusted channel

After the technical review, check mail forwarding rules, authorised devices and sessions, and accounts used during the exchange. Warn relevant people if messages may have been sent from an affected account.

Keep the URL, displayed number, receipts, timeline and software names without publishing personal data. Reporting steps depend on the harm observed and the territory involved.

Check an unexpected renewal or refund

A message may claim that a support subscription has renewed and ask you to call to cancel it. Open the provider’s account page independently to check the invoice, and look for the charge in your official banking app.

If you find an unfamiliar charge, contact your bank. Never grant remote access to obtain a refund or send money to correct a supposed overpayment.

The software does not validate the support request

A legitimate remote tool can appear in a deceptive request. Verify the original support need and contact independently. Separate displayed window, installed application and granted access: an alarming visual does not establish infection.

Arrange handoff after interruption

Record time, tool, presented contacts, actions and any payment. Do not call the popup’s number for reassurance. Have qualified support examine access and changes: ending a session does not establish absence of persistent changes.

Worked example

A pop-up claims immediate technical support is required

Fictional teaching case, not a client investigation.

Does the solicitation correspond to support actually requested by the user?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
A page displays an alert and a support number.The page presents a problem claim and proposed channel.The alert does not establish the device’s actual condition.
The caller requests installation of a remote-control tool.The request seeks access capability.The caller’s role and authorisation remain unconfirmed.
No ticket was opened and support reached through the official site does not recognise the process.The claimed pathway does not match the verified support process.Whether the device is compromised remains a separate question.

Conclusion to record

Stop the solicitation and withhold the requested access. If access was already granted, inform the technical team of known actions and times rather than continuing the conversation.

What would change the conclusion?

Have the device and access reviewed by independently chosen support; record the checks and measures actually performed.

Check your reasoning

Closing an alert does not prove a device is healthy. Separate stopping the solicitation from technical assessment.

· Open the verification log

Your working sheet

Turn the method into a documented review.

For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. State the limits

Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.

1. Contact origin

Channel, time, displayed number and remote-access request.

Limit: Company names and caller numbers can be spoofed.

2. Remote access

Software, session and observed actions without reusing the supplied link.

Limit: Closing a window may leave an installed agent.

3. Follow-up

Verified provider, exposed accounts and possible payments.

Limit: Do not pay another intermediary promising guaranteed recovery.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo result was found in the recorded scope.Describe queries, coverage and access limitations.

What to check and what to record

Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.

Topic-specific checks
CheckUseful recordInterpretation limit
Contact originChannel, time, displayed number and remote-access request.Company names and caller numbers can be spoofed.
Remote accessSoftware, session and observed actions without reusing the supplied link.Closing a window may leave an installed agent.
Follow-upVerified provider, exposed accounts and possible payments.Do not pay another intermediary promising guaranteed recovery.

Common pitfalls

Four shortcuts that weaken the result.

Headphones, studio microphone and pop filter — AI-generated photograph

Calling the pop-up number

The number may be part of the scam even when the warning looks technical.

Sharing a one-time code

A sign-in code can let a third party open an account without installing software.

Two phones and a backup device before changing devices — AI-generated photograph

Continuing on the exposed device

A device controlled by someone else is a poor place to change sensitive credentials.

A person examining a photograph before describing it — AI-generated photograph

Resetting before assessment

A premature reset may make it harder to establish which accounts and data were affected.

Practical questions

Frequently asked questions.

Is a warning on a website a system alert?

Not necessarily. Close the page without calling its number, then check the device through your usual tools and channels.

Must I immediately unplug the device?

If unauthorised remote control is active, interrupt the connection with help from your IT team when possible. The exact action depends on current activity and evidence needs.

What if I paid the fake support provider?

Contact the bank or payment service promptly through its official channel, keep the receipt and exchanges, and follow the relevant dispute and reporting steps.

Public references

These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.

Cybermalveillance.gouv.fr — fake technical support. French public guidance on first actions, remote access and payments.

US FTC — Tech support scams. Guidance on fake renewals, suspicious refund requests and reporting in the United States.

Editorial scope

Published by Internet Intelligence Service on 26 September 2026. Last content update: 21 November 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.

Find primary portals and their limitations

Editorial responsibility, examples and corrections

Further reading

Editorial resources on other sites