Screen sharing during a banking call: why it is risky

Screen sharing turns a private banking session into a live broadcast. A fraudster who can see your screen may learn balances, payees, security prompts and one-time codes, and remote-control software can go further by letting them interact with the device.

Seeing the screen can be enough to make the next scam much stronger

Even without full remote control, screen sharing can reveal account balances, recent transactions and the exact wording of security prompts. A criminal can use that information to tailor instructions in real time.

For example, seeing that you have £18,400 available allows the caller to choose a plausible transfer amount and claim they are “protecting” the precise balance shown on screen.

Practical checkpoint for screen sharing during a banking call: establish the starting position before you change anything. Use a caller who asks to install remote-help software and then open the banking app as a worked example and write down caller number, software installed, session time, bank logins and any transactions made during the call. That turns 'Seeing the screen can be enough to make the next scam much stronger' into a testable sequence rather than a vague problem.

Remote control creates a larger risk than ordinary screen sharing

If you install remote-access software, the other person may be able to move the pointer, open windows or alter what you can see. A legitimate piece of support software does not make an unsolicited banking call legitimate.

Banks do not need control of your computer to move money to safety. If the caller says remote access is required to reverse fraud, end the call.

Run the numbers or sequence on paper before repeating the action. In the example of a caller who asks to install remote-help software and then open the banking app, separate the amount, date, channel and decision point, then mark which part is confirmed and which part is still an assumption. For 'Remote control creates a larger risk than ordinary screen sharing', the useful question is not simply whether something can work, but what result you should see next and how long you are prepared to wait before changing route.

Second check for section 2, 'Remote control creates a larger risk than ordinary screen sharing': use a caller who asks to install remote-help software and then open the banking app and write a one-line expected result beside the actual result. Then verify caller number, software installed, session time, bank logins and any transactions made during the call. If the two do not match, pause rather than creating another transaction or application. Disconnect remote access, contact the bank independently and assess the device before using it again for financial access.

Never open banking while a stranger is connected

If a remote session is already active for legitimate IT support, close it before opening financial accounts. If the support request came from an unexpected caller, end it entirely and verify the organisation independently.

Do not assume that minimising the banking window hides it. Remote software can have broader access than what you think is visible.

Use a controlled process for 'Never open banking while a stranger is connected'. Gather caller number, software installed, session time, bank logins and any transactions made during the call, take one deliberate action, and record the result before trying a second route. Do not enter passwords or one-time codes while another person can see or control the screen. If the first route clearly cannot complete the job, disconnect remote access, contact the bank independently and assess the device before using it again for financial access rather than improvising with an unverified workaround.

After accidental sharing, check both the device and the bank

The NCSC advises a full antivirus scan where suspicious software was installed. In parallel, contact the bank if credentials, security codes or financial information were exposed. One response protects the device; the other protects the money.

Review new beneficiaries, wallet registrations, password or phone-number changes and payments. Criminals may prepare access before taking money.

Build a failure plan before the deadline matters. For screen sharing during a banking call, decide what you will do if the normal route fails at the worst reasonable moment: a bill is due, a payment is time-critical, a phone is unavailable or verification will not complete. Keep enough time and money outside the process to recover. Under 'After accidental sharing, check both the device and the bank', note the exact error or refusal wording because that is usually more useful to support than a general statement that it did not work.

Second check for section 4, 'After accidental sharing, check both the device and the bank': use a caller who asks to install remote-help software and then open the banking app and write a one-line expected result beside the actual result. Then verify caller number, software installed, session time, bank logins and any transactions made during the call. If the two do not match, pause rather than creating another transaction or application. Disconnect remote access, contact the bank independently and assess the device before using it again for financial access.

A second caller may pretend to clean up the first incident

After you disconnect, somebody may call claiming to be a senior fraud investigator or recovery technician. Do not restore screen sharing to prove what happened.

Reconnect to the bank or legitimate IT provider through contact information you find independently and continue from there.

Treat evidence as part of the solution, not paperwork added afterwards. For 'A second caller may pretend to clean up the first incident', keep caller number, software installed, session time, bank logins and any transactions made during the call in one dated folder and write a two-line chronology of each contact. Do not enter passwords or one-time codes while another person can see or control the screen, and use only a channel you reached independently when security or fraud is involved.

Second check for section 5, 'A second caller may pretend to clean up the first incident': use a caller who asks to install remote-help software and then open the banking app and write a one-line expected result beside the actual result. Then verify caller number, software installed, session time, bank logins and any transactions made during the call. If the two do not match, pause rather than creating another transaction or application. Disconnect remote access, contact the bank independently and assess the device before using it again for financial access.

What a scammer can see in one shared-screen session

Screen sharing turns private banking information into live intelligence. A caller may see balances, account numbers, saved payees, incoming security messages and the exact buttons needed to approve a transfer. Even if you never read out a password, the scammer can coach you through actions that make the payment appear to be your own decision. That is why a bank fraud team has no legitimate need to watch you log in or move money on your screen.

If you already shared the screen, end the session, disconnect the device from the internet and contact the bank from another trusted device. Tell the bank exactly what was visible and whether you entered credentials or approved any payments. Then secure email and other accounts that were open on the device. NCSC guidance on hacked devices recommends treating remote-control access as a wider device compromise, not only a banking incident.

Do not reinstall the remote-access application merely because the caller says it is needed to reverse a payment. If money was sent, report the transfer and the deception immediately. Preserve the call number, remote-access app name, session time and any transfer reference; those details can help the bank assess both fraud recovery and device risk.

Finish with a decision rule for screen sharing during a banking call. In the worked example of a caller who asks to install remote-help software and then open the banking app, the safer next step is the one that preserves evidence and keeps essential money or account access recoverable. If the provider cannot explain the next step clearly, disconnect remote access, contact the bank independently and assess the device before using it again for financial access and keep the case reference until the outcome is reconciled.

Sources and verification

• NCSC - Phishing scams: what to do
• FCA - Fraudulent payments
• NCSC - hacked-device recovery guidance
• NCSC - scam-call verification

MyBankAnswers uses official provider and UK regulatory sources wherever practical. Information is general and does not constitute financial advice.