← Back to All Products
Reverse Engineering · Mobile SecurityProduct Plan · Android Reverse Engineering
📱

Maersk Auto-Booking · Android Reverse Engineering

Full-Link Reverse Engineering & Protection-Bypass from APK to Production Automation

Using Maersk's official app as a sample, this fully demonstrates our Android reverse-engineering capability: static decompilation, Frida dynamic hooking, SSL certificate-pinning bypass, traffic-redirection capture, device certificate/key extraction, TLS-fingerprint replication (OkHttp/Android Chrome), and Akamai protection bypass — ultimately restoring a closed mobile interface into a standard, reusable API automation chain.

RELATED SYSTEMS

Relationship With Other Systems

Each project is annotated with its position in the product system, making it easy to see at a glance how systems support each other.

Reverse Methodology: Four Layers

From "visible" to "usable" — turning a black-box app into engineerable interface assets.

🔍

Static Analysis (APK)

jadx / APKTool

Decompile the APK to extract RSA public key, API host, Consumer-Key, embedded certificates, and hardcoded config — building the app's "map."

🪝

Dynamic Hook (Frida)

libflutter.so / SSL

Hook certificate validation and SSL calls at runtime, bypassing Certificate Pinning so a MITM proxy can decrypt HTTPS traffic.

📡

Traffic Redirect & Capture

mitmproxy / Burp

Frida rewrites the socket target + disables cert validation, routing app traffic to a proxy, reconstructing request structure and auth chain per API.

🛡️

Protection Bypass & Replication

Akamai / TLS Fingerprint

Replicate OkHttp / Android Chrome TLS fingerprints (JA3/JA4), with real or forged sensor data, bypassing Akamai Bot Manager and risk control.

Typical Android Reverse-Engineering Pain Points

The more closed and risk-controlled the enterprise app, the higher its first wall.

🔒

Pinning Blocks Capture

Built-in Certificate Pinning makes Charles/Burp throw cert errors; HTTPS traffic is invisible — the first wall of reverse engineering.

🧱

Flutter Native Hardening

Cert validation lives in the libflutter.so native layer; ordinary Java-layer hooks fail — must locate and hook native functions (GetSockAddr / verify_cert_chain).

🛡️

Akamai False-Kills

Server uses TLS fingerprint + sensor data + behavior signals for bot detection; scripts or proxy requests easily trigger 403 / 429 / 441, freezing accounts.

📱

Device Root Barrier

Cert and key extraction generally needs Root + ADB; memory dumps and system keystore reads are fragile and easily trigger app anti-tamper.

Async Validation Causes Fake Success

Query/validation APIs first return PROSPECTIVE or routeValidationsComplete=NO; using too early creates "fake success" — needs two-step polling for backend to converge.

💸

Fingerprint & Proxy Upkeep

Client version upgrades require syncing impersonate targets and custom OkHttp fingerprints; overseas residential proxies bill by traffic, SSL jitter often misread as account failure.

Core Capabilities

A reusable mobile reverse-engineering and automation engineering capability

🧰

Traffic-Capture Toolchain

Frida one-click injection + mitmproxy/Burp integrated capture, auto-extracting Akamai sensor data to JSON.

🔓

SSL Pinning Bypass

Hook SSLContext / X509TrustManager / OkHttp CertificatePinner / libssl, exporting client and server certificates.

🔑

Device Key & Cert Extraction

Via ADB + Root, extract system/app keystores, scan certs, dump app memory to locate private keys and credentials.

🆔

TLS Fingerprint Replication

Use curl_cffi impersonate to mimic Android Chrome and OkHttp 4.x JA3/JA4 fingerprints, keeping them consistent within a session.

🤖

Akamai Sensor Handling

Support both real-device sensor and algorithm-forged sensor modes, restoring service bypass with risk-control cookies.

🔁

Full API Chain Restoration

From capture, restore the 14+ call sequence from login OAuth, query, space-lock, to booking submission, incl. two-step verification timing.

