Remote Access Scams: Never Give a Stranger Control of Your Device

Someone calls unexpectedly and says they can fix a security problem. They ask you to install software, read out a connection code or share your screen. It can sound like ordinary technical support, but it may give the person access to your accounts and private information.

Never allow an unknown caller to control your device because they claim to represent a bank, police, CoinByte or another exchange. Verify the contact independently before following any troubleshooting instructions.

Key takeaways

• Legitimate remote access software can be misused by scammers.

• Screen sharing can expose information even without full device control.

• If access is ongoing, end the session and seek help using a trusted device.

What is remote access?

Remote access tools let another person view or operate a device from elsewhere. AnyDesk, TeamViewer and other remote desktop applications have legitimate uses. Their names appearing in a request do not authenticate the person making it.

Screen sharing may provide a view without control. That can still reveal balances, messages, identity documents and verification codes. A caller does not need to take over every function of a device to cause harm.

The risk depends on the permission you give and what is visible during the session. If you are unsure what access a tool provides, stop before granting it.

How the scam can unfold

A caller claims your account or device has a problem. They may say they have detected unauthorised transactions or need to inspect a security alert. They keep you on the phone and guide the installation of a remote support tool.

Once access is granted, they may ask you to sign in to online banking or CoinByte. A verification code is then explained as part of fixing the problem, even though it may authorise an account action.

Scamwatch's remote access scam alert describes criminals using familiar screen-sharing software and requesting banking information or security codes.

Pay attention to who initiated the contact. Support you deliberately sought through a verified channel is a different situation from an unknown caller diagnosing a problem and choosing the remedy.

Requests that should make you stop

• Install an app during an unexpected security call.

• Approve a remote connection without knowing who will receive access.

• Open banking, email or exchange accounts while sharing the screen.

• Show an authentication code, recovery phrase or identity document.

• Leave the remote session running while you make payments.

• Ignore a warning from your device or financial institution.

Do not assume disabling control makes the whole session safe. If the screen remains visible, information can still be exposed. You can end a conversation and independently contact support without proving the caller is a scammer first.

A fictional example

This scenario is invented and does not describe a CoinByte customer.

Helen receives a call from someone claiming to work in technical support. They say malware is interfering with her banking and ask her to install a remote desktop app.

During the session, the caller asks Helen to sign in to her bank and CoinByte so they can check whether funds are safe. They then ask her to display a code sent to her phone.

Helen stops. She ends the session and contacts her bank and CoinByte from another device. The request to expose financial accounts is enough reason to seek independent help, even before she knows whether any payment occurred.

If someone has already accessed your device

First end the remote session. If you cannot be sure access has stopped, disconnect the affected device from the internet. Use a different device you trust to contact relevant services.

Tell CoinByte if its account was opened during the session. Tell your bank if banking was accessed, and explain whether passwords or codes were visible. Do not wait for evidence of theft before reporting potential access.

Have unwanted remote access software and possible malware checked by a trusted IT professional. If the device still may be compromised, do not enter replacement passwords on it. ASD's ACSC provides guidance on recovering from hacking.

Keep a note of the application used, approximate session time and actions requested. Preserve records already available, but do not reconnect with the caller to gather information.

Make future support contact safer

If someone unexpectedly claims to be CoinByte support, end the conversation and open CoinByte independently. Use the support options published on the official website or app to check the request.

The CoinByte account security section is a starting point for published account guidance. Follow What to Do If You Think You've Been Scammed if account details, identity information or funds may be affected.