How to Detect FaceID Bypass Using Deep Fakes in Mobile Apps

Last updated July 29, 2024 by Appdome

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

What is Deep Fake Facial ID Bypass?

Mobile app deep fake facial ID bypass uses digital manipulation techniques to create a fake facial image that can bypass facial authentication on a mobile device or within a specific mobile application. Attackers can use this technique to gain unauthorized access to a device, such as a smartphone or tablet, by fooling the device’s facial recognition technology.

There are many mechanisms for spoofing images, such as intercepting and modifying the camera preview data from other apps while the preview shown to the user remains unchanged. This mechanism is usually used to steal sensitive data such as bank account details, bank checks, or passwords.

How does Appdome Detect FaceID Bypass?

Upon detecting the operation of the deep fake mechanism, regardless of the application that uses the Android or iOS camera, Appdome will exit the mobile app and display a user notification message of the detection.

Prerequisites for Using Detect FaceID Bypass:

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

Detect FaceID Bypass on Mobile apps using Appdome

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

    1. Building Detect FaceID Bypass by using Appdome’s DEV-API:

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

        Figure 1: Fusion Set that will contain the Detect FaceID Bypass 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 Detect FaceID Bypass feature via Appdome Console, to add the Detect FaceID Bypass 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 Detect FaceID Bypass feature via Appdome Console

      To build the Detect FaceID Bypass protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Social Engineering Prevention section.
      2. How: Check whether is toggled On (enabled), otherwise enable it . The feature Detect FaceID Bypass is enabled by default, as shown below. Toggle (turn ON) Detect FaceID Bypass, 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 Detects FaceID Bypass.
        Detect FaceID Bypass option

        Figure 3: Detect FaceID Bypass 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 Detect FaceID Bypass you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Detect FaceID Bypass

        Fusion Set applied Detect FaceID Bypass

        Figure 4: Fusion Set that displays the newly added Detect FaceID Bypass protection

      4. Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Detect FaceID Bypass:
        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 Detect FaceID Bypass.

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

          When this setting is used, Appdome detects a hook on a camera-related Java method 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 Detect FaceID Bypass Intelligence and Control in Mobile Apps.

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

          When this setting is used, Appdome detects and defends against FaceID Bypass (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 Detect FaceID Bypass Intelligence and Control in Mobile Apps.

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

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

Using Threat-Events™ for FaceID Bypass Intelligence and Control in Mobile Apps

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

The specifications and options for Threat-Events™ for FaceID Bypass are:

Threat-Event™ Elements Detect FaceID Bypass Method Detail
Appdome Feature Name Detect FaceID Bypass
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 FaceID Bypass Threat-Event™
Threat-Event NAME FaceIDBypassDetected
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6939
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

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 FaceID Bypass is detected.


The following is a code sample for native Mobile apps, which uses all values in the specification above for Detect FaceID Bypass:


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 Mobile Apps by using Detect FaceID Bypass. 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 Detect FaceID Bypass

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?

Mobile ATO Prevention

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