analyze-apk
Full security analysis of an Android application — from APK to report
v2026.7.31-4eb5d2f4 installs+4 in 7 days76 StarsMITsynced 12 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install theqmaks/analyze-apkWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package85ed26de…9b394839
85ed26debe97…55809b3948391 file · 2.5 KBScanHigh1 finding
- injection.system_promptSKILL.md:91
Sourcegithub.com/TheQmaks/areclaw/tree/main/.claude/skills/analyze-apk@4eb5d2f
On this page
You are performing a comprehensive security analysis. Think, don't checklist.
Input
$ARGUMENTS— either a package name (com.example.app) or path to APK file
Phase 1: Acquisition
If given a package name (not a file path):
# Option A: Pull from device (if connected)
adb shell pm path $ARGUMENTS
adb pull <path> workspace/samples/
# Option B: Download from store (no device needed)
justapk download $ARGUMENTS -o workspace/samples/If given a file path, use directly.
Set $APK = path to the APK file, $PKG = package name.
Phase 2: Reconnaissance — DETERMINE WHAT YOU'RE DEALING WITH
This phase determines your entire strategy. Do not skip.
# 1. Protection detection
apkid $APK
# 2. Check native libraries
unzip -l $APK | grep '\.so' | head -20
# 3. Check assets for framework indicators
unzip -l $APK | grep -E 'flutter|react|index\.android\.bundle|il2cpp|global-metadata'
# 4. Quick manifest check
java -jar tools/apktool/apktool.jar d -s -f -o /tmp/apk_quick $APK
# Read AndroidManifest.xmlDECIDE based on findings:
- Flutter → Focus on network interception, limited static analysis of Dart
- React Native → Extract and analyze JS bundle, check for Hermes bytecode
- Unity/IL2CPP →
tools/il2cppdumper/Il2CppDumper.exe libil2cpp.so global-metadata.dat output/+ Ghidra with recovered symbols - Packed → Use
clsdumperto dump DEX first, then proceed - Native Java/Kotlin → Full static + dynamic analysis
- Heavy obfuscation → Identify obfuscator, try
simplifyfirst (java -jar tools/simplify/simplify.jar -i app.apk -o clean.apk), then java-deobfuscator/threadtear
Phase 3: Static Analysis
3a. Decompilation
# Primary: jadx
jadx -d workspace/output/$PKG --deobf --show-bad-code $APK
# Resources + smali: apktool
java -jar tools/apktool/apktool.jar d -o workspace/output/$PKG-smali $APKIf packed and clsdumper was used, decompile the dumped DEX instead.
3b. Manifest Analysis
Read AndroidManifest.xml and analyze:
- Permissions: List all, flag dangerous ones, check for custom permissions
- Exported components: Activities, Services, Receivers, Providers with
exported="true"or intent-filters (implicit export) - Flags:
debuggable,allowBackup,usesCleartextTraffic,networkSecurityConfig - Deep links:
<intent-filter>withandroid.intent.action.VIEW+<data>elements - Target/Min SDK: Security implications of SDK versions
3c. Secret Scanning
# Step 1: apkleaks — fast APK-level scan
apkleaks -f $APK --json -o workspace/reports/$PKG-secrets.json
# Step 2: trufflehog — deep scan on decompiled source (800+ secret types, validates if live!)
tools/trufflehog/trufflehog.exe filesystem workspace/output/$PKG/ --jsonThen search decompiled source using expert patterns from the agent reference. Focus on: API keys, hardcoded credentials, Firebase configs, cloud service keys.
For every secret found: determine scope and impact. trufflehog validates automatically — check its output for verified credentials.
3d. API Mapping
Find all network endpoints:
- Retrofit interfaces (annotations)
- OkHttp interceptors (base URL)
- URL constants in strings/resources
- WebSocket endpoints
Build endpoint table: Method | Path | Auth Required | Request Model | Response Model
3e. Security Audit
Walk through patterns:
- Cryptography: weak algorithms, hardcoded keys, predictable IVs
- WebView: JavaScript enabled + interface exposure
- Data storage: SharedPrefs, SQLite, files — what's sensitive?
- IPC: Exported components without permissions
- Logging: Sensitive data in Log calls
Phase 4: Dynamic Analysis (if device connected)
Only if device is available (adb devices shows device):
# If app detects Frida (crashes on attach), use phantom-frida:
# Read tools/phantom-frida/build-info.json for <NAME> and <PORT>
# adb push tools/phantom-frida/<NAME>-server /data/local/tmp/<NAME>-server
# adb shell chmod 755 /data/local/tmp/<NAME>-server && adb shell /data/local/tmp/<NAME>-server -D &
# adb forward tcp:<PORT> tcp:<PORT>
# Then use: frida -H 127.0.0.1:<PORT> instead of frida -U
# Check root detection
frida -U -f $PKG -l workspace/frida-scripts/root-bypass.js
# Monitor crypto (reveals actual keys/algorithms in use)
frida -U -f $PKG -l workspace/frida-scripts/crypto-tracer.js
# Monitor SharedPrefs (reveals actual stored data)
frida -U -f $PKG -l workspace/frida-scripts/shared-prefs-monitor.js
# Check actual stored data on device
adb shell run-as $PKG ls shared_prefs/
adb shell run-as $PKG ls databases/Phase 5: Report
Generate report at workspace/reports/$PKG-$(date +%Y-%m-%d).md following the report format in the agent reference.
Critical: The report must show chain of reasoning, not just findings. Each finding should explain WHY it matters and WHAT an attacker could do with it.
Files in this version
- SKILL.md5.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | Yes | Yes |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- HighPrompt injection · injection.system_promptSKILL.md:91
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.7.31-4eb5d2f | Nov 13, 2026 | 4eb5d2f | 85ed26de | Signed | – |
More from TheQmaks
All from this publisherMore in Mobile, firmware and hardware
See the category- apk-reversezhaoxuya520/apk-reverse5
- ai-mobile-reverse-skillsfausto-404/ai-mobile-reverse-skills5
- open-apk1013503897/open-apk4
- performing-mobile-device-forensics-with-cellebritemukul975/performing-mobile-device-forensics-with-cellebrite4
- mobile-reversezhaoxuya520/mobile-reverse3
- performing-android-app-static-analysis-with-mobsfmukul975/performing-android-app-static-analysis-with-mobsf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login