What problem does it solve? Android apps ship compiled C/C++ code as .so libraries with no memory safety, and auditing them for buffer overflows, use-after-free, and insecure JNI boundaries requires deep reverse-engineering expertise that is easy to get wrong or skip entirely. ## Core Features & Use Cases - Native Library Inventory: A read-only detector script lists every bundled lib/<abi>/.so with ABI and size, and flags JNI_OnLoad, Java_ exports, and risky imports like strcpy, sprintf, and memcpy when binutils are available. - Five-TTP Methodology: Structured test procedures cover memory corruption, use-after-free, native RCE, insecure JNI boundaries, and known-CVE bundled libraries, each with preconditions, signals, and confirmation steps. - Hardening Review: checksec-style commands verify RELRO, stack canaries, PIE, FORTIFY, and NX so missing mitigations are reported alongside any memory bug. - Use Case: During an authorized bug-bounty test, you find an exported Activity passing attacker bytes to a native method; use this Skill to inventory the .so, reverse the JNI handler in radare2 or Ghidra, and confirm an out-of-bounds write under ASan. ## Quick Start Run the native-audit inventory script against my extracted APK target hash and tell me which bundled .so libraries expose JNI entry points or risky C imports worth reversing.
