Mobile application penetration testing services.

Need a security report for your Android or iOS app? We find the vulnerabilities, confirm every finding, prioritize what matters and tell your team how to fix it.

For teams that build and publish Android and iOS apps.

Mobile apps handle accounts, personal data and payments, and rely on APIs that attackers can reach directly. A vulnerability can expose your users' data or let attackers abuse your service.

Tell us what you want tested and what you need the pentest for.

Every app is different: before testing, we study yours to decide where the effort is worth spending. Depending on the agreed scope, testing can cover:

  • Authentication and session handling.
  • Sensitive data storage and exposure.
  • Platform attack surfaces: deep links, WebViews, inter-process communication (IPC), permissions and integrations.
  • Client-side security controls and business logic.
  • Communication with backend services and APIs, where included in scope.

If what you need is to check whether your app's RASP or anti-bot protections stop real attackers, we have a dedicated service for that.

  1. Call: you tell us about your app and what worries you. We shape the assessment around your concerns and the questions you need answered.
  2. Proposal: we set out the agreed scope, what we need from you, the schedule and a fixed price.
  3. Testing: you send us the builds and we start. If we find something critical, we let you know right away.
  4. Report and review: we send you the report and go through it with your engineers.
  5. Retest: once you have fixed the vulnerabilities, we confirm they are resolved in the new build.

Technical report

Every finding includes evidence, reproduction steps, impact, a CVSS score and vector, CWE and, where they apply, OWASP MASWE references, and how to fix it.

Executive summary

Covers the scope and build tested, the results and the priorities, for management and non-technical readers.

Retest report

If you include the retest, we send a new version of the report with the status of each finding on the new build.

Letter for your customers

On request, at no extra cost, we provide a signed letter with what we tested, the version, the date and the result, for your customers or auditors. After the retest, we update it with the new results.

Want to see what a report looks like? Download a sample.

We help write the OWASP testing guide

Our team contributes tests and demos to the OWASP MASTG, and those same specialists are the ones who test your app. OWASP recognized this work by naming vulnit an OWASP MAS Advocate, and the team holds offensive certifications such as OSCP, OSWE and OSED.

Your app's protections won't stop the test

Reverse engineering protected apps is our daily work: certificate pinning, root detection and obfuscation are part of the job, not the end of it. We test the same build your users get, with nothing special for your team to prepare.

Meet the team
Will the report work for my customer's security review?

It is designed for that. The report includes an executive summary for non-technical readers and, on request, a signed letter, at no extra cost, with what we tested, the version, the date and the result, which you can share without disclosing the details of the findings.

How long does it take and what does it cost?

It depends on how many platforms we test (Android, iOS or both), the complexity of your app and the scope. We send you a proposal with a fixed price and the schedule. It usually takes one to two weeks per platform, report included. We can usually start the same week you accept the proposal; the start date depends on our team's workload and is stated in the proposal.

Are backend APIs included?

They can be, and we generally recommend it: much of a mobile app's risk lies in the APIs it uses. We decide it with you case by case, depending on the type of app and what its backend exposes.

What do you need from us?

The app builds (APK or AAB for Android, IPA for iOS), test accounts for each role in scope and access to the environment you prefer, whether production or a staging environment. The proposal sets out the details.

Do you need source code?

No. By default, testing is black-box: we attack your app with the same information an attacker would have, using the same build you release to your users. If you prefer, we can also review the source code.

Do you test on physical devices?

When needed. On Android we mainly work with Chameleon, our analysis environment: it gives us deep visibility into what the app does in the operating system, and handles root, pinning and anti-instrumentation checks at the OS level by default. If we hit a limitation that matters for your app, we use physical devices. On iOS we use physical devices.

Do you use AI on my app?

Yes, to cover more of your app and go deeper in the same time. We use AI providers that do not train their models on your data. We only use accounts you provide or that we create ourselves, never other real users' accounts. Our specialists lead the work and validate every result. If your policy does not allow external AI, tell us when we agree on the scope and we work without it.

Who validates the findings?

Our specialists review and validate every finding. Automation and AI help with the analysis, but the final call is always theirs.

Is retesting included?

Retesting is quoted separately at a reduced rate. In the proposal we give you two options, testing only or testing with one retest round, so you know the total cost from the start.

What format do the findings come in?

You receive one report per platform, with every finding detailed. If you also want to use them in your own tools, we provide them as CSV or JSON too.

Can I see a sample report?

Yes. Download our sample report, a real deliverable from a full assessment.

What language is the report in?

English by default. If you need it in Spanish, just tell us.

How do you handle confidentiality?

We agree confidentiality terms before you share builds or documentation. We have a standard NDA, but if you prefer to use yours, we are happy to review it.

Assessing against a security standard?

A penetration test focuses on exploitable vulnerabilities and their impact. If your objective is to evaluate coverage against specific security controls, explore our OWASP MASVS assessment. If you need both, we can combine them in a single project: the work on one also serves the other.

For mobile payment software, our PCI MPoC testing helps identify security weaknesses and prepare for formal laboratory evaluation.

For EU product security requirements, our CRA testing for mobile apps connects the evidence to your technical documentation.

Can I combine several services in one project?

Yes. They all start from the same analysis of your app. Tell us what you want to know, for example which vulnerabilities it has, whether your protections stop an attacker or which OWASP MASVS controls it meets, and we combine it into a single project.

Tell us about your app and what you need the pentest for. We reply within one business day to arrange a scoping call.

Talk to our team

A necessary cookie remembers your choices for up to 180 days. Privacy policy.