← ClaudeAtlas

harden-mobile-appslisted

Static and runtime hardening for Android and iOS apps running on devices an attacker controls: APK/IPA reverse engineering, rooted or jailbroken devices, Frida or Xposed hooking, repackaging, certificate pinning bypass, and secrets read from local storage (MITRE ATT&CK Mobile T1617, T1631, T1626, T1655, T1638, T1634, T1533). Signals come mostly from server-side attestation: Google Play Integrity verdicts, Apple App Attest and DeviceCheck, Android Key Attestation, Firebase App Check, RASP tamper events, and MDM/UEM compliance. Gives hardening controls (TLS pinning, Keystore/Keychain storage, obfuscation, RASP, attestation enforcement), detection, a hunt, and OWASP MASVS mapping. Use when hardening or reviewing an Android or iOS app, pinning TLS or storing secrets on a mobile client, choosing between Play Integrity, App Attest, and App Check, triaging root/jailbreak or Frida alerts, or hunting repackaged clients hitting your API.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Mobile App Hardening (Android / iOS) - Defensive Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule and reference sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet. ## TL;DR A mobile app runs on hardware the attacker owns, so every client-side check can eventually be patched out. The only durable control is to **treat the client as untrusted and enforce trust at the backend through attestation**: have the server require and verify a fresh **Google Play Integrity** token (Android) or **Apple App Attest** assertion (iOS), reject requests that fail, and never let a client-side "device is clean" boolean be the gate. Layer four client-side hardening measures on top as defense in depth, not as the boundary: **TLS certificate or public-key pinning** so a stripped-CA proxy cannot read traffic, **secure storage** in the Android Keystore (StrongBox where present) and iOS Keychain with Secure Enclave rather than shared preferences or plists, **code shrinking and obfuscation** (R8/ProGuard, and a commercial obfuscator for high-value logic) to raise reverse-engineering cost, and **RASP** (root/jailbreak, debugger, emulator, and