main logo icon

Mobile Application Penetration Testing

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 Application Penetration Testing
ellipse

Our Approach to Mobile Application Penetration Testing

ellipse

Step 1

Scoping and Threat Modeling

We confirm the platforms, builds and backend environments in scope, the user roles and entitlements to test, and whether the engagement is black box (IPA and APK only), gray box (test accounts per role) or white box (source code and build configuration). Rules of engagement and test devices are agreed before testing begins.

Benefits of Mobile Application Penetration Testing

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:

check icon

Session tokens, credentials and personal data leaking from local storage, logs or backups

check icon

Hardcoded API keys and secrets extracted from the shipped binary

check icon

SSL pinning and jailbreak or root detection being bypassed to tamper with traffic

check icon

Broken authorization (IDOR) and business logic abuse on the backend API

check icon

Exported components, deep links and WebViews abused by malicious applications on the same device

What Our Mobile Penetration Test Covers

iOS Application Testing

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

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

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.

OWASP MASVS and MASTG Aligned Methodology

Static and Binary Analysis

Static and Binary Analysis

  • check icon

    Reverse engineering of the IPA and APK to recover application logic, secrets and hardcoded endpoints.

  • check icon

    MASVS-STORAGE and MASVS-CRYPTO checks: data at rest, Keychain and Keystore usage, weak or misused cryptography.

  • check icon

    MASVS-CODE and MASVS-PLATFORM checks: build hardening, vulnerable SDKs, exported components and inter-process communication.

Dynamic and Runtime Analysis

Dynamic and Runtime Analysis

  • check icon

    Instrumentation with Frida and Objection on jailbroken and rooted devices to observe and modify the application while it runs.

  • check icon

    MASVS-NETWORK and MASVS-AUTH checks: transport security, session management, biometric and local authentication bypass.

  • check icon

    Traffic interception and replay against the backend API, including authorization and business logic abuse.

Resilience and Bypass Resistance

Resilience and Bypass Resistance

  • check icon

    SSL pinning bypass attempts using runtime instrumentation, repackaging and trust store manipulation.

  • check icon

    MASVS-RESILIENCE checks: jailbreak and root detection, anti-debugging, anti-tamper and emulator detection bypass attempts.

  • check icon

    MASVS-PRIVACY review of the data the application collects, shares with SDKs and exposes to the platform.

What Stingrai tests in a mobile application

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.

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

Network and transport

  • TLS configuration and App Transport Security
  • Certificate pinning and its bypass resistance
  • Android network security configuration
  • Cleartext traffic and insecure endpoints

Authentication and session

  • Login, token storage and refresh
  • Biometric and local authentication bypass
  • Session expiry and logout on the device and the server
  • OAuth and deep link sign-in flows

Platform interaction

  • Exported activities, services, content providers and receivers
  • URL schemes, universal links and deep links
  • WebViews and JavaScript bridges
  • Intents and inter-process communication

Code, binary and resilience

  • Hardcoded keys, secrets and endpoints in the binary
  • Vulnerable SDKs and build hardening
  • Jailbreak and root detection bypass
  • Anti-tamper, anti-debugging and repackaging

Backend API

  • Authentication and authorization on every endpoint the app calls
  • BOLA and IDOR across user roles
  • Business logic and rate limiting
  • Injection and server-side input handling

Methodology and standards

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.

What you receive

Evidence for customers and auditors, priorities for leadership and fix-ready detail for mobile and backend teams.

For engineering

Findings in the PTaaS portal

Each finding is posted as soon as it is confirmed, with a proof of concept, the platform affected, severity and remediation guidance.

For leadership

Executive summary

A plain-language view of risk to users and data, and the fixes to prioritize first.

For security teams

Report and MASVS matrix

Methodology, a MASVS coverage matrix per platform and every finding with reproduction steps, as a redactable PDF.

For engineering

Retesting included

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

Attestation letter

Issued with every human-led mobile engagement, stating scope and testing dates, ready to share.

For the project team

Integrations and direct chat

Jira, Slack and GitHub integration, and direct chat with the assigned penetration testers throughout the test.

Sample Pentest Report

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.

Timeline

Typical durations. The schedule for each engagement is fixed in writing at scoping.

ScopingPricing within 24 hours
Submit the Get a Quote form and receive pricing within 24 hours, or book a 30-minute discovery call to review platforms, builds and roles first.
One platformTypically 3 to 5 testing days
One iOS or Android build and its backend API, with test accounts for each role in scope.
iOS and AndroidTypically 5 to 10 testing days
Both binaries and the shared backend API. Large APIs and deep resilience testing add days.
FindingsAs they are confirmed
Every finding reaches the PTaaS portal when it is confirmed, so remediation starts during the test.
ReportAt the close of testing
The executive summary, technical report, MASVS coverage matrix and attestation letter are issued when testing closes.
RetestOn request, included
Once a fixed build is available, a retest is requested from the portal and the status of every finding is updated.

Pricing and what drives cost

Mobile engagements are quoted to scope; there is no package price. These factors set the number of testing days:

Platforms
iOS, Android or both. Each platform is a separate binary with its own storage, IPC and resilience surface.
User roles
Each role and entitlement level adds authorization testing on the device and the API.
Backend API size
The number of endpoints the app calls, and any API not reachable from the app.
Resilience depth
How far pinning, jailbreak and root detection, anti-tamper and obfuscation are tested.
Source code access
White-box review shortens discovery and adds code-level findings.
Cadence
A one-time assessment or a continuous program that tests every significant release.

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.

Compliance evidence

One mobile penetration test and its retest results produce evidence for several programs at once.

SOC 2
Evidence for the separate evaluations described in CC4.1, and supporting evidence for vulnerability identification under CC7.1 alongside scan output.
PCI DSS v4.0.1
Requirement 11.4: application-layer penetration testing for payment apps and the APIs that handle cardholder data.
ISO/IEC 27001:2022
Evidence for Annex A 8.8, management of technical vulnerabilities, and 8.29, security testing in development and acceptance.
HIPAA Security Rule
Evidence for the risk analysis at 45 CFR 164.308(a)(1)(ii)(A) and the periodic technical evaluation at 164.308(a)(8) for apps that handle ePHI.
Customer security reviews
A MASVS coverage matrix, a dated report and an attestation letter for enterprise security questionnaires.

Why Stingrai

check icon

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.

check icon

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.

check icon

Published Mobile Research

Stingrai publishes its own mobile security research, including a complete SSL pinning bypass walkthrough, and its researchers have published 18 CVEs.

check icon

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.

check icon

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.

check icon

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.

Trusted by Industry Leaders

quote icon

Rigorous, genuinely hands-on pentest partner that behaves like part of your team. The technical depth is well beyond what we expected at this price point, and they traced issues to specific code paths.

Elia R., Mesh ID (G2 review)

quote icon

Simplifies the pentesting process by giving us one place to request, manage, and track security testing. We spent WAY less time coordinating and more time improving security.

Riley D., Frontend Developer, TPH (G2 review)

Frequently asked questions about mobile application penetration testing

Evidence against the eight control groups in OWASP MASVS v2.1.0: STORAGE, CRYPTO, AUTH, NETWORK, PLATFORM, CODE, RESILIENCE and PRIVACY. In practice that means local storage and keychain or keystore analysis, cryptographic implementation review, server-side authorization testing, transport security and certificate pinning bypass attempts, platform interface abuse including exported components, WebViews and deep links, dependency and SDK review, reverse engineering and anti-tamper testing, and privacy data-flow verification. The backend API the app calls is tested in the same engagement.

Test Your iOS and Android Apps Before Attackers Do

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.