Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
harishwarrior avatar

Owasp Mobile Security Checker

  • 323 installs
  • 58 repo stars
  • Updated July 12, 2026
  • harishwarrior/flutter-claude-skills

Runs security audits on Flutter and mobile apps against the OWASP Mobile Top 10 (2024) with Python scanners for secrets, dependencies, network, and storage.

About

A mobile security skill combining four automated Python scanners with manual-review guidance for the OWASP Mobile Top 10. A developer uses it to find hardcoded secrets, insecure storage, weak network config, and vulnerable dependencies.

  • Automated scanners for M1 secrets, M2 dependencies, M5 network, M9 storage
  • Reference guidance for the six manual-review categories

Owasp Mobile Security Checker by the numbers

  • 323 all-time installs (skills.sh)
  • +21 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #610 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/harishwarrior/flutter-claude-skills --skill owasp-mobile-security-checker

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs323
repo stars58
Last updatedJuly 12, 2026
Repositoryharishwarrior/flutter-claude-skills

What it does

Runs security audits on Flutter and mobile apps against the OWASP Mobile Top 10 (2024) with Python scanners for secrets, dependencies, network, and storage.

Files

SKILL.mdMarkdownGitHub ↗

OWASP Mobile Security Checker

Requirements

  • Python 3.7+
  • Flutter/Dart project with pubspec.yaml
  • Android and/or iOS targets
  • Run scripts from the project root directory

Comprehensive security analysis for Flutter and mobile applications based on OWASP Mobile Top 10 (2024).

Automated Scanners

Four Python scanners cover the most automatable risk categories. Replace <skill-dir> with the skill's install path (e.g. ~/.claude/skills/owasp-mobile-security-checker):

M1 — Hardcoded Secrets

python3 <skill-dir>/scripts/scan_hardcoded_secrets.py /path/to/project

Detects API keys, tokens, passwords, AWS credentials, and Firebase keys in Dart code and config files.

M2 — Dependency Vulnerabilities

python3 <skill-dir>/scripts/check_dependencies.py /path/to/project

Analyzes pubspec.yaml for outdated packages, any version constraints, and known CVEs.

M5 — Network Security

python3 <skill-dir>/scripts/check_network_security.py /path/to/project

Checks HTTP vs HTTPS usage, certificate pinning, Android Network Security Config, and iOS ATS settings.

M9 — Insecure Storage

python3 <skill-dir>/scripts/analyze_storage_security.py /path/to/project

Identifies unencrypted SharedPreferences, plaintext file storage, unencrypted databases, and insecure backup configurations.

Manual Analysis

M3, M4, M6, M7, M8, and M10 require code review. See references/owasp_mobile_top_10_2024.md for Flutter-specific vulnerability patterns, attack flows, and remediation for each category.

Workflow

Is this a comprehensive audit?
├─ YES → Run all 4 scanners → Review JSON outputs → Manual analysis (M3/M4/M6/M7/M8/M10) → Generate report
└─ NO → Continue...

Specific risk category?
├─ M1 → scan_hardcoded_secrets.py
├─ M2 → check_dependencies.py
├─ M5 → check_network_security.py
├─ M9 → analyze_storage_security.py
└─ M3/M4/M6/M7/M8/M10 → references/owasp_mobile_top_10_2024.md → manual analysis

Quick pre-release check?
└─ YES → Run all 4 scanners → Fix CRITICAL and HIGH findings only

Quick Start: Full Audit

# Run all automated scanners from the project root
python3 <skill-dir>/scripts/scan_hardcoded_secrets.py .
python3 <skill-dir>/scripts/check_dependencies.py .
python3 <skill-dir>/scripts/check_network_security.py .
python3 <skill-dir>/scripts/analyze_storage_security.py .

# Outputs produced:
#   owasp_m1_secrets_scan.json
#   owasp_m2_dependencies_scan.json
#   owasp_m5_network_scan.json
#   owasp_m9_storage_scan.json

1. Prioritise by severity — fix CRITICAL and HIGH before release 2. For M3, M4, M6, M7, M8, M10 — see references/owasp_mobile_top_10_2024.md 3. Generate remediation plan with code examples and timeline

OWASP Mobile Top 10 (2024) — Quick Reference

RiskIssueAutomated?Key Check
M1Hardcoded credentials✅ scannerAPI keys, tokens in source/config
M2Vulnerable dependencies✅ scannerOutdated or unconstrained packages
M3Weak authenticationManualToken storage, MFA, session expiry
M4Input validationManualSQL injection, XSS in WebViews, IDOR
M5Insecure communication✅ scannerHTTP usage, missing cert pinning
M6Privacy violationsManualPII in logs/analytics, excess permissions
M7No binary protectionsManualMissing --obfuscate, no root detection
M8MisconfigurationManualDebug flags in production, verbose logging
M9Insecure storage✅ scannerSensitive data in SharedPreferences
M10Weak cryptographyManualMD5/SHA1/ECB usage, hardcoded keys

Understanding Scan Results

SeverityMeaningAction
CRITICALExploitable immediatelyFix now — do not release
HIGHSignificant vulnerabilityFix before release
MEDIUMShould be addressedPlan for next sprint
LOWBest practice improvementAddress as time permits

Common False Positives

  • M1: Test/example keys, placeholders like YOUR_API_KEY
  • M2: Dev-only dependencies (linters, test tools)
  • M5: HTTP for localhost/127.0.0.1 in development
  • M9: Non-sensitive data in SharedPreferences (theme preference, language)

Always verify findings in context before flagging as vulnerabilities.

When NOT to Use

  • Web application security audits — this skill is mobile/Flutter-specific
  • Backend API or server security reviews
  • As a substitute for professional penetration testing or a formal security audit
  • Projects that do not use Flutter/Dart or pubspec.yaml

Reference Documentation

references/owasp_mobile_top_10_2024.md provides per-risk detail:

  • Real-world attack scenarios and examples
  • Flutter-specific vulnerability patterns (Dart code)
  • Insecure vs secure code examples
  • Platform-specific guidance (Android Keystore/NSC, iOS Keychain/ATS)
  • Full mitigation strategies

Integration Points

StageAction
Pre-commitRun scan_hardcoded_secrets.py as a lightweight secrets gate
Pull requestsRun all 4 scanners, post findings as PR comment
Release buildsFull audit including manual analysis for all 10 categories
Incident responseRun targeted scanner for the reported vulnerability category

Related skills

Securityappsecaudit

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.