How to Detect Remote Desktop Scams in Mobile Apps Using AI

Last updated February 16, 2025 by Appdome

This Knowledge Base article describes how to use Appdome’s AI/ML in your CI/CD pipeline to continuously deliver plugins that Prevent Remote Desktop Scam in Android apps.

What Is a Remote Desktop Scam?

A Remote Desktop Scam exploits remote access tools to gain control over a mobile device, typically by tricking users into granting access through social engineering tactics disguised as technical support. Once access is obtained, attackers can steal login credentials, manipulate transactions, access sensitive data, and tamper with app functions by injecting or intercepting key events and user inputs. Commonly misused tools like TeamViewer, AnyDesk, and AirDroid facilitate these scams, posing significant risks to user accounts and financial transactions. As AI-powered agents evolve, they could automate remote control attacks, making detection and defense more challenging and increasing the risk of account takeovers and fraudulent transactions on mobile platforms. Protecting against these attacks is essential to comply with regulations such as PCI DSS, which mandate secure access and data handling to prevent unauthorized manipulation.

How Appdome Protects Mobile Apps Against Remote Desktop Scams?

Appdome’s dynamic Detect Remote Desktop Scams plugin for Android defends against remote access tools that allow attackers to gain unauthorized control of Android devices, posing risks such as data theft, credential compromise, and transaction manipulation. The plugin continuously monitors the Android environment for popular remote desktop tools such as TeamViewer, AnyDesk, AirDroid, and VNC by detecting suspicious input events, mirrored displays, unauthorized screen sharing, and remote control service activity. The plugin automatically detects and blocks remote desktop control attempts by identifying abnormal device interactions, such as simulated touch events, keypress injections, and remote screen broadcasts. The plugin also monitors system APIs, accessibility services, and system settings commonly exploited by remote control tools. When a threat is detected, the plugin triggers in-app defenses to close the app. Mobile developers can leverage Appdome’s Threat-Events™ to collect detailed data on remote desktop control events and create customized in-app responses based on detected threats.

Prerequisites for Using Appdome's Prevent Remote Desktop Scam Plugins:

To use Appdome’s mobile app security build system to Prevent Remote Desktop Scam , you’ll need:

