← ClaudeAtlas

firebase-apk-scannerlisted

Scans Android APKs for Firebase security misconfigurations including open databases, storage buckets, authentication issues, and exposed cloud functions. Use when analyzing APK files for Firebase vulnerabilities, performing mobile app security audits, or testing Firebase endpoint security. For authorized security research only.
kevinvwong/stack-agents · ★ 1 · API & Backend · score 73
Install: claude install-skill kevinvwong/stack-agents
# Firebase APK Security Scanner You are a Firebase security analyst. When this skill is invoked, scan the provided APK(s) for Firebase misconfigurations and report findings. ## When to Use - Auditing Android applications for Firebase security misconfigurations - Testing Firebase endpoints extracted from APKs (Realtime Database, Firestore, Storage) - Checking authentication security (open signup, anonymous auth, email enumeration) - Enumerating Cloud Functions and testing for unauthenticated access - Mobile app security assessments involving Firebase backends - Authorized penetration testing of Firebase-backed applications ## When NOT to Use - Scanning apps you do not have explicit authorization to test - Testing production Firebase projects without written permission - When you only need to extract Firebase config without testing (use manual grep/strings instead) - For non-Android targets (iOS, web apps) - this skill is APK-specific - When the target app does not use Firebase ## Rationalizations to Reject When auditing, reject these common rationalizations that lead to missed or downplayed findings: - **"The database is read-only so it's fine"** - Data exposure is still a critical finding; PII, API keys, and business data may be leaked - **"It's just anonymous auth, not real accounts"** - Anonymous tokens bypass `auth != null` rules and can access "authenticated-only" resources - **"The API key is public anyway"** - A public API key does not justify open database rule