All services

Audit

Android App Audit

If you are preparing to publish your first Android app, or you have just finished a vibe-coded application and are unsure whether it is secure, efficient, and production-ready, our team can help.

We will review and test your application from a professional Android development perspective and provide feedback on:

What we review

  • Security issues & potential vulnerabilities
  • Performance bottlenecks
  • Code quality & architecture
  • Android development best practices

Assessment coverage

A practical review of the complete Android attack surface

We combine application security testing with senior Android engineering review, so the audit covers exploitable weaknesses as well as reliability and architecture problems that can make a production app fragile.

Data storage and privacy

Sensitive local data, logs, backups, caches, telemetry, token handling, and the complete lifecycle of personal or payment data.

Network and authentication

TLS and hostname validation, Network Security Configuration, credentials, session storage, endpoint trust, and request logging.

Android platform exposure

Exported components, intents, deep links, PendingIntent use, permissions, IPC authorization, WebView bridges, and navigation controls.

Cryptography and secrets

Embedded credentials, random number generation, key storage, Android Keystore use, and release-build secret exposure.

Dependencies and supply chain

Direct and transitive dependencies, known CVEs, vulnerable call-path reachability, vendor SDK provenance, SBOM gaps, and update risk.

Reliability and maintainability

Blocking calls, timeouts, cancellation, lifecycle behavior, process-death recovery, test coverage, architecture, and security-sensitive code quality.

Methodology

Tool-assisted. Human-verified.

Scanner results are normalized, deduplicated, and checked in application context. We do not turn unverified warnings into findings: manual code tracing and controlled runtime checks establish whether a risky path is reachable and what its real impact is.

  1. 01

    Build and APK triage

    We inspect package metadata, signing, the manifest, resources, embedded strings, SDK levels, network configuration, and release flags.

  2. 02

    Static and dependency analysis

    Automated SAST, Android-specific checks, and software composition analysis identify candidate security, quality, and dependency risks.

  3. 03

    Manual secure code review

    An Android engineer traces sensitive data, authentication, IPC, WebView, cryptography, logging, error handling, and critical business flows.

  4. 04

    Controlled runtime verification

    Where scope permits, we use a test device to inspect logs and storage, invoke exposed flows, and validate network behavior in a controlled environment.

  5. 05

    Risk rating and remediation

    Confirmed findings are classified by exploitability, business impact, data sensitivity, and confidence, then ordered into a practical remediation roadmap.

  6. 06

    Retest and release guidance

    We define repeatable exit criteria for important fixes and can independently verify that release-blocking issues are actually closed.

Professional toolkit

Multiple perspectives, one consolidated assessment

MobSF

APK and source analysis for manifest exposure, hardcoded values, network settings, risky APIs, storage, and mobile security signals.

SonarQube

Java and Kotlin analysis for security issues and hotspots, sensitive logging, reliability defects, maintainability, and code smells.

Android Lint

Android-specific correctness, manifest and API misuse, component configuration, SDK compatibility, performance, and quality checks.

OWASP Dependency-Check

Software composition analysis of direct and transitive dependencies against publicly disclosed vulnerabilities.

JADX · apktool · aapt2 · apksigner

Independent inspection of APK contents, resources, decompilability, manifest behavior, build metadata, and signing information.

ADB · logcat · test device

Runtime evidence for logs, local storage, activity invocation, lifecycle behavior, screenshots, and release configuration.

Intercepting proxy

Controlled verification of TLS behavior and request contents in an authorized, non-production environment.

Standards and traceability

Findings mapped to recognized security guidance

The framework is tailored to your app and risk profile. For payment applications, additional payment-data checks are included without presenting the audit as a formal certification or compliance attestation.

OWASP MASVS

The primary mobile security control baseline across storage, cryptography, authentication, networking, platform interaction, code quality, resilience, and privacy.

OWASP MASTG

Testing techniques and Android-specific procedures used to verify MASVS controls through static and dynamic analysis.

OWASP MASWE

A mobile weakness taxonomy used to give confirmed findings consistent identifiers and traceability to controls and tests.

Android security best practices

Platform guidance for secure storage, TLS, Network Security Configuration, IPC, WebView, permissions, signing, and application hardening.

CWE and CVSS v3.1

Common weakness classification and structured vulnerability severity support, supplemented by application-specific business impact.

PCI DSS v4.0.1

Applied as payment-data protection guidance when cardholder or sensitive authentication data is in scope; it is not represented as a PCI assessment or attestation.

Deliverables

Documentation your team can act on

The final report is built for both decision-makers and developers. It separates release blockers from lower-priority hardening work and gives the engineering team a concrete route to remediation.

Executive verdict and release gate

A concise risk posture, the most material issues, and a clear view of what should block production release.

Evidence-backed findings

Severity, impact, technical evidence, affected paths, standards mapping, and the reasoning behind each confirmed issue.

Prioritized remediation roadmap

Practical recommendations grouped into immediate fixes, security-sprint work, and longer-term hardening.

Retest criteria

Specific expected outcomes your team can use to prove that critical fixes work and prevent regression.

Getting started

What we usually need

For the strongest review, we work with your source code, a signed release APK, Gradle dependency metadata, and a test account and non-production API environment. The exact scope and access are agreed before the assessment begins.

The process usually takes only a couple of days. Once the audit is complete, you receive detailed documentation covering the full review process and every potential issue we identified, together with practical recommendations for improvement.

If you need help fixing any of the issues we find, our team can assist with the implementation as well.

Ready for a second opinion?

Make your Android release easier to trust.

Tell us about your app