How to Detect Malicious Proxies in Android & iOS Apps

Last updated June 2, 2024 by Appdome

Learn to Detect Malicious Proxy in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are Malicious Proxies?

Malicious proxies are proxy servers that are often used by malicious agents in mobile Man in the Middle (MiTM) attacks.

Hackers target insecure networks and Wi-Fi connections and hijack the connection between a mobile app and the server to which the app tries to connect. They then redirect the session to malicious proxies so they can perform malevolent actions such as harvesting data, stealing credentials, and depositing malware.

How Does Appdome Prevent the use of Malicious Proxy Servers?

When the Malicious Proxy Detection is enabled, Appdome detects any attempt to connect to or from unknown, untrusted, or malicious proxies or other intermediary devices.

Prerequisites for Using Malicious Proxy Detection:

To use Appdome’s mobile app security build system to Detect Malicious Proxy , you’ll need:

Detect Malicious Proxy on Mobile apps using Appdome

On Appdome, follow these simple steps to create self-defending Mobile Apps that Detect Malicious Proxy without an SDK or gateway:

  1. Upload the Mobile App to Appdome.

    1. Upload an app to Appdome’s Mobile App Security Build System

    2. Upload Method: Appdome Console or DEV-API
    3. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
    4. Malicious Proxy Detection Compatible With: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
  2. Build the feature: Malicious Proxy Detection.

    1. Building Malicious Proxy Detection by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Malicious Proxy Detection feature as shown below:
      2. fusion set that contains Malicious Proxy Detection

        Figure 1: Fusion Set that will contain the Malicious Proxy Detection feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      3. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Malicious Proxy Detection feature via Appdome Console, to add the Malicious Proxy Detection feature to this Fusion Set.

      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 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Circle CI or other system:
        1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        2. Look for sample APIs in Appdome’s GitHub Repository
    2. Building the Malicious Proxy Detection feature via Appdome Console

      To build the Malicious Proxy Detection protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > Secure Communication section.
      2. When you enable MiTM Prevention you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Malicious Proxy Detection

        Fusion Set applied Malicious Proxy Detection

        Figure 4: Fusion Set that displays the newly added Malicious Proxy Detection protection

      3. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Malicious Proxy Detection protection is now added to the mobile app
  3. Certify the Malicious Proxy Detection feature in Mobile Apps.

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

    Figure 5: 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 Malicious Proxy Detection has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Malicious Proxy Detection and other mobile app security features are in each build of the mobile app

Using Threat-Events™ for Malicious Proxy Intelligence and Control in Mobile Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Malicious Proxy is detected. To consume and use Threat-Events™ for Malicious Proxy in Mobile Apps, use AddObserverForName in Notification Center, and the code samples for Threat-Events™ for Malicious Proxy shown below.

The specifications and options for Threat-Events™ for Malicious Proxy are:

Threat-Event™ Elements Detect Malicious Proxy Method Detail
Appdome Feature Name Malicious Proxy Detection
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 Detecting Malicious Proxy Threat-Event™
Threat-Event NAME NetworkProxyConfigured
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6510
Threat-Event SCORE
currentThreatEventScore Current Threat-Event score
threatEventsScore Total Threat-events score
Threat-Event Context Keys
message Message displayed for the user on event
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
deviceID Current device ID
reasonCode Reason code of the occured event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device
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

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

The following is a code sample for native Mobile apps, which uses all values in the specification above for Malicious Proxy Detection:

Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Malicious Proxy Detection. 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 Malicious Proxy Detection

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:

If you have any questions, please send them our way at 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?

Mobile Bot Defense

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