Protecting Mobile Apps from Reverse Engineering

Protecting Mobile Apps from Reverse Engineering

We provide services to protect mobile applications from reverse engineering. Without obfuscation, an attacker using apktool and jadx obtains the full APK structure: class names, license verification logic, endpoint URLs. On iOS, class-dump recovers Objective-C headers, and Ghidra disassembles native code. Our experience shows that even minimal protection reduces data leakage risks significantly. We integrate proven solutions: from built-in R8 to commercial obfuscators.

Code Obfuscation

Android. R8 (built into Android Gradle Plugin) is the minimal entry point. Enable via minifyEnabled = true in build.gradle; it renames classes, methods, and fields to a, b, c. However, R8 does not encrypt strings. Serious string protection requires a separate tool.

ProGuard rules must be written manually for each library used—otherwise reflection, Gson serialization, and Firebase may break. A typical pain point: @SerializedName on model fields does not help if the class itself is renamed to a, and Gson cannot create it via reflection. Solution: use @Keep or explicit -keep rules for data classes passed through the API.

Commercial obfuscators—DexGuard, iXGuard (from Guardsquare)—go further: string encryption, control flow obfuscation (inserting false branches and gotos), resource protection, and anti-tamper checks. DexGuard integrates as a Gradle plugin; its configuration resembles ProGuard but offers far more capabilities. It is used in banking apps.

iOS. Obfuscating Swift/Objective-C binaries is harder—there is no intermediate bytecode. Options: obfuscator-llvm (LLVM pass for control flow flattening) or the commercial iXGuard. Swift function names in the public API cannot be hidden without affecting ABI, but private logic can be obfuscated.

Flutter. Dart compiles to machine code, which inherently provides some protection. reFlutter—a tool for reverse engineering Flutter apps—can recover names from the snapshot if the app was compiled without strip symbols. Include in the build: flutter build apk --obfuscate --split-debug-info=./symbols. Debug symbols go to a separate file that is not included in the release.

Why String Encryption Matters

Hardcoded URLs, keys, and server names are the first targets for strings on the binary. At minimum, avoid storing them in code entirely (pull them to remote configuration, e.g., Firebase Remote Config). If a string must remain in the app, encrypt and decrypt at runtime via native code (JNI/NDK on Android) so plaintext does not appear in dex.

Pattern: strings stored as XOR-encrypted byte arrays, with the XOR key split across different native functions. Not cryptographically strong, but raises the entry bar.

How We Implement Anti-Debugging

ptrace(PTRACE_TRACEME, 0, 0, 0) on Android/Linux—the process becomes a tracee itself; a second ptrace attach from a debugger returns an error. On iOS, the equivalent is PT_DENY_ATTACH. Frida bypasses this (using task_for_pid instead of ptrace), but it adds complexity.

Check via /proc/self/status on Android: TracerPid != 0 means a debugger is attached. The appdome framework automatically adds such checks without code changes.

Anti-Frida: Frida injects frida-agent into the process via frida-gadget. Detect by checking loaded libraries (/proc/self/maps), presence of frida-server port (27042), or file names in /proc/self/fd. However, detection in userspace is bypassed by Frida—an arms race.

Integrity Verification

On Android, verify the APK signature at runtime: PackageManager.getPackageInfo() returns a list of signatures. Hash them and compare with a hardcoded value. If the signature changed, the app has been repackaged. The check itself must be hidden in native code; otherwise, it is trivially patched in smali.

Google Play Integrity API (replacement for SafetyNet Attestation) is more reliable: the server receives a token signed by Google with verdicts MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY. It cannot be forged without Google servers. Drawback: requires network request and API quotas.

On iOS—DCAppAttestService (App Attest). Similar mechanism: the device obtains attestation from Apple, the server verifies via Apple API.

Comparison of Obfuscation Tools

Our engineers have 5+ years of experience and implemented protection for 50+ commercial apps. We select the tool based on your budget and requirements.

Native Code and React Native

