Back to catalog
Static reviewDevelopment

Skill dossier

performing-android-app-static-analysis-with-mobsf

Source declaration

Performs automated static analysis of Android applications using Mobile Security Framework (MobSF) to identify hardcoded secrets, insecure permissions, vulnerable components, weak cryptography, and code-level security flaws without executing the application. Use when assessing Android APK/AAB files for security vulnerabilities before deployment, during penetration testing, or as part of CI/CD security gates. Activates for requests involving Android static analysis, MobSF scanning, APK security assessment, or mobile application code review.

The author's original description, preserved in English. It describes intent, not verified performance.

Performs automated static analysis of Android applications using Mobile Security Framework (MobSF) to identify hardcoded secrets, insecure permissions, vulnerable components, weak cryptography, and code-level security flaws without executing the application. Use when assessing Android APK/AAB files for security vulnerabilities before deployment, during penetration testing, or as part of CI/CD security gates. Activates for requests involving Android static analysis, MobSF scanning, APK security assessment, or mobile application code review.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Performs automated static analysis of Android applications using Mobile Security Framework (MobSF) to identify hardcoded secrets, insecure permissions, vulnerable components, weak cryptography, and code-level security flaws without executing the application. Use when assessing Android APK/AAB files for security vulnerabilities before deployment, during penetration testing, or as part of CI/CD security gates. Activates for requests involving Android static analysis, MobSF scanning, APK security assessment, or mobile application code review. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L55]
  • Step 1: Deploy MobSF and Obtain API Key [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L57]
  • Step 2: Upload APK for Static Analysis [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L67]
  • Step 3: Trigger and Retrieve Static Scan Results [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L78]
  • Step 4: Analyze Critical Findings [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L94]
  • Step 5: Generate and Export Reports [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L119]
  • Step 6: Integrate into CI/CD Pipeline [Source statement; provisional, not tested. Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L135]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
51 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-android-app-static-analysis-with-mobsf/assets/template.mdReference3.6 KB
skills/performing-android-app-static-analysis-with-mobsf/LICENSEOther11 KB
skills/performing-android-app-static-analysis-with-mobsf/references/api-reference.mdReference5.5 KB
skills/performing-android-app-static-analysis-with-mobsf/references/standards.mdReference2.9 KB
skills/performing-android-app-static-analysis-with-mobsf/references/workflows.mdReference3.7 KB
skills/performing-android-app-static-analysis-with-mobsf/scripts/agent.pyScript9 KB
skills/performing-android-app-static-analysis-with-mobsf/scripts/process.pyScript8.1 KB
skills/performing-android-app-static-analysis-with-mobsf/SKILL.mdInstruction7.2 KB

SKILL.md frontmatter

{
  "name": "performing-android-app-static-analysis-with-mobsf",
  "description": "Performs automated static analysis of Android applications using Mobile Security Framework (MobSF) to identify hardcoded secrets, insecure permissions, vulnerable components, weak cryptography, and code-level security flaws without executing the application. Use when assessing Android APK/AAB files for security vulnerabilities before deployment, during penetration testing, or as part of CI/CD security gates. Activates for requests involving Android static analysis, MobSF scanning, APK security assessment, or mobile application code review.\n",
  "domain": "cybersecurity",
  "subdomain": "mobile-security",
  "author": "mahipal",
  "tags": [
    "mobile-security",
    "android",
    "mobsf",
    "static-analysis",
    "owasp-mobile",
    "penetration-testing"
  ],
  "version": "1.0.0",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "PR.AA-05",
    "ID.RA-01",
    "DE.CM-09"
  ],
  "mitre_attack": [
    "T1059",
    "T1056",
    "T1036",
    "T1078"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Deploy MobSF and Obtain API Key

    Source-described action candidate under “Step 1: Deploy MobSF and Obtain API Key”; not verified execution.

  4. 04
    Input

    Step 2: Upload APK for Static Analysis

    Source-described input candidate under “Step 2: Upload APK for Static Analysis”; not verified execution.

  5. 05
    Input

    Upload the target APK using the MobSF REST API:

    Source-described input candidate under “Step 2: Upload APK for Static Analysis”; not verified execution.

  6. 06
    Action

    Step 3: Trigger and Retrieve Static Scan Results

    Source-described action candidate under “Step 3: Trigger and Retrieve Static Scan Results”; not verified execution.

Inspect all extracted workflow candidates (26 candidate steps)
  1. 07
    Action

    Step 4: Analyze Critical Findings

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  2. 08
    Action

    Exported activities, services, receivers, and content providers without permission guards

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  3. 09
    Action

    `android:debuggable="true"` left enabled

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  4. 10
    Action

    `android:allowBackup="true"` enabling data extraction via ADB

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  5. 11
    Action

    Missing `android:networkSecurityConfig` for certificate pinning

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  6. 12
    Input

    Hardcoded API keys, passwords, and tokens in Java/Kotlin source

    Source-described input candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  7. 13
    Action

    Insecure SharedPreferences usage for storing sensitive data

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  8. 14
    Action

    Weak or broken cryptographic implementations (ECB mode, static IV, hardcoded keys)

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  9. 15
    Action

    Missing certificate pinning configuration

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  10. 16
    Action

    Custom TrustManagers that accept all certificates

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  11. 17
    Action

    Cleartext HTTP traffic allowed without exception domains

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  12. 18
    Action

    Missing ProGuard/R8 obfuscation

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  13. 19
    Action

    Native library vulnerabilities (stack canaries, NX bit, PIE)

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  14. 20
    Action

    Debugger detection absence

    Source-described action candidate under “Step 4: Analyze Critical Findings”; not verified execution.

  15. 21
    Output

    Step 5: Generate and Export Reports

    Source-described output candidate under “Step 5: Generate and Export Reports”; not verified execution.

  16. 22
    Output

    Export findings in multiple formats for stakeholder communication:

    Source-described output candidate under “Step 5: Generate and Export Reports”; not verified execution.

  17. 23
    Action

    Step 6: Integrate into CI/CD Pipeline

    Source-described action candidate under “Step 6: Integrate into CI/CD Pipeline”; not verified execution.

  18. 24
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  19. 25
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  20. 26
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

62 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

25 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 25 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

32 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 32 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

4 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

File deletion is described or implemented

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-android-app-static-analysis-with-mobsf/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/performing-android-app-static-analysis-with-mobsf/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-android-app-static-analysis-with-mobsf
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.