mobile-pentest

Perform end-to-end penetration testing of Android and iOS mobile applications.

21|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/woohyun212/security-skill --skill mobile-pentest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-pentest
Source: https://github.com/woohyun212/security-skill/tree/main/mobile-pentest
Command: npx skills add https://github.com/woohyun212/security-skill --skill mobile-pentest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies security weaknesses in Android and iOS applications by combining static analysis, dynamic instrumentation, network interception, and storage inspection to find insecure storage, certificate pinning and root/jailbreak bypasses, and exposed secrets mapped to OWASP MASVS.

Core Features & Use Cases

  • Static analysis: Decompile and inspect APKs/IPAs for hardcoded secrets, exported components, and insecure configuration using tools like JADX, apktool, class-dump, and otool.
  • Dynamic instrumentation: Use Frida and objection to bypass SSL pinning, observe runtime behavior, and extract sensitive runtime artifacts.
  • Network and storage inspection: Intercept traffic with a proxy, inspect SharedPreferences/NSUserDefaults, SQLite/Keychain, and validate TLS and certificate pinning controls.
  • MASVS-aligned reporting: Map findings to OWASP MASVS categories and generate a structured findings report for remediation and compliance.
  • Use Cases: Pre-release security assessments, bug bounty triage for mobile targets, and MASVS/MASTG compliance audits.

Quick Start

Request a full assessment of /tmp/target.apk to detect SSL pinning, exposed secrets, insecure storage, and produce a MASVS-mapped findings report.

Frequently Asked Questions about mobile-pentest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform mobile app penetration testing for Android and iOS applications?

Mobile app penetration testing identifies insecure storage, certificate pinning bypasses, and exposed secrets by combining static decompilation with jadx or class-dump, dynamic Frida instrumentation, proxy interception, and storage inspection to map findings to OWASP MASVS controls.

Can I bypass SSL pinning and inspect runtime behavior using Frida and objection?

Yes, bypassing SSL pinning and observing runtime behavior is achieved through dynamic instrumentation using Frida and objection to extract sensitive runtime artifacts and validate certificate pinning controls during mobile security assessments.

Do I need a jailbroken device or root access to run dynamic mobile security analysis?

Yes, runtime access for dynamic instrumentation requires either adb for Android or a jailbroken iOS device to successfully execute Frida scripts, intercept network traffic via proxy, and inspect SharedPreferences, SQLite, or Keychain storage.

What is the best way to map mobile application security findings to OWASP MASVS compliance?

Mapping mobile application security findings to OWASP MASVS compliance requires generating a structured report that aligns identified vulnerabilities from static and dynamic analysis with specific MASVS categories for remediation and audit purposes.

How do I decompile APKs and IPAs to find hardcoded secrets and insecure configurations?

Decompiling APKs and IPAs to find hardcoded secrets and insecure configurations is done through static analysis using JADX and apktool for Android, alongside class-dump and otool for iOS, to inspect exported components and configuration files.