How to Implement Prevent Remote Desktop Scam in Android Apps Using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Prevent Remote Desktop Scam without an SDK or gateway:

  1. Designate the Mobile App to be protected.

    1. Upload an app via the Appdome Mobile Defense platform GUI or via Appdome’s DEV-API or CI/CD Plugins.

    2. Android Formats: .apk or .aab
    3. Prevent Remote Desktop Scam is compatible with: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps.
  2. Select the defense: Prevent Remote Desktop Scam.

      1. Create and name the Fusion Set (security template) that will contain the Prevent Remote Desktop Scam feature as shown below:
        fusion set that contains Prevent Remote Desktop Scam

        Figure 1: Fusion Set that will contain the Prevent Remote Desktop Scam feature

      2. Follow the steps in Sections 2.2-2.2.2 of this article to add the Prevent Remote Desktop Scam feature to your Fusion Set via the Appdome Console.

      3. When you select the Prevent Remote Desktop Scam you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains Prevent Remote Desktop Scam.

        Fusion Set applied Prevent Remote Desktop Scam

        Figure 2: Fusion Set that displays the newly added Prevent Remote Desktop Scam protection
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set. Copy the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 3: Fusion Set Detail Summary

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, Jenkins, Travis, Team City, Circle CI or other system:
        1. Refer to the Appdome API Reference Guide for API building instructions.
        2. Look for sample APIs in Appdome’s GitHub Repository.
    1. Add the Prevent Remote Desktop Scam feature to your security template.

      1. Navigate to Build > Anti ATO tab > Social Engineering Prevention section in the Appdome Console.
      2. Toggle On > Prevent Remote Desktop Scam.

        (a) Choose to monitor this attack vector by checking the Threat Events checkbox associated with Prevent Remote Desktop Scam as shown below.

        (b) To receive mobile Threat Monitoring, check the ThreatScope™ box as shown below. For more details, see our knowledge base article on ThreatScope™ Mobile XDR.
        Prevent Remote Desktop Scam option

        Figure 4: Selecting Prevent Remote Desktop Scam

        Note: The Appdome Platform displays the Mobile Operation Systems supported by each defense in real-time. For more details, see our OS Support Policy KB.

      3. Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Prevent Remote Desktop Scam:
        1. Threat-Events™ OFF > In-App Defense

          If the Threat-Events™ setting is not selected. Appdome will detect and defend the user and app by enforcing Remote Desktop Scam.

        2. Threat-Events™ ON > In-App Detection

          When this setting is used, Appdome detects Remote Desktop Exploits and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing, enforcement, and user notification. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ to Prevent Remote Desktop ScamPrevent Intelligence and Control in Mobile Apps.

        3. Threat-Events™ ON > In-App Defense

          When this setting is used, Appdome detects and defends against Remote Desktop Scam (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Prevent Remote Desktop ScamPrevent Intelligence and Control in Mobile Apps.

      4. Configure the User Experience Options for Prevent Remote Desktop Scam:
        With Threat-Events™ OFF, Appdome provides several user experience options for mobile brands and developers.
        1. App Compromise Notification: Customize the pop-up or toast Appdome uses to notify the user when a threat is present while using the protected mobile app.
        2. Short message Option. This is available for mobile devices that allow a banner notification for security events.
        3. Localized Message Option. Allows Appdome users to support global languages in security notifications.

          Localized Message

          Figure 5: Default User Experience Options for Appdome’s Remote Desktop Scam

        4. Prevent Remote Desktop Scam Threat Code™. Appdome uses AI/ML to generate a unique code each time Prevent Remote Desktop Scam is triggered by an active threat on the mobile device. Use the code in Appdome Threat Resolution Center™ to help end users identify, find and resolve active threats on the personal mobile devices.
    2. Initiate the build command either by clicking Build My App at the bottom of the Build Workflow (shown in Figure 4) or via your CI/CD as described in Section 2.1.4.
    Congratulations!  The Prevent Remote Desktop Scam protection is now added to the mobile app
  3. Certify the Prevent Remote Desktop Scam feature in Android Apps

    After building Prevent Remote Desktop Scam, Appdome generates a Certified Secure™ certificate to guarantee that the Prevent Remote Desktop Scam protection has been added and is protecting the app. To verify that the Prevent Remote Desktop Scam protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Prevent Remote Desktop Scam shown in Certificate secure

    Figure 6: Certified Secure™ certificate

    Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Prevent Remote Desktop Scam has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Prevent Remote Desktop Scam and other mobile app security features are in each build of the mobile app.

Using Threat-Events™ for Remote Desktop Scam Intelligence and Control in Android Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Remote Desktop Scam is detected. To consume and use Threat-Events™ for Remote Desktop Scam in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for Remote Desktop Scam shown below.

The specifications and options for Threat-Events™ for Remote Desktop Scam are:

Threat-Event™ Elements Prevent Remote Desktop Scam Method Detail
Appdome Feature Name Prevent Remote Desktop Scam
Threat-Event Mode
OFF, IN-APP DEFENSE Appdome detects, defends and notifies user (standard OS dialog) using customizable messaging.
ON, IN-APP DETECTION Appdome detects the attack or threat and passes the event in a standard format to the app for processing (app chooses how and when to enforce).
ON, IN-APP DEFENSE Uses Appdome Enforce mode for any attack or threat and passes the event in a standard format to the app for processing (gather intel on attacks and threats without losing any protection).
Certified Secure™ Threat Event Check
Visible in ThreatScope™
Developer Parameters for Preventing Remote Desktop Scam Threat-Event™
Threat-Event NAME IlegalDisplayEvent
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6926
Threat-Event SCORE
packageName Remote desktop application
currentThreatEventScore Current Threat-Event score
threatEventsScore Total Threat-events score
Threat-Event Context Keys
message Message displayed for the user on event
failSafeEnforce Timed enforcement against the identified threat
externalID The external ID of the event which can be listened via Threat Events
osVersion OS version of the current device
deviceModel Current device model
deviceManufacturer The manufacturer of the current device
fusedAppToken The task ID of the Appdome fusion of the currently running app
kernelInfo Info about the kernel: system name, node name, release, version and machine.
carrierPlmn PLMN of the device. Only available for Android devices.
deviceID Current device ID
reasonCode Reason code of the occurred event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device. Only available for Android.
updatedOSVersion Is the OS version up to date
deviceBrand Brand of the device
deviceBoard Board of the device
buildUser Build user
buildHost Build host
sdkVersion Sdk version
timeZone Time zone
deviceFaceDown Is the device face down
locationLong Location longitude conditioned by location permission
locationLat Location latitude conditioned by location permission
locationState Location state conditioned by location permission
wifiSsid Wifi SSID
wifiSsidPermissionStatus Wifi SSID permission status
threatCode The last six characters of the threat code specify the OS, allowing the Threat Resolution Center to address the attack on the affected device.

With Threat-Events™ enabled (turned ON), Android developers can get detailed attack intelligence and granular defense control in Android applications and create amazing user experiences for all mobile end users when Remote Desktop Scam is detected.


The following is a code sample for native Android apps, which uses all values in the specification above for Prevent Remote Desktop Scam:


Important! Replace all placeholder instances of <Context Key> with the specific name of your threat event context key across all language examples. This is crucial to ensure your code functions correctly with the intended event data. For example, The <Context Key> could be the message, externalID, OS Version, reason code, etc.



Using Appdome, there are no development or coding prerequisites to build secured Apps by using Prevent Remote Desktop Scam. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.

Releasing and Publishing Mobile Apps with Prevent Remote Desktop Scam

After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:

Related Articles:

How Do I Learn More?

If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.

Want a Demo?

Social Engineering Prevention

GilWe're here to help
We'll get back to you in 24 hours to schedule your demo.

Search Appdome Solutions

Search
Blog Post 1377x900@2x

Top 5 Reasons You Need Geo Fencing in Mobile Apps

The mobile economy is global. People travel constantly, interacting with apps across borders, and brand value transcends geographic boundaries. Yet, despite this global reach, geofencing remains a crucial strategy…