Block ARM-in-ARM Virtual Devices for Android & iOS Apps

Last updated May 7, 2024 by Appdome

Learn to Block ARM-in-ARM Virtual Devices in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are ARM-in-ARM Virtual Devices?

A Virtual ARM-in-ARM device is a form of virtual machine that forces an app to run on a “guest” system above the OS (not the true physical mobile device or the true OS). This allows for a new attack vector that circumvents traditional security controls for both Android and iOS.

Why Block ARM-in-ARM Virtual Devices in Mobile Apps?

Virtual ARM-in-ARM environments can be used to weaponize apps for fraud or other forms of attacks. With Appdome Block Virtual ARM-in-ARM devices, apps can be protected from this attack vector.

Prerequisites for Using Block ARM-in-ARM Virtual Devices:

To use Appdome’s mobile app security build system to Block ARM-in-ARM Virtual Devices , you’ll need:

Block ARM-in-ARM Virtual Devices on Mobile apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Block ARM-in-ARM Virtual Devices 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. Block ARM-in-ARM Virtual Devices Compatible With: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
  2. Build the feature: Block ARM-in-ARM Virtual Devices.

    1. Building Block ARM-in-ARM Virtual Devices by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Block ARM-in-ARM Virtual Devices feature as shown below:
      2. fusion set that contains Block ARM-in-ARM Virtual Devices

        Figure 1: Fusion Set that will contain the Block ARM-in-ARM Virtual Devices 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 Block ARM-in-ARM Virtual Devices feature via Appdome Console, to add the Block ARM-in-ARM Virtual Devices 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 Block ARM-in-ARM Virtual Devices feature via Appdome Console

      To build the Block ARM-in-ARM Virtual Devices protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Fraud Detection section.
      2. How: Check whether is toggled On (enabled), otherwise enable it . The feature Block ARM-in-ARM Virtual Devices is enabled by default, as shown below. Toggle (turn ON) Block ARM-in-ARM Virtual Devices, as shown below.
        If needed, Customize the Threat Notification to be displayed to the mobile end-user in a standard OS dialog notification when Appdome Blocks ARM-in-ARM Virtual Devices.
        Block ARM-in-ARM Virtual Devices option

        Figure 3: Block ARM-in-ARM Virtual Devices option
        Note: The App Compromise Notification contains an easy to follow default remediation path for the mobile app end user. You can customize this message as required to achieve brand specific support, workflow or other messaging.

      3. When you select the Block ARM-in-ARM Virtual Devices you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Block ARM-in-ARM Virtual Devices

        Fusion Set applied Block ARM-in-ARM Virtual Devices

        Figure 4: Fusion Set that displays the newly added Block ARM-in-ARM Virtual Devices protection

      4. Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Block ARM-in-ARM Virtual Devices:
        1. Threat-Events™ OFF > In-App Defense

          If the Threat-Events™ setting is cleared (not selected). Appdome will detect and defend the user and app by enforcing Block ARM-in-ARM Virtual Devices.

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

          When this setting is used, Appdome detects virtual ARM-in-ARM devices 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™ for Block ARM-in-ARM Virtual Devices Intelligence and Control in Mobile Apps.

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

          When this setting is used, Appdome detects and defends against ARM-in-ARM Virtual Devices (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence 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 Block ARM-in-ARM Virtual Devices Intelligence and Control in Mobile Apps.

      5. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Block ARM-in-ARM Virtual Devices protection is now added to the mobile app
  3. Certify the Block ARM-in-ARM Virtual Devices feature in Mobile Apps

    After building Block ARM-in-ARM Virtual Devices, Appdome generates a Certified Secure™ certificate to guarantee that the Block ARM-in-ARM Virtual Devices protection has been added and is protecting the app. To verify that the Block ARM-in-ARM Virtual Devices protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Block ARM-in-ARM Virtual Devices 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 Block ARM-in-ARM Virtual Devices has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block ARM-in-ARM Virtual Devices and other mobile app security features are in each build of the mobile app

Using Threat-Events™ for ARM-in-ARM Virtual Devices Intelligence and Control in Mobile Apps

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

The specifications and options for Threat-Events™ for ARM-in-ARM Virtual Devices are:

Threat-Event™ Elements Block ARM-in-ARM Virtual Devices Method Detail
Appdome Feature Name Block ARM-in-ARM Virtual Devices
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 Blocking ARM-in-ARM Virtual Devices Threat-Event™
Threat-Event NAME CorelliumFileFound
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6933
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
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
data Corellium file path

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 ARM-in-ARM Virtual Devices are detected.

The following is a code sample for native Mobile apps, which uses all values in the specification above for Block ARM-in-ARM Virtual Devices:


Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Block ARM-in-ARM Virtual Devices. 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 Block ARM-in-ARM Virtual Devices

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?

Know Your Customer

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