playbooks

home / skills / a5c-ai / babysitter / mobile-security

mobile-security skill

/plugins/babysitter/skills/babysit/process/specializations/security-research/skills/mobile-security

This skill enables Android and iOS security testing through dynamic instrumentation, SSL pinning bypass, and automated mobile threat analysis.

npx playbooks add skill a5c-ai/babysitter --skill mobile-security

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.3 KB
---
name: Mobile Security Testing Skill
description: Android and iOS application security testing
allowed-tools:
  - Bash
  - Read
  - Write
  - Edit
  - Glob
  - Grep
---

# Mobile Security Testing Skill

## Overview

This skill provides Android and iOS application security testing capabilities using dynamic instrumentation and analysis tools.

## Capabilities

- Execute Frida scripts for hooking
- Analyze APK/IPA files
- Bypass SSL pinning
- Extract app data and credentials
- Perform dynamic instrumentation
- Support Objection framework
- Run MobSF analysis
- Generate mobile security reports

## Target Processes

- mobile-app-security-research.js
- bug-bounty-workflow.js
- red-team-operations.js

## Dependencies

- Frida (frida-tools)
- Objection framework
- MobSF (Mobile Security Framework)
- adb (Android Debug Bridge)
- idevice tools (iOS)
- apktool, jadx (Android)

## Usage Context

This skill is essential for:
- Mobile application penetration testing
- App store security assessment
- Mobile malware analysis
- API security testing from mobile apps
- SSL/TLS inspection

## Integration Notes

- Supports both rooted and non-rooted testing
- Can automate common bypass techniques
- Integrates with CI/CD for mobile security
- Supports emulator and real device testing
- Can extract and analyze app binaries

Overview

This skill provides end-to-end Android and iOS application security testing using dynamic instrumentation, binary analysis, and automated tooling. It combines Frida scripting, MobSF scanning, and Objection capabilities to uncover runtime vulnerabilities, data leaks, and SSL/TLS weaknesses. The goal is repeatable, automatable mobile assessments that integrate into developer and CI/CD workflows.

How this skill works

The skill inspects APK and IPA binaries, runs static analysis via Mobile Security Framework (MobSF), and performs dynamic instrumentation with Frida and Objection to hook functions and bypass protections. It automates common tasks such as SSL pinning bypass, credential extraction, and runtime API tracing on emulators or real devices. Results are aggregated into concise security reports suitable for bug bounty, red team, and developer remediation work.

When to use it

  • Performing mobile app penetration tests for Android or iOS.
  • Validating fixes in CI/CD after security patches or dependency updates.
  • Running automated scans for app store submission or compliance checks.
  • Investigating suspected malware or suspicious app behavior.
  • Supporting bug bounty or red-team engagements with dynamic hooks and proofs.

Best practices

  • Start with static MobSF analysis to prioritize dynamic testing targets.
  • Use emulators for early exploration and real devices for final verification.
  • Keep Frida scripts modular and version-controlled for reproducibility.
  • Respect legal and authorization boundaries; obtain explicit consent before testing.
  • Integrate scans into CI pipelines to catch regressions early.

Example use cases

  • Automate SSL pinning bypass and record intercepted TLS calls to validate API protections.
  • Extract and inspect stored credentials and session tokens to find persistent data leaks.
  • Hook sensitive API calls at runtime to reveal insecure usage of cryptography or authentication.
  • Scan an APK/IPA in CI to generate a MobSF report and fail builds on high-severity findings.
  • Support a bug-bounty workflow by producing reproducible Frida scripts and proof-of-concept traces.

FAQ

Does this skill require rooted or jailbroken devices?

It supports both rooted/jailbroken and non-rooted workflows; some deep hooks and bypasses are easier with elevated device access.

Can it run inside CI/CD pipelines?

Yes. Static scans and many automated tasks are CI-friendly; dynamic instrumentation can be orchestrated with emulators or device farms for pipeline execution.