How to Detect Face Swap Apps in Android and iOS Apps Using AI

Last updated November 17, 2025 by Appdome

This Knowledge Base article describes how to use Appdome’s AI in your CI/CD pipeline to continuously deliver plugins that Detect Face Swap Apps in Mobile apps.

What are Face Swap Apps?

Face swap apps like FFmpeg and OBS are commonly used to inject pre-recorded or synthesized video streams into mobile apps, bypassing camera-based identity verification. These tools can manipulate media at the system level or inject fake video streams directly into app sessions via screen captures or virtual camera feeds. Attackers use them to defeat liveness detection and impersonate users during high-value actions such as onboarding, login, or financial transactions. The threat is increasingly difficult to detect as these tools become more configurable and operate with minimal footprints. Face swap app detection is essential for fraud prevention, identity integrity, and compliance with KYC and AML mandates.

How Appdome Protects Android and iOS Apps Against Face Swap Apps

Appdome’s dynamic Detect Face Swap Apps plugin defends Android and iOS apps against video injection tools like FFmpeg and OBS. It monitors system-level video input sources and detects anomalies in streaming behavior.

Prerequisites for Using Appdome's Detect Face Swap Apps Plugins:

To use Appdome’s mobile app security build system to Detect Face Swap Apps , you’ll need:

How to Implement Detect Face Swap Apps in Mobile Apps Using Appdome

On Appdome, follow these simple steps to create self-defending Mobile Apps that Detect Face Swap Apps 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. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
    3. Detect Face Swap Apps is compatible with: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more.
  2. Select the defense: Detect Face Swap Apps.

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

        Figure 1: Fusion Set that will contain the Detect Face Swap Apps feature

      2. Follow the steps in Sections 2.2-2.2.2 of this article to add the Detect Face Swap Apps feature to your Fusion Set via the Appdome Console.

      3. When you enable Detect Deepfake Apps you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains Detect Face Swap Apps.

        Fusion Set applied Detect Face Swap Apps

        Figure 2: Fusion Set that displays the newly added Detect Face Swap Apps 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 Detect Face Swap Apps feature to your security template.

      1. Navigate to Build > Anti ATO tab > Deepfake Detection section in the Appdome Console.
      2. Toggle On Detect Deepfake Apps > Detect Face Swap Apps.
        Note: The checkmark feature Detect Face Swap Apps is enabled by default, as shown below. Detect Face Swap Apps option

        Figure 4: Selecting Detect Face Swap Apps

    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 Detect Face Swap Apps protection is now added to the mobile app
  3. Certify the Detect Face Swap Apps feature in Mobile Apps

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

Using Threat-Events™ for Face Swap Apps Intelligence and Control in Mobile Apps

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

The specifications and options for Threat-Events™ for Face Swap Apps are:

Threat-Event™ Elements Detect Face Swap Apps Method Detail
Appdome Feature Name Detect Face Swap Apps
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 x
Visible in ThreatScope™ x
Developer Parameters for Detecting Face Swap Apps Threat-Event™
Threat-Event NAME
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event SCORE
currentThreatEventScore Current Threat-Event score
threatEventsScore Total Threat-events score
Threat-Event Context Keys
Timestamp The exact time the threat event was triggered, recorded in milliseconds since epoch
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. Only available for Android devices.
deviceID Current device ID
reasonCode Reason code of the occurred event
deviceBrand Brand of the device
deviceBoard Board of the device
buildUser Build user
buildHost Build host
sdkVersion Sdk version
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), 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 Face Swap Apps are detected.


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


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 Face Swap Apps. 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 Face Swap Apps

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?

Deepfake Detection

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

Search Appdome Solutions

Search
Image Blog 2 Text

Device Binding in the Age of AI

For years, fraud prevention solutions have tried to use Device IDs to bind (or link) a user’s account or session to a specific device to prevent unauthorized access from other devices. However, until recently, Device IDs lacked persistence and the broad threat context needed to stop fraud and ATOs …