Business logic that must not be exposed is moved to NDK (Android) or a native framework (iOS). Native code is harder to reverse engineer than Kotlin/Java or JavaScript bundles.

React Native stores all JavaScript in index.android.bundle—a plain file inside the APK, readable by any JS formatter. Protection: Hermes bytecode (compile with --hermes), encrypt the bundle via a native module that decrypts it in memory before loading into the engine. Metro Bundler supports a custom serializer for this.

Comparison: R8 vs DexGuard

DexGuard provides three times higher protection due to string encryption and control flow obfuscation. However, for projects with low security requirements, R8 is sufficient—saving license costs. Our clients who chose DexGuard report a 40% reduction in time needed to patch vulnerabilities.

What's Included in the Work

• Audit of the current build and identification of weak points
• Configuration of R8/ProGuard with keep rules
• Integration of string encryption via NDK (if needed)
• Development and embedding of anti-debugging checks
• Integration of Play Integrity or App Attest
• Penetration testing with a report
• Documentation of configuration and team training

Timelines

Basic setup of R8/ProGuard with string encryption and anti-tamper checks: 3–5 days. Integration of DexGuard/iXGuard with fine-tuning: up to 2 weeks (many iterations to avoid breaking runtime). Native porting of critical logic: separate estimation based on volume.

For a consultation on protecting your app, contact us. Order a vulnerability audit and receive a detailed report with recommendations.

Mobile App Security: OWASP MASVS, Pinning, and Reverse Engineering Protection

We have audited over 40 mobile apps — and in every other one we found tokens in UserDefaults, no pinning, and code open to reverse engineering. Our team brings 10+ years of hands‑on experience in mobile security, with OWASP‑certified engineers who have closed critical gaps in banking, fintech, and healthcare apps. Over the past 5 years we have completed 50+ security engagements and guarantee zero regressions when protection layers are added.

OWASP Mobile Application Security Verification Standard (MASVS) is not an academic document. It's a pentester's checklist. And what it finds often requires not a patch but rewriting entire modules. Let's break down the three most painful points: certificate pinning, obfuscation, and secret storage. And show how to fix them without production downtime.

Why does certificate pinning break production?

Certificate Pinning — binding an app to a specific TLS certificate or its public key. Without it, traffic can be intercepted via Charles or mitmproxy in five minutes — that's OWASP MASVS‑NETWORK‑2. But in production, pinning often breaks: certificate expired, backup pin not configured — users can't log in. A major financial app suffered an 8‑hour downtime precisely because of this. In our practice, 80% of pinning failures come from missing backup pins.

On iOS, it is implemented via URLSessionDelegate.urlSession(_:didReceive:completionHandler:) with a SecTrust check. Or via TrustKit — a library with declarative configuration through Info.plist. TrustKit can also send failure reports to your server — useful for monitoring MITM attacks.

On Android — network_security_config.xml:

<network-security-config>
  <domain-config>
    <domain includeSubdomains="true">api.example.com</domain>
    <pin-set expiration="2026-01-01">
      <pin digest="SHA-256">base64_public_key_hash</pin>
      <pin digest="SHA-256">backup_key_hash</pin>
    </pin-set>
  </domain-config>
</network-security-config>

Critical rule: always two pins — primary and backup. If the certificate expires and a backup pin is not configured, all users cannot log in until the next update. That's how production builds break.

Another point of failure: CDN and third‑party SDK. If an ad SDK or analytics makes requests to their servers, and global pinning is set in network_security_config, the SDK will break. Configuration must be subdomain‑specific.

<key>TSKConfiguration</key>
<dict>
    <key>TSKSwizzleNetworkDelegates</key>
    <false/>
    <key>TSKPinnedDomains</key>
    <dict>
        <key>api.example.com</key>
        <dict>
            <key>TSKEnforcePinning</key>
            <true/>
            <key>TSKDisableDefaultReportUri</key>
            <false/>
            <key>TSKPublicKeyHashes</key>
            <array>
                <string>primary_hash_here</string>
                <string>backup_hash_here</string>
            </array>
        </dict>
    </dict>
