Mobile Application Penetration Testing
Your mobile app runs on devices you don't control. We test iOS and Android builds for insecure storage, weak crypto, and backend flaws, covering the app, its APIs and the data it leaves behind.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.
What's covered
- Static and dynamic analysis of iOS and Android builds
- Insecure data storage, logging and backup exposure
- Certificate pinning, transport security and man-in-the-middle resistance
- Authentication, session and token handling
- Reverse-engineering resistance, tampering and root/jailbreak checks
- Backend API testing that supports the mobile app
What you receive
- Technical report covering client and server-side findings
- Executive summary with risk ratings
- Remediation guidance aligned to OWASP MASVS
- Free retest of fixes
- Attestation letter
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Only apps and backends you own or are authorised to test
- No attacks against app-store infrastructure or third-party SDKs' servers
- No use of real user data beyond proof of impact
- No distribution of modified builds outside the engagement
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Do you test both iOS and Android?
- Yes, we test either or both to OWASP MASVS. Cross-platform apps are tested per platform because storage, crypto and transport behaviour differ.
- What builds do you need?
- A test build (IPA/APK), test accounts for each role, and a signed scope. Non-obfuscated debug builds speed up static analysis, though we test release builds too.
- Do you also test the backend?
- Yes. Most serious mobile risk lives in the APIs behind the app, so backend testing is included in the methodology.
Related services
Offensive / Testing
API Penetration Testing
APIs are where modern breaches happen. We test your REST, GraphQL and gRPC endpoints for broken authorisation, data leakage and logic flaws, so the interfaces powering your apps and partners can't be turned against you.
Offensive / Testing
Web Application Penetration Testing
We attack your web application the way a skilled adversary would — safely, under a signed scope — and hand you a clear map of every exploitable weakness. You get proof, business impact and a fix-it plan, not a raw scanner dump.
Offensive / Testing
Reverse Engineering & Binary Analysis
When you need to understand what a binary really does — your own software, a vendor component or suspicious code you're authorised to examine — our analysts take it apart to reveal hidden behaviour, weaknesses and risks.