All use cases

App tampering

Detect modified, repackaged, or instrumented builds of your mobile app that run on compromised devices and lie to your backend.

Overview

App tampering is when an attacker modifies your mobile app's code or runtime behavior so it actively misrepresents itself to your backend. This ranges from repackaging, where the app is decompiled, altered, re-signed, and redistributed (sometimes as a trojanized clone laced with malware), to live instrumentation that rewrites methods in memory while the genuine app runs. Because the request still originates from something that looks like your app, network-level and account-level checks tend to wave it through.

The durable defenses sit in the build and the backend: code obfuscation and integrity checks raise the cost of modifying the app, certificate pinning resists interception, and the server treats any client-asserted value as untrusted until verified. Device intelligence contributes the runtime evidence that the environment or the app has been compromised. Developer Tools Detection flags production devices with active debugging features which are common in repackaging workflows. Frida Detection flags dynamic instrumentation hooking a running app, and Rooted and Jailbroken Device Detection surface the privileged environments most tampering depends on. MitM Attack Detection flags when requests to Fingerprint servers may have been intercepted or modified, so you know when to distrust other device signals on that session. The persistent Visitor ID ties tampered traffic back to the device behind it across attempts. Confirm that the Visitor IDs your backend receives match what the client originally produced rather than a locally forged value.

App tampering threatens any organization with a mobile app tied to money or trust, especially fintech and banking, gaming, and ecommerce, plus media apps protecting licensed content. The fallout includes forged transactions and entitlements, exfiltrated secrets and logic, malware-laced clones that damage your brand, and fraud that passes silently because the request looked legitimate. Treat detected tampering as a trigger to reject the request, invalidate the session, and route the device for review.

How to implement it

  • Use Frida Detection alongside Developer Tools Detection to catch dynamic instrumentation rewriting your app at runtime, a core technique for making a genuine app lie to your backend.

  • Use Rooted and Jailbroken Device Detection to flag the privileged environments most repackaging and instrumentation depend on, and step up verification from them.

  • Use MitM Attack Detection to flag when requests to Fingerprint servers may have been intercepted or modified, and reject or step up when you cannot trust the device signals on that session.

  • Validate that the Visitor ID your backend receives matches what the client produced, and use Android Emulator, iOS Simulator, and Factory Reset Detection to link tampered traffic across disposable environments.

  • Use Tampered Request Detection to flag identification requests whose payload was modified in transit, a sign the attacker is manipulating the SDK call itself rather than just the device environment.

Also known as

app tampering · app repackaging · repackaged app · modified app · app modification · trojanized app · re-signed app · runtime tampering · app integrity · tampered request · app cloning malware · mobile app manipulation

Ready to identify?

Start building with a free trial or speak to an expert to explore our Enterprise plan.