←../back_to_projects
⚡ 2026 Project·completed·Mobile AppSec & Binary Analysis

>_ How I Reverse-Engineered Production Android Apps to Uncover Auth & TLS Pinning Flaws

Authorized Android application security research and reverse engineering: decompiling DEX bytecode with JADX, runtime hooking via Frida, bypassing SSL pinning & root detection, and auditing API traffic against OWASP MASVS.

Android Security Research & Reverse Engineering — architecture.stack
APK / DEX Binary
Static unpacking & manifest inspection
JADX & Smali
Control-flow & crypto key analysis
Frida Runtime Hook
Bypass root & TLS pinning checks
Mitmproxy / Burp
API payload & token vulnerability audit

Figure 1.0 — End-to-end architecture and data flow for Android Security Research & Reverse Engineering

# The Journey Overview

A thorough security audit of production Android apps to find data-leak weaknesses before outsiders can exploit them.

The Starting Point (Problem)

Mobile apps often keep sensitive business logic, API keys, or session tokens on the client, where attackers can pull them apart.

Why This Matters (Outcome & Impact)

Mapped sensitive data flows, proved the risk of bypassing app protections (SSL pinning & root detection), and wrote remediation recommendations based on OWASP MASVS.

# Phase 1: System Architecture & Pipeline

The system architecture is designed to be modular so each layer has a clearly isolated responsibility:

STAGE 01

APK / DEX Binary

Static unpacking & manifest inspection

STAGE 02

JADX & Smali

Control-flow & crypto key analysis

STAGE 03

Frida Runtime Hook

Bypass root & TLS pinning checks

STAGE 04

Mitmproxy / Burp

API payload & token vulnerability audit

Core Technical Deliverables

  • Decompiling APK/DEX to Java & Smali to dissect authentication logic
  • Runtime dynamic instrumentation to test SSL pinning resilience
  • Encrypted REST API traffic analysis & local storage audit (Keystore/SharedPrefs)

# Phase 2: Engineering Decisions & Implementation

[Decision 01]Combined static analysis (JADX) with dynamic hooking (Frida) so security validation does not rest on guesses from static code alone.
[Decision 02]Used JavaScript injection scripts in Frida to intercept Cipher and OkHttp CertificatePinner calls in real time without modifying the APK signature.
[Decision 03]Wrote findings with step-by-step reproduction evidence so the developer team can patch the weaknesses right away.
frida-pinning-audit.js
Java.perform(() => {
  const Pinner = Java.use("okhttp3.CertificatePinner");
  Pinner.check.overload("java.lang.String", "java.util.List")
    .implementation = function (hostname) {
      console.log("[audit] TLS check intercepted for: " + hostname);
      return; // Verify server-side token validation resilience
    };
});

# Phase 3: Application Screens & Operational Workflow

1. Static Decompilation

Mapping the package structure, exported activities, and hardcoded secrets in DEX bytecode.

2. Runtime Hooking

Testing root detection & certificate pinning resilience on a test device using Frida.

3. Traffic & Storage Audit

Verifying API payload encryption and the security of tokens kept in local storage.