Flutter & Mobile App Auditing
Security assessments of Flutter, iOS, and Android applications. We test data storage, API communications, certificate pinning, reverse engineering resilience, and platform-specific attack vectors unique to mobile.
Reverse engineering of Flutter binaries, Dart source review, API token leakage, insecure local storage, and platform channel security across both iOS and Android builds.
What we cover
Local storage
Credentials, tokens and personal data written to shared preferences, SQLite, or the device keychain without protection.
Transport security
Certificate pinning strength, TLS configuration, and whether traffic can be intercepted with a proxy on a rooted device.
Reverse engineering
What an attacker recovers from your shipped binary, including embedded secrets, API endpoints and business logic.
API surface
The backend your app talks to, tested directly rather than only through the UI the app happens to present.
Platform channels
The boundary between Dart and native code, where input validation is frequently assumed to have already happened.
Platform controls
Root and jailbreak detection, screenshot and clipboard protection, and biometric gating that can be bypassed.
A mobile app is two things at once: a binary you hand to the public, and a client for an API you control. Both need testing, and testing only the first is how most assessments miss the findings that matter.
Anything shipped inside your app should be treated as known to an attacker. Flutter's compilation to native code is not the barrier it is often assumed to be. Dart snapshots can be unpacked, and embedded API keys, internal endpoints and licensing logic recovered from a release build.
How we approach a mobile audit
We begin with the shipped artefact, pulling apart your release build to establish exactly what it discloses. We then run the application on instrumented devices, intercepting its traffic to see what it actually sends, what it stores between sessions, and what it leaves behind on logout.
From there we test the API directly. Mobile backends are frequently more trusting than their web equivalents, on the assumption that only the official client will ever call them, so we call them the way an attacker would, without the client in the way.
Platforms we work with
We test Flutter applications across both iOS and Android builds, as well as native Swift and Kotlin codebases, and React Native where required. For Flutter specifically we review Dart source where it is available and work from the compiled snapshot where it is not.
What you get
01
A written report covering both the application and the API it depends on
02
Proof of concept for each exploitable finding, reproduced on a real device
03
Specific remediation guidance for Dart, Swift and Kotlin code paths
04
A follow-up review of your fixes once remediation is complete
Other services
Every engagement starts with a conversation about scope. Tell us what you have built and what worries you about it, and we will tell you what a useful assessment looks like.