What it is
Hooking means intercepting a function, in your app or in the system, to see the data it receives or change the result it returns. Instrumentation goes one step further: tools that inject themselves into your app’s process and let someone, while it runs, read its memory, call its functions or rewrite its logic. Attaching a debugger is the most basic form of the same thing: pausing the app, inspecting it and changing values by hand.
These tools have legitimate uses in security research and testing. They can also be used to prepare attacks: skipping a check, capturing keys or tokens, disabling certificate validation or changing the amount of a transaction.
Why it matters
Instrumentation is dangerous because it does not need to modify your app’s package or re-sign it. The change happens in memory, on the phone, while the app runs. That is why static protections, such as package signing or code obfuscation, do not see it: the installed file is still intact.
The same tools can also be turned against the protection itself. A well-placed hook can make a security check always return “all clear”. Whoever protects an app has to watch both for outside threats and for attempts to blind its own detectors.
It is often paired with a rooted or jailbroken phone, but not always: someone can repackage your app with the tool bundled inside and run it on an unmodified phone.
What Pulse does
Pulse detects signs of debugging, hooking and instrumentation on Android and iOS. Coverage depends on the platform and SDK version. The application can handle detections according to the configured policy, while security teams investigate received reports.
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
- New or adapted techniques. Detection of every tool or prevention of all tampering is not guaranteed.
- Development environments. Authorized testing may use debugging and instrumentation. Policies must distinguish testing from production.
- Operation protection. Detecting a signal does not guarantee that an operation has already been blocked. Additional actions require application and backend integration.
- Defense in depth. Pulse complements server controls; it does not replace validation of sensitive operations.