What it is
Android isolates every app in its own space: no app can read another app’s files or change the operating system. That isolation holds because, during normal use, nobody has system administrator rights, which Linux calls the root user. Not even the person who owns the phone.
Rooting a phone means obtaining that access. It usually involves unlocking the bootloader, modifying the image the system boots from and installing a manager that decides which apps get administrator rights. From then on, any authorized program can read the memory and data of other apps, intercept what they do and change how the system behaves.
Plenty of people root their phones for legitimate reasons: to customize them, remove preinstalled apps or install a different version of Android. The problem is not the person but what that environment allows. On a rooted phone, the security guarantees you designed your app around are no longer assured.
Why it matters
Your app relies on the operating system for several things: that its files stay private, that nobody else reads its memory, that the keystore protects its secrets and that the code running is the code you shipped. With root, any of those guarantees can break without your app noticing.
For someone who wants to attack an app, a rooted phone is the ideal test bench. From there they can:
- read the databases, preferences and temporary files your app keeps on the phone;
- run tools that inject themselves into your app to observe it or change its logic while it runs (we explain this in hooking and instrumentation);
- hide the root itself from apps that look for it;
- automate operations at scale with accounts created for fraud.
That is why, in banking, healthcare or commerce, knowing that your app is running on a rooted phone changes how you should treat that session. You may want to ask for an extra check, limit the most sensitive operations or, at the very least, leave a record for your fraud team.
What Pulse does
Pulse detects signals associated with root on Android while the application runs. These signals support configured responses and provide investigation context, without assuming that every person using a modified device is committing fraud.
How it responds
The policy can record the signal, notify the application or trigger termination, where the response is applicable. Actions such as requesting additional verification, restricting an operation or protecting content require implementation in your application.
Local detection and response can work offline. Pending reports are sent when connectivity returns; the console shows the data it receives. History should not be interpreted as a guaranteed record of all device activity.
Before applying restrictions in production, assess detections on the devices and versions used by your organization. Observation mode supports investigating signals and potential false positives without enabling their restrictive response. Define separate policies for development, testing and production.
Scope and limitations
- Limited coverage. Detection cannot guarantee identification of every root variant or concealment technique.
- Protection scope. Pulse does not manage the phone or prevent its owner from modifying it.
- Legitimate use. A rooted device does not establish fraud. Responses must account for affected flows and legitimate users.
- Backend controls. Payment authorization and other critical decisions must remain on the server.