Data storage and privacy
- Keychain, Keystore, shared preferences and local databases
- Tokens and personal data in logs, caches and backups
- Data shared with third-party SDKs
- Clipboard, screenshots and background snapshots
Stingrai's penetration testers test iOS and Android applications the way real adversaries do: reverse engineering the binary, instrumenting the app at runtime, bypassing SSL pinning and jailbreak or root detection, and testing the backend API the app relies on. The methodology is aligned to OWASP MASVS and MASTG.


Mobile applications run on devices you do not control. Every IPA and APK you release can be downloaded, decompiled, instrumented and replayed against your backend. Mobile application penetration testing identifies the weaknesses that expose your users and your API before they are exploited by an attacker in control of the device.
Our team tests the iOS binary, the Android binary and the backend API as a single engagement, and delivers a detailed report with a reproducible proof of concept, a severity rating and clear remediation guidance for each finding.
By completing this assessment, you significantly reduce your risk of:
Session tokens, credentials and personal data leaking from local storage, logs or backups
Hardcoded API keys and secrets extracted from the shipped binary
SSL pinning and jailbreak or root detection being bypassed to tamper with traffic
Broken authorization (IDOR) and business logic abuse on the backend API
Exported components, deep links and WebViews abused by malicious applications on the same device
iOS Application Testing
Static and dynamic analysis of the IPA: Keychain and local data storage, App Transport Security and certificate pinning, jailbreak detection, Swift and Objective-C runtime instrumentation with Frida and Objection, URL schemes, universal links, WebViews and third-party SDK behavior.
Android Application Testing
Decompilation and instrumentation of the APK: Keystore and shared preferences, network security configuration and pinning, root detection and anti-tamper controls, exported activities, services, content providers and broadcast receivers, deep links, WebViews and intent handling.
Backend API Testing
The REST or GraphQL API behind the application, where the highest-impact vulnerabilities are typically found: authentication and session management, broken object and function level authorization (IDOR), business logic abuse, rate limiting and input validation across every user role.
Static and Binary Analysis
Reverse engineering of the IPA and APK to recover application logic, secrets and hardcoded endpoints.
MASVS-STORAGE and MASVS-CRYPTO checks: data at rest, Keychain and Keystore usage, weak or misused cryptography.
MASVS-CODE and MASVS-PLATFORM checks: build hardening, vulnerable SDKs, exported components and inter-process communication.
Dynamic and Runtime Analysis
Instrumentation with Frida and Objection on jailbroken and rooted devices to observe and modify the application while it runs.
MASVS-NETWORK and MASVS-AUTH checks: transport security, session management, biometric and local authentication bypass.
Traffic interception and replay against the backend API, including authorization and business logic abuse.
Resilience and Bypass Resistance
SSL pinning bypass attempts using runtime instrumentation, repackaging and trust store manipulation.
MASVS-RESILIENCE checks: jailbreak and root detection, anti-debugging, anti-tamper and emulator detection bypass attempts.
MASVS-PRIVACY review of the data the application collects, shares with SDKs and exposes to the platform.
Mobile engagements are human-led and cover both the app on the device and the backend it calls. Exact coverage is confirmed at scoping and stated in the MASVS coverage matrix.
Testing combines static analysis of the IPA and APK with dynamic analysis on jailbroken and rooted devices, using Frida and objection to instrument the running app, intercept its traffic and test the controls it relies on.
Engagements are black-box (store build only), grey-box (test accounts for each role) or white-box (source code and build configuration). Grey-box is the common choice, because most high-impact mobile findings sit in the backend API behind authenticated roles.
Mobile engagements are human-led. The backend API the app calls is tested by the same penetration testers in the same engagement.
Evidence for customers and auditors, priorities for leadership and fix-ready detail for mobile and backend teams.
For engineering
Each finding is posted as soon as it is confirmed, with a proof of concept, the platform affected, severity and remediation guidance.
For leadership
A plain-language view of risk to users and data, and the fixes to prioritize first.
For security teams
Methodology, a MASVS coverage matrix per platform and every finding with reproduction steps, as a redactable PDF.
For engineering
Fixed findings are retested on request against the new build, and their status is updated in the portal and the report.
For customers and auditors
Issued with every human-led mobile engagement, stating scope and testing dates, ready to share.
For the project team
Jira, Slack and GitHub integration, and direct chat with the assigned penetration testers throughout the test.
Explore how we structure executive summaries, prioritized findings, evidence, reproduction steps, and remediation guidance, tailored to SOC 2, ISO 27001, PCI DSS, and HIPAA compliance.
PDF, 4 MB. No email address required.
Typical durations. The schedule for each engagement is fixed in writing at scoping.
Mobile engagements are quoted to scope; there is no package price. These factors set the number of testing days:
Submit the Get a Quote form and receive pricing within 24 hours. Every quote includes the retest. Market ranges and quote comparisons are in the mobile app penetration testing cost guide.
One mobile penetration test and its retest results produce evidence for several programs at once.
CREST-Accredited Firm
Stingrai Inc. is a CREST-accredited penetration testing provider, founded in Toronto in 2021 with an office in London. The company itself is accredited by CREST for Penetration Testing and for AI-Enabled Penetration Testing, which assesses its responsible use of AI in testing.
Named Penetration Testers
Every mobile engagement is human-led by two named penetration testers from a team holding OSCE³, OSWE, OSEP, CREST CRT and CISSP certifications, including a founding member of Uber's offensive security team with 15 years in web, mobile and LLM testing.
Published Mobile Research
Stingrai publishes its own mobile security research, including a complete SSL pinning bypass walkthrough, and its researchers have published 18 CVEs.
Binary, Runtime and Backend
The iOS binary, the Android binary and the backend API are tested by the same penetration testers in one engagement, so a weakness on the device can be followed to the data it exposes on the server.
One-Time or Continuous
A one-time mobile penetration test fits an audit, a launch or a major release; a continuous program tests every significant build. Many clients begin with a one-time assessment and move to a continuous program.
Rated 5.0 on Clutch
Stingrai holds a 5.0 rating across 20 verified Clutch reviews and 4.9 on G2, from clients ranging from startups to enterprises in healthcare, financial services and SaaS.
Our mobile penetration tests cover the binary, the runtime and the backend API in a single engagement, aligned to OWASP MASVS and MASTG. Every finding includes a working proof of concept, remediation guidance and a complimentary retest, delivered as a one-time assessment or a continuous program.