79% vs 51%: independent neobanks lag on app security. Read the report

Product

Product

Introducing Mobile ADR: Protect a Mobile App Without Touching Its Code

Ostorlab is launching Mobile ADR, Mobile Application Detection & Response. Upload the APK, AAB or IPA you would publish, download a copy protected with RASP, and see the checks each install reports: rooted and jailbroken devices, debuggers, Frida and other hooks, emulators, app cloning, code integrity and network interception. No source code and no SDK.

Mobile ADR (Mobile Application Detection & Response) adds RASP to a copy of the mobile app you already built, with no source code and no SDK, and shows what its installs observe on the device: rooted phones, debuggers, Frida, cloning apps, VPNs and proxies.

A mobile app ships to devices you don't control. Some are rooted or jailbroken. Some run a debugger, Frida, or a cloning app that wraps your app inside another one. Some route every request through a proxy. An app that ships without protection can't see any of it, and neither can you.

The usual answer is a shielding SDK: add it to the code, rebuild, and hope the integration survives the next release. We test that kind of protection with Mobile Shielding Scan, and we keep seeing checks that detect a threat and then do nothing with it. The app knows; the team that owns it doesn't.

So we built Mobile ADR, Mobile Application Detection & Response.

Two questions it answers

  1. How do I protect an app I've already built? Upload it. Mobile ADR adds RASP (runtime application self-protection) to a copy of the app, without the source code and without an SDK. You sign the protected copy and publish it as usual.
  2. What is happening on the devices running it? Every install runs the RASP checks when the app starts and then about every minute, and reports what it finds. The Mobile ADR page shows each protected app, its builds and the events its installs report.

What's different about Mobile ADR

  • No code changes. It takes the APK, AAB or IPA you would publish. There is no SDK integration to maintain in your app’s source code. One thing does change on Android: the protected copy needs Android 12 or later, because Mobile ADR raises the app's minimum version, so it won't install on older devices.
  • You choose what runs. All the checks are on by default; turn off the ones that don't fit your users, for example the VPN check for an app whose users all go through a company VPN.
  • Signals you can act on. Each event says which check ran, what it observed and which build reported it, for example a Frida library loaded in the app's memory.
  • Open code inside your app. The runtime that runs on your users' devices is open source under Apache-2.0. Your security team can read it and build it.

What the checks cover

Area What the RASP checks look for
Rooted and jailbroken devices Root and jailbreak files, mounts and system properties; on iOS, whether the app can act outside its sandbox
Debuggers A tracer attached to the app's process
Frida and other hooks Instrumentation libraries in memory, injected libraries, Frida's default port on iOS, writable and executable memory
App cloning and virtualization The app running under another package, user or container than its own
Emulators and simulators Emulator properties on Android, the simulator on iOS
Code integrity The runtime's own code changed in memory (Android)
Network interception VPN tunnels; on iOS, system proxies

Platforms: Android 12 and later, on every Android CPU architecture, and iOS 12 and later. On Android, Mobile ADR also encrypts the app's own code in the protected copy.

Android and iOS installs both report to Mobile ADR.

How it works

  1. In the Ostorlab web app, open Protect → Mobile ADR and select Protect an app.
  2. Upload the APK, AAB or IPA.
  3. Choose the checks the protected app runs. They are all on by default.
  4. Mobile ADR adds RASP to a copy and builds it. Download the protected copy, sign it, and publish it.
  5. As people use the app, its installs report their checks. They appear in the Events tab, with the app and the build each one came from.

What it doesn't do yet

Mobile ADR is new. Today it detects and reports: it doesn't score events or send alerts. You see the facts each install reports and decide what they mean for your app. If you run another RASP product and want its events in one place, talk to us.

Protect your first app

Open Mobile ADR and upload a build.