Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Objection wraps Frida in a command-driven interface, so common mobile testing tasks such as disabling certificate pinning or dumping the keychain take one command instead of a script.

What Is Objection?
Objection is a runtime mobile exploration toolkit built by Sensepost. It sits on top of Frida and packages the instrumentation that mobile testers write repeatedly into ready-made commands. Where a Frida script to defeat certificate pinning might run to a hundred lines and need maintaining across platform versions, Objection does it with one command that works across most implementations.
Calling it a wrapper undersells it in practice. It turns an afternoon of script writing into a few minutes of exploration, which changes how much of an assessment budget goes on setup rather than on finding problems.
Objection presents an interactive shell against a running application. The commands that matter in nearly every assessment:
The patchapk and patchipa commands repackage an application with the Frida Gadget library embedded, so instrumentation works on a device that has not been rooted or jailbroken. The application is unpacked, the library inserted, a loading hook added, and the package resigned with a test certificate.
This matters more than it sounds. Current Android and iOS versions are harder to root and jailbreak than they used to be, test devices on current platform versions are often unavailable, and some applications refuse to run at all on a compromised device. Patching sidesteps all three.
The trade-off is that resigning breaks anything tied to the original signature: platform attestation, app-specific entitlements, and some backend checks that verify the signing certificate. Findings from a patched application need that caveat recorded.
Objection exists because the same client-side protections are implemented the same way in thousands of applications, which makes them bypassable by a shared script. Three conclusions follow.
Client-side checks are signals, not controls. Root detection, pinning, and tamper checks raise the cost of attacking an application on a device the attacker owns. None of them prevents it. Anything security-critical belongs on the server.
Stock implementations are bypassed first. Objection targets the common libraries and the documented APIs, because that is what most applications use. A custom implementation, obfuscated and varied between releases, takes meaningfully longer to defeat. This is not security through obscurity in the pejorative sense; it is raising cost, which is the honest objective of the whole MASVS-RESILIENCE control group.
Do not announce the detection. An application that exits with a message naming the problem tells the tester exactly which check to disable next. Report the signal to the server, let the server decide, and degrade functionality quietly.
Beyond resilience, the findings Objection surfaces most often are storage problems: authentication tokens in plain preferences, personal data in an unencrypted local database, keychain entries accessible when the device is locked, and secrets left in memory far longer than needed. Those are fixable properly, by using the platform keystore and Secure Enclave, keeping sensitive data off the device where possible, and clearing it when it is no longer required. See mobile data leakage.
At Privia Security, our Mobile Application Security Services test how your application behaves once its client-side defences have been removed, which is the condition it will eventually face.
Frida is the instrumentation engine that injects a JavaScript runtime into a process and lets you hook anything. Objection is a toolkit built on it that packages the scripts mobile testers write repeatedly into single commands: disable pinning, dump the keychain, list the sandbox, hook a class. Use Objection for the common tasks and write Frida scripts for anything specific.
Yes. The patchapk and patchipa commands repackage the application with the Frida Gadget library embedded, so instrumentation works on an unmodified device. The application has to be resigned with a test certificate, which breaks anything tied to the original signature, including platform attestation and some backend certificate checks. Record that caveat alongside the findings.
Because without it the application’s traffic cannot be routed through an intercepting proxy, and the entire network and API layer stays invisible. Since the backend API is usually where the most serious findings are, an assessment that cannot see the traffic is severely limited. Pinning still protects users against network attackers; it does not resist someone controlling the device.
Treat client-side checks as signals rather than controls, and put security-critical decisions on the server. Use platform attestation such as Play Integrity or App Attest, validated server-side. Implement resilience checks with custom code rather than stock library calls, obfuscate them, vary them between releases, and report detection quietly to the server instead of displaying a message.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.