A mobile app runs on a device the attacker fully controls. They can unpack the app, read what it stores and intercept its traffic to your servers. MAYASEVEN tests iOS and Android apps and the APIs behind them, using OWASP MASVS as the reference. Every finding is verified by an expert and comes with a CVSS score and a proof-of-concept.
Whether the app keeps tokens, passwords or personal data where another app, or anyone holding the device, can read them.
Transport encryption, certificate validation and certificate pinning bypass, to intercept and modify traffic between the app and the backend.
Login, biometrics, PIN and session handling tested for bypass, and a check that authorization is enforced on the server and not only in the app.
Unpacking the app to find hardcoded secrets, and testing protections such as root or jailbreak detection, anti-tampering and code obfuscation.
Most serious mobile findings sit in the server-side API. Testing the APIs the app calls is always part of the work.
Deep links, inter-app communication, requested permissions and components exposed to other apps.
Analysing the app package without running it, to find embedded secrets, insecure configuration and vulnerable libraries.
Running the app on test devices, intercepting traffic, changing its behaviour at runtime and inspecting what it writes to the device.
Testing the APIs and servers the app connects to, the same way we test web applications and APIs.
The IPA and APK of the version to test, or store links if that version is already published.
Accounts at each privilege level, plus anything needed to complete transactions, such as test accounts or cards.
Tell us whether the app uses certificate pinning, root detection or an app-shielding product, so we can plan the time accurately.
Our own on-prem AI agent helps analyse the unpacked app code and every endpoint the app calls, so the suspicious spots are flagged quickly and completely. Our experts then test on real devices, bypass the app's protections by hand and prove the impact of each vulnerability. A named expert signs off every report.
We recommend both. The client code, storage mechanisms and protections differ between platforms, so a flaw on one may not exist on the other. The shared backend API is tested once.
Yes. Cross-platform apps are unpacked and intercepted differently from native apps. Tell us the framework during scoping so we can prepare the right tooling and estimate the time accurately.
OWASP MASVS (Mobile Application Security Verification Standard) is the OWASP standard that defines security requirements for mobile apps, grouped into areas such as storage, cryptography, authentication, network communication and resilience against reverse engineering. We use it as the reference framework for testing.
No. A standard test uses the app builds and test accounts. If you want code-level depth, it can be combined with a source code review.
The main factors are the number of platforms, the number of functions and privilege levels, and the protections the app uses. Pricing is based on scope, not a fixed package. We send a quote after a short scoping conversation, and a lead expert replies within one business day.
Talk to MAYASEVEN to scope the work and get a quote — a lead expert replies within one business day.