How to Protect Mobile Apps With Send IDAnchor on Compromise Using AI

Last updated July 31, 2025 by Appdome

This Knowledge Base article describes how to use Appdome’s AI in your CI/CD pipeline to continuously deliver plugins that Protect IDAnchor on Compromise in Mobile apps.

What is IDAnchor on Compromise?

Send IDAnchor on Compromise is an optional feature in Appdome’s IDAnchor™ suite that delivers the device’s IDAnchor value whenever a threat or attack is detected at runtime. This identity is a unique, tamper-resistant fingerprint created from deep, hard-to-alter attributes of the device and app environment.

Send IDAnchor on Compromise is designed for mobile apps that need to take immediate action when a security issue occurs. For example, if rooting, hooking frameworks, emulator use, or other forms of malicious activity are detected, the app will instantly receive the device’s IDAnchor value. This feature is especially useful in fraud response, session risk scoring, and account protection, where fast, data-driven decisions depend on having a verified device identity associated with the threat event.

How Appdome Protects Mobile Apps With Send IDAnchor on Compromise

Appdome’s dynamic Send IDAnchor on Compromise plugin automatically delivers the device’s IDAnchor value when a runtime threat or attack is detected. Developers can use this identity to assess risk, trigger custom defenses, and improve real-time fraud protection.

Below is a list of metadata that can be associated with each IDAnchor payload, true device attributes, and Advertising ID protections. Additionally, you can retrieve the IDAnchor Threat Events context keys for Android or iOS.

Payload Context Keys

immutableDeviceID	The current ID Anchor value, as calculated for the device in the session.
immutableDeviceIDDetections	Any security detections associated with the IDAnchor from the current session.
installationID	The Application Install ID; a unique ID assigned to the application installation on the device. The ID will change in case of application reinstalls or upgrades.
gsfID (*Android only)	Google Services Framework (GSF) ID — a 16-character hexadecimal identifier assigned by Google when a user logs in with a Google account on Android.
previousImmutableDeviceID	The ID Anchor value that was calculated in the previous session of the current device.
previousImmutableDeviceIDSimilarity	A similarity score (0 – 1) between the current and previous immutableDeviceID values.
releaseID	The Task ID of the Appdome build used to create this app version.
teamFingerprint	The Team ID on the Appdome platform; an identifier for the DevOps workspace/team that initiated the application fuse.

True Device Attributes Context Keys

*Relevant for both iOS and Android unless otherwise stated.

trueDeviceManufacturer	The device manufacturer, as determined and validated by Appdome.
trustDeviceManufacturer	Whether the device’s manufacturer attribute appears to be manipulated. Possible results: safe or at-risk.
trueDeviceModel	The model of the device, as determined and validated by Appdome.
trustDeviceModel	Whether the device’s model attribute appears to be manipulated. Possible results: safe or at-risk
trueOsVersion	The OS version running on the device, as determined and validated by Appdome.
trustOsVersion	Whether the OS version appears to be manipulated. Possible results: safe or at-risk.
trueSdkVersion (*Android only)	The Android SDK version on the device, as determined and validated by Appdome.
trustSdkVersion (*Android only)	Whether the reported SDK version appears to be manipulated. Possible results: safe or at-risk.

Advertising ID Protections Context Keys

trustGAID (*Android only)	Appdome’s assessment of whether the Google Advertising ID (GAID) has been tampered with. Possible results: safe or at-risk.
trustIDFA (*iOS only)	Appdome’s assessment of whether the Identifier for Advertisers (IDFA) has been tampered with. Possible results: safe or at-risk.
trustIDFV (*iOS only)	Appdome’s assessment of whether the Identifier for Vendors (IDFV) has been tampered with. Possible results: safe or at-risk.

Use the code snippets below to retrieve the desired context keys’ values.

Android:

IntentFilter intentFilter = new IntentFilter();
intentFilter.addAction("IDAnchor");