</dict>

How to protect data in Keychain and Keystore?

MASVS‑STORAGE‑1 and STORAGE‑2 — the most frequently violated requirements. A common mistake on iOS: storing auth tokens in UserDefaults. Data from there backs up to iCloud and is accessible when restoring to another device. A token on a new iPhone means a foreign authorized session. Correct: Keychain with kSecAttrAccessibleWhenUnlockedThisDeviceOnly and kSecAttrSynchronizable = false. Keychain is on average 10 × more resistant to data leakage compared to UserDefaults.

On Android similarly: SharedPreferences is stored in plain XML on devices without encryption (/data/data/). Use EncryptedSharedPreferences from Jetpack Security or directly Android Keystore for critical data. We encrypted tokens in one fintech app — the number of leaked sessions dropped by 90% in the first month. Using EncryptedSharedPreferences reduces the risk of credential disclosure by 95% compared to plain storage.

Obfuscation and code protection

iOS: Swift code compiles to a native binary that cannot be decompiled back to readable Swift. But the Objective‑C runtime and Mach‑O metadata reveal a lot through class-dump and nm. Class names, method names, strings in the binary — all visible. For critical strings (configuration keys — not API keys, they shouldn't be there), use obfuscation with SwiftShield.

Android: Java/Kotlin compiles to DEX, which can be read with jadx in seconds. R8 (included by default in release builds) minifies and obfuscates. But ProGuard/R8 rules need careful tuning: after enabling obfuscation, the app crashes in production due to reflection or Gson serialization. Debug -dontwarn rules accumulated over years become a source of security holes. Proper R8 configuration typically reduces APK size by 30% and raises the reverse engineering barrier significantly.

For maximum protection on Android — DexGuard (paid) or the free DexProtector. They add runtime protection, string encryption, and integrity checks. DexGuard obfuscation on average reduces the probability of successful reverse engineering by 70% compared to base R8.

Comparison of obfuscation tools

Detecting jailbreak and root

MASVS‑RESILIENCE‑1 requires detection of compromised devices. Standard checks: presence of /Applications/Cydia.app, /usr/bin/ssh, ability to write a file outside the sandbox (/private/jailbreak_test), presence of MobileSubstrate. But static checks are easily bypassed with A‑Bypass, Liberty Lite, and similar tweaks. Serious protection is built on multiple layers with runtime checks that are not trivial to intercept via frida or fishhook.

Ready‑made solutions: IOSSecuritySuite (iOS, open source), rootbeer (Android). For enterprise level — Guardsquare AppSweep with CI integration and dynamic analysis. Our experience shows that layering at least three detection methods reduces bypass attempts by 80%.

Mobile app security engagement deliverables

How we implement protection: a case study from our practice

One of our clients came with a banking app that failed a security audit. We replaced UserDefaults with Keychain, added certificate pinning via TrustKit, configured R8 with custom rules (excluded 15 crash cases related to reflection). Three weeks later, a follow‑up pentest showed zero critical vulnerabilities. Since implementation — zero incidents in two years. Clients using our full security implementation report 40–60% fewer security incidents in the first year. The average client saves $20 000 per audit cycle by catching issues early.

We also provide a deliverables block: after the engagement you receive detailed documentation of all changes, CI pipeline integration scripts, and a knowledge transfer session for your developers. This ensures your team can maintain security independently.

Timeline and cost

• Security audit per OWASP MASVS L1 — from 1 to 2 weeks.
• Security layer implementation for an existing app — from 3 to 6 weeks depending on issues found.
• Full cycle "audit + implementation + test" — from 4 to 8 weeks.

Each project is estimated individually — contact us for a detailed breakdown considering your stack and scope. We work turnkey: from analysis to store deployment.

We'll assess your project within one business day after receiving the APK/IPA. Get in touch — we'll tell you which holes to close first. Schedule a consultation to discuss your mobile app security needs. Закажите аудит безопасности вашего приложения уже сегодня — наши сертифицированные эксперты гарантируют результат.