Fake technical support and remote access

Why this page exists

• Unsolicited support that wants to control your device is an immediate risk.

Common situations

• Microsoft support AnyDesk
• TeamViewer bank helpdesk
• virus pop-up computer
• Quick Assist scam

What the fraudster is trying to get

• In cases involving the remote support alert, the goal is usually to trigger an action before you have time to check: click, pay, share a code or open access to an account.
• Urgency, fear of losing something and copying a known organisation are used to reduce your attention. None of these things proves the request is real.

Check through an independent channel

• Do not rely on the message you received. Open the official website or app yourself, or use a number already listed on a trusted document.
• Compare the sender, the exact domain, the beneficiary and the action requested. One consistent detail is not enough if the rest of the process leaves the official channel.

What to do now

• Do not install anything.
• Do not let anyone control your phone or computer.
• Disconnect the device if remote access has already started.

If you have already interacted

• Stop the exchange. Change the login details you entered through the official app or website and enable two-factor authentication where available.
• Contact your bank quickly if a payment, card, IBAN, code or validation is involved. Keep the useful evidence for a report.

Scope of this hub

• This hub covers calls, pop-ups and messages that ask for remote access or software.
• The fake technical support file gives the detailed procedure.

Triage and urgency level

• Identify where the contact came from, the tool installed and the accounts visible during the session.
• Cut the connection and secure the accounts from a trusted device if access has already started.

Limits of this classification

• This hub does not confirm the identity or reliability of a contact. For this family, the first check remains: Identify where the contact came from, the tool installed and the accounts visible during the session.
• A situation may fall under several families. Go to the file whose dangerous action matches the real case: The fake technical support file gives the detailed procedure.

Limits of this page

• This page does not prove that a message is safe and does not replace your bank, the police, Safeonweb, a platform or a public service.
• A scam may be new, very well written or described with too little context. Use the result as decision support, not as absolute certainty.
• Before taking a final action, checking through the official channel matters more than the appearance of the received message.

Check through an official channel

• Type the service address yourself or open the official app. Do not use a phone number, link or QR code from the suspicious message to verify the situation.
• When money, card details, a code or account access are involved, the safety action comes first. The analysis can then help organise the evidence.

How to read the result

• A low number of signals does not mean that everything is safe. It only means that this page or analysis did not find decisive evidence with the information available.
• Focus on the requested action: paying, sharing a code, installing an app, approving a bank action or leaving an official platform. That action matters more than a logo, sender name or polished wording.
• If the situation feels urgent, step away from the received message first. Then check calmly through a channel you already trusted before the message arrived.

Belgian reading of this situation

• For the remote support alert, focus on the relevant Belgian next step: open the official channel yourself, contact the bank, use Safeonweb or preserve evidence.
• The right decision for the remote support alert depends on what has already happened. Reading a message is not the same as clicking, paying, sharing a code or granting remote access.

What to do now without panic

• If the remote support alert worries you, choose the next step from the requested action: clicking, paying, sharing a code, installing an app, sending a document or approving account access. Do not rely only on the logo or sender name.
• When the remote support alert involves an urgent, financial or hard-to-undo action, StopArnaques treats the situation as something that must be checked first. Polished wording, a familiar brand or a realistic amount does not make the request reliable by itself.
• If you already acted in a case involving the remote support alert, the order matters more than the label: contact the bank, platform or official service first, preserve evidence next, then compare the situation with similar campaigns.

What can be legitimate

• For the remote support alert, some notifications can be real: a delivery, invoice, administrative document, payment request, security alert or platform message. This is why this page does not claim that every similar message is automatically a scam.
• The difference in a the remote support alert case is verification. A real request should be visible through the app, portal, customer area or phone number that you open yourself, not only through a link, QR code or number included in the suspicious message.
• If the official environment does not show the same request about the remote support alert, amount, reference or beneficiary, it is safer to stop and report or verify the case before continuing.

Limits and responsibility

• For the remote support alert, StopArnaques helps explain signals and choose safer actions, but it does not replace your bank, the police, Safeonweb, the FPS Economy, a platform or the organisation concerned.
• A result about the remote support alert may remain uncertain when the text is too short, when context is missing or when the fraud uses a new variant. In that situation, slow down, verify independently and avoid any irreversible action.
• If the remote support alert involves a payment, code, card, identity document, itsme approval, banking app or remote access, the protective action comes first. Do not wait for a perfect label if harm may already be possible.

Keep evidence and report

• For the remote support alert, keep the message, date, channel, visible sender, neutralised link and useful screenshots. Do not publish personal data or clickable suspicious links on social media.
• Report the remote support alert to the relevant channel when appropriate, for example Safeonweb for suspicious messages, the platform for account abuse and your bank when money or payment details are involved.
• This evidence about the remote support alert can also help link a campaign to a case later without storing raw personal data. That matters if the system is to improve without exposing users unnecessarily.

Frequently asked questions

Useful official sources

• SPF Économie - Allô ? Escrocs au bout du fil - link checked on 2026-09-17
• Febelfin - Fraude au faux support technique bancaire - link checked on 2026-09-17
• SPF Économie - Arnaques téléphoniques - link checked on 2026-09-17
• Safeonweb - Soyez vigilant face aux appels et SMS suspects - link checked on 2026-09-17
• SPF Économie - Victime d'une arnaque ? Que faire ? - link checked on 2026-09-17