BroadcastReceiver threatEventReceiver = new BroadcastReceiver() {
    @Override
    public void onReceive(Context context, Intent intent) {
        Bundle extras = intent.getExtras();
        if (extras == null) return;

        String immutableDeviceID = extras.getString("immutableDeviceID");
        String immutableDeviceIDDetections = extras.getString("immutableDeviceIDDetections");
        String previousImmutableDeviceID = extras.getString("previousImmutableDeviceID");
        String previousImmutableDeviceIDSimilarity = extras.getString("previousImmutableDeviceIDSimilarity");
        String installationID = extras.getString("installationID");
        String releaseID = extras.getString("releaseID");
        String teamFingerprint = extras.getString("teamFingerprint");
        String gsfID = extras.getString("gsfID");

        // True Device Attributes
        String trueDeviceManufacturer = extras.getString("trueDeviceManufacturer");
        String trustDeviceManufacturer = extras.getString("trustDeviceManufacturer");
        String trueDeviceModel = extras.getString("trueDeviceModel");
        String trustDeviceModel = extras.getString("trustDeviceModel");
        String trueOsVersion = extras.getString("trueOsVersion");
        String trustOsVersion = extras.getString("trustOsVersion");
        String trueSdkVersion = extras.getString("trueSdkVersion");
        String trustSdkVersion = extras.getString("trustSdkVersion");

        // Protect Advertising IDs
        String trustGAID = extras.getString("trustGAID");

        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    }
};

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
    registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);
} else {
    registerReceiver(threatEventReceiver, intentFilter);
}

iOS:

[[NSNotificationCenter defaultCenter] addObserverForName:@"IDAnchor" object:nil queue:nil usingBlock:^(NSNotification *org_note) {
    __block NSNotification *note = org_note;
    
    dispatch_async(dispatch_get_main_queue(), ^(void) {
        
        NSString *immutableDeviceID = [[note userInfo] objectForKey:@"immutableDeviceID"];
        NSString *immutableDeviceIDDetections = [[note userInfo] objectForKey:@"immutableDeviceIDDetections"];
        NSString *previousImmutableDeviceID = [[note userInfo] objectForKey:@"previousImmutableDeviceID"];
        NSString *previousImmutableDeviceIDSimilarity = [[note userInfo] objectForKey:@"previousImmutableDeviceIDSimilarity"];
        NSString *installationID = [[note userInfo] objectForKey:@"installationID"];
        NSString *releaseID = [[note userInfo] objectForKey:@"releaseID"];
        NSString *teamFingerprint = [[note userInfo] objectForKey:@"teamFingerprint"];
        
        // True Device Attributes
        NSString *trueDeviceManufacturer = [[note userInfo] objectForKey:@"trueDeviceManufacturer"];
        NSString *trustDeviceManufacturer = [[note userInfo] objectForKey:@"trustDeviceManufacturer"];
        NSString *trueDeviceModel = [[note userInfo] objectForKey:@"trueDeviceModel"];
        NSString *trustDeviceModel = [[note userInfo] objectForKey:@"trustDeviceModel"];
        NSString *trueOsVersion = [[note userInfo] objectForKey:@"trueOsVersion"];
        NSString *trustOsVersion = [[note userInfo] objectForKey:@"trustOsVersion"];
        
        // Protect Advertising IDs
        NSString *trustIDFA = [[note userInfo] objectForKey:@"trustIDFA"];
        NSString *trustIDFV = [[note userInfo] objectForKey:@"trustIDFV"];
        
        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    });
}];

Prerequisites for Using Appdome's Send IDAnchor on Compromise Plugins:

To use Appdome’s mobile app security build system to Protect IDAnchor on Compromise , you’ll need:

Appdome account (create a free Appdome account here)
A license for Send IDAnchor on Compromise
Mobile App (.ipa for iOS, or .apk or .aab for Android)
Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)

How to Implement Protect IDAnchor on Compromise in Mobile Apps Using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Protect IDAnchor on Compromise without an SDK or gateway:

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. Send IDAnchor on Compromise is compatible with: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more.
Select the defense: Send IDAnchor on Compromise.

Create and name the Fusion Set (security template) that will contain the Send IDAnchor on Compromise feature as shown below:

Figure 1: Fusion Set that will contain the Send IDAnchor on Compromise feature

Follow the steps in Sections 2.2-2.2.2 of this article to add the Send IDAnchor on Compromise feature to your Fusion Set via the Appdome Console.

When you enable IDAnchor™ you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains Send IDAnchor on Compromise.

Figure 2: Fusion Set that displays the newly added Send IDAnchor on Compromise protection
Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

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):

Figure 3: Fusion Set Detail Summary

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:

Refer to the Appdome API Reference Guide for API building instructions.

Look for sample APIs in Appdome’s GitHub Repository.

Add the Send IDAnchor on Compromise feature to your security template.