Reverse-Engineering Flow

Crystallize one "black-box capture" into a reusable, engineerable standard process

Engineering Flow
1
APK Static Decompile
Use jadx/APKTool to locate login encryption (RSA public key), API host, Consumer-Key, embedded certs.
2
Env Prep (Root + Frida)
Root the test device, deploy frida-server, confirm Magisk/jailbreak detection not triggered.
3
Frida Dynamic Injection
Hook libflutter.so GetSockAddr / verify_cert_chain, disabling cert pinning and SSL validation.
4
Traffic Redirect Capture
Rewrite app socket target to a local proxy (mitmproxy/Burp), decrypt and record full HTTPS traffic.
5
Cert & Key Extraction
Runtime hook and memory dump extract client cert, private key, KeyStore entries; ADB pull locally if needed.
6
API Timing Restoration
Map departures → validated → booking-options → bookings, identifying async computation and two-step verification polling.
7
TLS Fingerprint Replication
Use curl_cffi impersonate to mimic mobile JA3/JA4, ensuring script behavior matches a real device.
8
Protection-Bypass Injection
Attach Akamai sensor data, device identifiers as headers, reuse risk-control cookies to bypass Bot Manager.
9
Engineering & Reuse
Wrap as a standard client + scheduled task, with circuit breaking, proxy rotation, concurrent scheduling — production automation.

Key Results · Reverse-Engineering Asset

Turn a one-off black-box break into a repeatable, handoff-ready engineering asset.

4 Layers
Reverse Methodology
Static → Dynamic → Capture → Bypass
JA3
TLS Fingerprint Replica
OkHttp / Android Chrome
14+
APIs Restored
Login to booking submission
2 Steps
Verification Polling
Avoid async fake success

Key Breakthroughs

The difficulty is not "can we hook," but engineering the breakthrough into something stable and reusable.

🪝

Frida Integrated Capture

Self-built traffic-capture script auto-starts frida-server and injects redirect, removing manual proxy/cert configuration.

🆔

Consistent TLS Fingerprint

Fix JA3/JA4 within a session (Android Chrome / OkHttp 4.x), avoiding mid-session switching detection and lifting pass rate.

🤖

Real + Forged Dual-Track Sensor

Support both real-device sensor capture and algorithm forgery, switch by scenario for authenticity, cost, stability.

Circuit Break & Proxy Rotation

Dead/frozen accounts auto break and thaw; per-proxy SSL error-rate stats and switching decouple "network" from "account" issues.

Business Value

Convert technical capability into quantifiable, reusable business value.

Improvements Delivered
Turn a closed enterprise app's interface into a standard, callable API asset — near-zero reuse cost.
After bypassing cert pinning, any HTTPS traffic becomes observable, replayable, unit-testable.
TLS fingerprint + sensor double insurance makes automated requests look "like a real device" to risk control.
Full reverse engineering crystallized into toolchain and docs; newcomers quickly reproduce similar app interface restoration.
Applicable Scenarios
Competitor/partner app interface & business-flow research (within authorized scope).
Automated regression testing and interface monitoring for your own apps.
Interface rebuilding and data integration for legacy / undocumented systems.
Mobile risk-control and cert-pinning security assessment and hardening verification.
📌

Content Under Active Update

Product content has been published based on internal materials. The following areas are planned for further development:

Redacted capture samples and interface-field docs (public version)
Frida scripts and toolchain demo video
More industry reverse-engineering case studies
Compliance authorization scope and legal-boundary statement
Contact Us

Start AI Partnership

Whether in government, finance, manufacturing, consumer, or content, we can customize vertical AI agent solutions for you.

📍

Address

Xiamen, Fujian · Wuhan OPC (planned)

🌐

Xianma AI

Xiamen Xianma Intelligent Technology Co., Ltd.

© 2024-2026 Xiamen Xianma Intelligent Technology Co., Ltd. · AI Agent Solutions · www.xianma.top

Products: 15active projects