Overview
A mobile app is three attack surfaces wearing one icon: the binary you shipped, the data it leaves on the device, and the backend it talks to. We test all three, on rooted and jailbroken hardware, against the build you are about to release.
Findings arrive in your channel as they are confirmed, with the exact steps and tooling needed to reproduce them.
What is covered
Static analysis of the shipped binary and its dependencies
Runtime instrumentation and hooking on real devices
Local storage, keychain, cache and logging handling
Certificate pinning and transport security
Deep links, IPC and exported components
The backend API the app depends on
How it runs
Five stages: Scope, Recon, Exploit, Report, Retest. We test the build you intend to ship, and we retest the build that fixes it — both included in the same engagement.
What you get
A working proof for every finding, reproducible on a device you own
Platform-specific remediation, not generic advice
A retest and a letter of attestation once the fixes land
Direct access to the engineer who did the work
Method and standards
OWASP MASVS for the verification standard and MASTG for the testing procedures
OWASP Mobile Top 10 for risk framing
Apple and Google platform security guidance for the device-side controls
Rules of engagement, test accounts and an abort path agreed in writing before day one
Our Services