Navigate to Build > IDAnchor tab > Android IDAnchor section in the Appdome Console.
Like all other options in ONEShield™, Send IDAnchor on Compromise is turned on by default, as shown below:
Figure 4: Selecting Send IDAnchor on Compromise
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.

Toggle On IDAnchor™ > Send IDAnchor on Compromise.

Figure 4: Selecting Protect IDAnchor on Compromise

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 Send IDAnchor on Compromise protection is now added to the mobile app

Certify the Send IDAnchor on Compromise feature in Mobile Apps

After building Send IDAnchor on Compromise, Appdome generates a Certified Secure™ certificate to guarantee that the Send IDAnchor on Compromise protection has been added and is protecting the app. To verify that the Send IDAnchor on Compromise protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below:

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 Send IDAnchor on Compromise has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Send IDAnchor on Compromise and other mobile app security features are in each build of the mobile app.

Using Threat-Events™ for IDAnchor on Compromise Intelligence and Control in Mobile Apps

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

The specifications and options for Threat-Events™ for IDAnchor on Compromise are:

Threat-Event™ Elements Protect IDAnchor on Compromise Method Detail

Appdome Feature Name Send IDAnchor on Compromise

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 Protecting IDAnchor on Compromise 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 IDAnchor on Compromise is detected.

The following is a code sample for native Mobile apps, which uses all values in the specification above for Send IDAnchor on Compromise:

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.

IntentFilter intentFilter = new IntentFilter(); intentFilter.addAction(""); BroadcastReceiver threatEventReceiver = new BroadcastReceiver() { @Override public void onReceive(Context context, Intent intent) { String message = intent.getStringExtra("message"); // Message shown to the user String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code // Current threat event score String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore"); // Total threat events score String threatEventsScore = intent.getStringExtra("threatEventsScore"); // Replace '' with your specific event context key // String variable = intent.getStringExtra(""); // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) } }; if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) { registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED); } else { registerReceiver(threatEventReceiver, intentFilter); }

xxxxxxxxxx
1
20
1
15
1
15
1
15

1
IntentFilter intentFilter = new IntentFilter();
2
intentFilter.addAction("");
3
BroadcastReceiver threatEventReceiver = new BroadcastReceiver() {
4
@Override
5
public void onReceive(Context context, Intent intent) {
6
String message = intent.getStringExtra("message"); // Message shown to the user
7
String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause
8
String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code
9

10
// Current threat event score
11
String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore");
12

13
// Total threat events score
14
String threatEventsScore = intent.getStringExtra("threatEventsScore");
15

16
// Replace '<Context Key>' with your specific event context key
17
// String variable = intent.getStringExtra("<Context Key>");
18

19
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
20
}
21
};
22

23
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
24
registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);
25
} else {
26
registerReceiver(threatEventReceiver, intentFilter);
27
}

val intentFilter = IntentFilter() intentFilter.addAction("") val threatEventReceiver = object : BroadcastReceiver() { override fun onReceive(context: Context?, intent: Intent?) { var message = intent?.getStringExtra("message") // Message shown to the user var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code // Current threat event score var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore") // Total threat events score var threatEventsScore = intent?.getStringExtra("threatEventsScore") // Replace '' with your specific event context key // var variable = intent?.getStringExtra("") // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) } } if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) { registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED) } else { registerReceiver(threatEventReceiver, intentFilter) }

xxxxxxxxxx
1
20
1
15
1
15
1
15

1
val intentFilter = IntentFilter()
2
intentFilter.addAction("")
3
val threatEventReceiver = object : BroadcastReceiver() {
4
override fun onReceive(context: Context?, intent: Intent?) {
5
var message = intent?.getStringExtra("message") // Message shown to the user
6
var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause
7
var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code
8

9
// Current threat event score
10
var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore")
11

12
// Total threat events score
13
var threatEventsScore = intent?.getStringExtra("threatEventsScore")
14

15
// Replace '<Context Key>' with your specific event context key
16
// var variable = intent?.getStringExtra("<Context Key>")
17

18
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
19
}
20
}
21

22
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
23
registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED)
24
} else {
25
registerReceiver(threatEventReceiver, intentFilter)
26
}

