How to Configure Obfuscation in Mobile Apps by Excluding Web Assets

Last updated August 11, 2025 by Appdome

This Knowledge Base article describes how to use Appdome’s AI in your CI/CD pipeline to continuously deliver plugins that Use Exclude Web Assets in Mobile apps.

What is Exclude Web Assets?

Exclude Web Assets is an optional plugin for Non-Native Code Obfuscation that allows mobile developers to exclude specific web-related files—such as .html, .js, and .css—from the obfuscation process. This gives developers more control over which assets are protected versus which remain in clear text for debugging, accessibility, or functional needs. In hybrid apps built with frameworks like Cordova or React Native, certain scripts or stylesheets may need to remain readable for runtime injection, developer inspection, or external access. However, selectively excluding these assets carries risk, as any unobfuscated file can expose app logic or behavior to reverse engineering. This makes Exclude Web Assets valuable in fine-tuning the security posture without impeding development, while also helping to meet compliance requirements, such as OWASP MASVS code integrity standards.

How Appdome Configures Obfuscation by Excluding Web Assets

Appdome’s dynamic Exclude Web Assets plugin gives developers the option to leave .html, .js, and .css files unobfuscated. This is useful when specific scripts or styles must remain accessible or human-readable for debugging or runtime use. When enabled, only the selected web assets are excluded, while all other non-native files remain protected by default. This ensures targeted obfuscation while preserving essential dev workflows.

Prerequisites for Using Appdome's Exclude Web Assets Plugins:

To use Appdome’s mobile app security build system to Use Exclude Web Assets , you’ll need:

How to Implement Use Exclude Web Assets in Mobile Apps Using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Use Exclude Web Assets 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. Exclude Web Assets is compatible with: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more.
  2. Select the defense: Exclude Web Assets.

      1. Create and name the Fusion Set (security template) that will contain the Exclude Web Assets feature as shown below:
        fusion set that contains Exclude Web Assets

        Figure 1: Fusion Set that will contain the Exclude Web Assets feature

      2. Follow the steps in Sections 2.2-2.2.2 of this article to add the Exclude Web Assets feature to your Fusion Set via the Appdome Console.

      3. When you enable Non-Native Code Obfuscation you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains Exclude Web Assets.

        Fusion Set applied Exclude Web Assets

        Figure 2: Fusion Set that displays the newly added Exclude Web Assets 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 Exclude Web Assets feature to your security template.

      1. Navigate to Build > Security tab > TOTALCode™ Obfuscation section in the Appdome Console.
      2. Toggle On Non-Native Code Obfuscation > Exclude Web Assets.
        Exclude Web Assets option

        Figure 4: Selecting Use Exclude Web Assets

    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 Exclude Web Assets protection is now added to the mobile app
  3. Certify the Exclude Web Assets feature in Mobile Apps

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

Using Threat-Events™ for Exclude Web Assets Intelligence and Control in Mobile Apps

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

The specifications and options for Threat-Events™ for Exclude Web Assets are:

Threat-Event™ Elements Use Exclude Web Assets Method Detail
Appdome Feature Name Exclude Web Assets
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 Using Exclude Web Assets 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 Exclude Web Assets is detected.


The following is a code sample for native Mobile apps, which uses all values in the specification above for Exclude Web Assets:


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 Exclude Web Assets. 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 Exclude Web Assets

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 Code Obfuscation

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 …