Promon Shield for Mobile

Applies name and control-flow obfuscation, string and resource encryption, code virtualization and white-box cryptography to make reverse engineering harder, so an attacker cannot lift intellectual property or embedded credentials out of the application or clone it.

Instruments runtimes to intercept database queries, command execution, and deserialization across Java, .NET, Python, Node.js, PHP, Ruby, and Go, with coverage depth varying by product.

Detects compromised runtime environments at startup and during execution, including rooted Android devices, jailbroken iOS devices, emulators, and attached debuggers, and reacts per policy when an untrusted environment is found.

Verifies the integrity of application code, resources, and the execution environment at runtime, detecting repackaging, method hooking, and dynamic instrumentation such as Frida, and triggering a defensive response when tampering is detected.

Operate in monitor-only mode (log and alert), or active blocking mode (terminate request upon detection). Most deployments begin in monitor mode to establish a false positive baseline before enabling blocking.

Performs in-process interception and threat analysis with minimal latency impact, keeping the agent viable in production workloads with overhead varying by product.

Protects AI models and inference logic embedded in the application from tampering, extraction, and manipulation at runtime, preserving the integrity of on-device AI features.

Encrypts and isolates secrets, tokens, and sensitive assets stored inside the protected application so data remains inaccessible even on rooted or jailbroken devices, using in-app key protection such as whitebox cryptography.

Detects other applications and services on the device that are being used to defraud the user mid-session, such as accessibility-service overlays, screen readers and remote assistance or screen-sharing tools, and restricts their access while the protected app is in the foreground.