let center = NotificationCenter.default center.addObserver(forName: Notification.Name(""), object: nil, queue: nil) { (note) in guard let usrInf = note.userInfo else { return } let message = usrInf["message"]; // Message shown to the user let reasonData = usrInf["reasonData"]; // Threat detection cause let reasonCode = usrInf["reasonCode"]; // Event reason code // Current threat event score let currentThreatEventScore = usrInf["currentThreatEventScore"]; // Total threat events score let threatEventsScore = usrInf["threatEventsScore"]; // Replace '' with your specific event context key // let variable = usrInf[""]; // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) }

x
1
21
1
21
1
21
1
21

1
let center = NotificationCenter.default
2
center.addObserver(forName: Notification.Name(""), object: nil, queue: nil) { (note) in
3
guard let usrInf = note.userInfo else {
4
return
5
}
6

7
let message = usrInf["message"]; // Message shown to the user
8
let reasonData = usrInf["reasonData"]; // Threat detection cause
9
let reasonCode = usrInf["reasonCode"]; // Event reason code
10

11
// Current threat event score
12
let currentThreatEventScore = usrInf["currentThreatEventScore"];
13

14
// Total threat events score
15
let threatEventsScore = usrInf["threatEventsScore"];
16

17
// Replace '<Context Key>' with your specific event context key
18
// let variable = usrInf["<Context Key>"];
19

20
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
21
}

[[NSNotificationCenter defaultCenter] addObserverForName: @"" object:nil queue:nil usingBlock:^(NSNotification *org_note) { __block NSNotification *note = org_note; dispatch_async(dispatch_get_main_queue(), ^(void) { // Message shown to the user NSString *message = [[note userInfo] objectForKey:@"message"]; // Threat detection cause NSString *reasonData = [[note userInfo] objectForKey:@"reasonData"]; // Event reason code NSString *reasonCode = [[note userInfo] objectForKey:@"reasonCode"]; // Current threat event score NSString *currentThreatEventScore = [[note userInfo] objectForKey:@"currentThreatEventScore"]; // Total threat events score NSString *threatEventsScore = [[note userInfo] objectForKey:@"threatEventsScore"]; // Replace '' with your specific event context key // NSString *variable = [[note userInfo] objectForKey:@""]; // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) }); }];

xxxxxxxxxx
1
20
1
15
1
15
1
15

1
[[NSNotificationCenter defaultCenter] addObserverForName: @"" object:nil queue:nil usingBlock:^(NSNotification *org_note) {
2
__block NSNotification *note = org_note;
3
dispatch_async(dispatch_get_main_queue(), ^(void) {
4

5
// Message shown to the user
6
NSString *message = [[note userInfo] objectForKey:@"message"];
7

8
// Threat detection cause
9
NSString *reasonData = [[note userInfo] objectForKey:@"reasonData"];
10

11
// Event reason code
12
NSString *reasonCode = [[note userInfo] objectForKey:@"reasonCode"];
13

14
// Current threat event score
15
NSString *currentThreatEventScore = [[note userInfo] objectForKey:@"currentThreatEventScore"];
16

17
// Total threat events score
18
NSString *threatEventsScore = [[note userInfo] objectForKey:@"threatEventsScore"];
19

20
// Replace '<Context Key>' with your specific event context key
21
// NSString *variable = [[note userInfo] objectForKey:@"<Context Key>"];
22

23
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
24
});
25
}];

const { ADDevEvents } = NativeModules; const aDDevEvents = new NativeEventEmitter(ADDevEvents); function registerToDevEvent(action, callback) { NativeModules.ADDevEvents.registerForDevEvent(action); aDDevEvents.addListener(action, callback); } export function registerToAllEvents() { registerToDevEvent( "", (userinfo) => Alert.alert(JSON.stringify(userinfo)) var message = userinfo["message"] // Message shown to the user var reasonData = userinfo["reasonData"] // Threat detection cause var reasonCode = userinfo["reasonCode"] // Event reason code // Current threat event score var currentThreatEventScore = userinfo["currentThreatEventScore"] // Total threat events score var threatEventsScore = userinfo["threatEventsScore"] // Replace '' with your specific event context key // var variable = userinfo[""] // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) ); }

xxxxxxxxxx
1
20
1
15
1
15
1
15
2
29

1
const { ADDevEvents } = NativeModules;
2
const aDDevEvents = new NativeEventEmitter(ADDevEvents);
3

4
function registerToDevEvent(action, callback) {
5
NativeModules.ADDevEvents.registerForDevEvent(action);
6
aDDevEvents.addListener(action, callback);
7
}
8

9
export function registerToAllEvents() {
10
registerToDevEvent(
11
"",
12
(userinfo) => Alert.alert(JSON.stringify(userinfo))
13

14
var message = userinfo["message"] // Message shown to the user
15
var reasonData = userinfo["reasonData"] // Threat detection cause
16
var reasonCode = userinfo["reasonCode"] // Event reason code
17

18
// Current threat event score
19
var currentThreatEventScore = userinfo["currentThreatEventScore"]
20

21
// Total threat events score
22
var threatEventsScore = userinfo["threatEventsScore"]
23

24
// Replace '<Context Key>' with your specific event context key
25
// var variable = userinfo["<Context Key>"]
26

27
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
28
);
29
}

RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("")); class ThreatEventReceiver : BroadcastReceiver { public override void OnReceive(Context context, Intent intent) { String message = intent.GetStringExtra("message"); // Message shown to the user String reasonData = intent.GetStringExtra("reasonData"); // Threat detection cause String reasonCode = intent.GetStringExtra("reasonCode"); // Event reason code // Current threat event score String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore"); // Total threat events score String threatEventsScore = intent.GetStringExtra("threatEventsScore"); // Replace '' with your specific event context key // String variable = intent.GetStringExtra(""); // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) } }

x
27

1
RegisterReceiver(new ThreatEventReceiver(), new IntentFilter(""));
2

3
class ThreatEventReceiver : BroadcastReceiver
4
{
5
public override void OnReceive(Context context, Intent intent)
6
{
7
// Message shown to the user
8
String message = intent.GetStringExtra("message");
9

10
// Threat detection cause
11
String reasonData = intent.GetStringExtra("reasonData");
12

13
// Event reason code
14
String reasonCode = intent.GetStringExtra("reasonCode");
15

16
// Current threat event score
17
String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore");
18

19
// Total threat events score
20
String threatEventsScore = intent.GetStringExtra("threatEventsScore");
21

22
// Replace '<Context Key>' with your specific event context key
23
// String variable = intent.GetStringExtra("<Context Key>");
24

25
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
26
}
27
}

NSNotificationCenter.DefaultCenter.AddObserver( (NSString)"", // Threat-Event Identifier delegate (NSNotification notification) { // Message shown to the user var message = notification.UserInfo.ObjectForKey("message"); // Threat detection cause var reasonData = notification.UserInfo.ObjectForKey("reasonData"); // Event reason code var reasonCode = notification.UserInfo.ObjectForKey("reasonCode"); // Current threat event score var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore"); // Total threat events score var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore"); // Replace '' with your specific event context key // var variable = notification.UserInfo.ObjectForKey(""); // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) } );

x

1
NSNotificationCenter.DefaultCenter.AddObserver(
2
(NSString)"", // Threat-Event Identifier
3
delegate (NSNotification notification)
4
{
5
// Message shown to the user
6
var message = notification.UserInfo.ObjectForKey("message");
7

8
// Threat detection cause
9
var reasonData = notification.UserInfo.ObjectForKey("reasonData");
10

11
// Event reason code
12
var reasonCode = notification.UserInfo.ObjectForKey("reasonCode");
13

14
// Current threat event score
15
var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore");
16

17
// Total threat events score
18
var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore");
19

20
// Replace '<Context Key>' with your specific event context key
21
// var variable = notification.UserInfo.ObjectForKey("<Context Keys>");
22

23
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
24
}
25
);

window.broadcaster.addEventListener("", function(userInfo) { var message = userInfo.message // Message shown to the user var reasonData = userInfo.reasonData // Threat detection cause var reasonCode = userInfo.reasonCode // Event reason code // Current threat event score var currentThreatEventScore = userInfo.currentThreatEventScore // Total threat events score var threatEventsScore = userInfo.threatEventsScore // Replace '' with your specific event context key // var variable = userInfo. // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) });

xxxxxxxxxx
1
20
1
15
1
15
1
15
2
29

1
window.broadcaster.addEventListener("", function(userInfo) {
2
var message = userInfo.message // Message shown to the user
3
var reasonData = userInfo.reasonData // Threat detection cause
4
var reasonCode = userInfo.reasonCode // Event reason code
5

6
// Current threat event score
7
var currentThreatEventScore = userInfo.currentThreatEventScore
8

9
// Total threat events score
10
var threatEventsScore = userInfo.threatEventsScore
11

12
// Replace '<Context Key>' with your specific event context key
13
// var variable = userInfo.<Context Keys>
14

15
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
16
});

import 'dart:async'; import 'package:flutter/material.dart'; import 'package:flutter/services.dart'; class PlatformChannel extends StatefulWidget { const PlatformChannel({super.key}); @override State createState() => _PlatformChannelState(); } class _PlatformChannelState extends State { // Replace with your EventChannel name static const String _eventChannelName = ""; static const EventChannel _eventChannel = EventChannel(_eventChannelName); @override void initState() { super.initState(); _eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError); } void _onEvent(Object? event) { setState(() { // Adapt this section based on your specific event data structure var eventData = event as Map; // Example: Accessing 'externalID' field from the event var externalID = eventData['externalID']; // Customize the rest of the fields based on your event structure String message = eventData['message']; // Message shown to the user String reasonData = eventData['reasonData']; // Threat detection cause String reasonCode = eventData['reasonCode']; // Event reason code // Current threat event score String currentThreatEventScore = eventData['currentThreatEventScore']; // Total threat events score String threatEventsScore = eventData['threatEventsScore']; // Replace '' with your specific event context key // String variable = eventData['']; }); } // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) }

x

1
import 'dart:async';
2
import 'package:flutter/material.dart';
3
import 'package:flutter/services.dart';
4

5
class PlatformChannel extends StatefulWidget {
6
const PlatformChannel({super.key});
7

8
@override
9
State<PlatformChannel> createState() => _PlatformChannelState();
10
}
11

12
class _PlatformChannelState extends State<PlatformChannel> {
13
// Replace with your EventChannel name
14
static const String _eventChannelName = "";
15
static const EventChannel _eventChannel = EventChannel(_eventChannelName);
16

17
@override
18
void initState() {
19
super.initState();
20
_eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError);
21
}
22

23
void _onEvent(Object? event) {
24
setState(() {
25
// Adapt this section based on your specific event data structure
26
var eventData = event as Map;
27

28
// Example: Accessing 'externalID' field from the event
29
var externalID = eventData['externalID'];
30

31
// Customize the rest of the fields based on your event structure
32
String message = eventData['message']; // Message shown to the user
33
String reasonData = eventData['reasonData']; // Threat detection cause
34
String reasonCode = eventData['reasonCode']; // Event reason code
35

36
// Current threat event score
37
String currentThreatEventScore = eventData['currentThreatEventScore'];
38

39
// Total threat events score
40
String threatEventsScore = eventData['threatEventsScore'];
41

42
// Replace '<Context Key>' with your specific event context key
43
// String variable = eventData['<Context Keys>'];
44
});
45
}
46

47
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
48
}

Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Send IDAnchor on Compromise. 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 Send IDAnchor on Compromise

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:

Customizing, Configuring & Branding Secure Mobile Apps.

Deploying/Publishing Secure mobile apps to Public or Private app stores.

Releasing Secured Android & iOS Apps built on Appdome.

Related Articles:

How to Protect iOS Apps With IDAnchor Using AI

How to Protect Android Apps With IDAnchor Using AI

How to Protect Mobile Apps With Mobile Device ID Using AI

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.

How to Protect Mobile Apps With Send IDAnchor on Compromise Using AI

What is IDAnchor on Compromise?

How Appdome Protects Mobile Apps With Send IDAnchor on Compromise

Prerequisites for Using Appdome's Send IDAnchor on Compromise Plugins:

How to Implement Protect IDAnchor on Compromise in Mobile Apps Using Appdome

Designate the Mobile App to be protected.

Upload an app via the Appdome Mobile Defense platform GUI or via Appdome’s DEV-API or CI/CD Plugins.

Select the defense: Send IDAnchor on Compromise.

Add the Send IDAnchor on Compromise feature to your security template.

Certify the Send IDAnchor on Compromise feature in Mobile Apps

Using Threat-Events™ for IDAnchor on Compromise Intelligence and Control in Mobile Apps

Related Articles:

How Do I Learn More?

Thank you!

Device Binding in the Age of AI

How Persistent Mobile Identity Delivers Stronger API Protection

How App & Install Binding Stop Social Engineering in Mobile Apps

Eliminating Mobile Ad Fraud with IDAnchor™

Threat-Event™ Elements	Protect IDAnchor on Compromise Method Detail
Appdome Feature Name	Send IDAnchor on Compromise
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 Protecting IDAnchor on Compromise 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.