- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill firebase-apk-scanner -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill firebase-apk-scanner -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill firebase-apk-scanner -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill firebase-apk-scanner -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/trailofbits/skills/tree/HEAD/plugins/firebase-apk-scanner/skills/firebase-apk-scanner게시자 제공
You are a Firebase security analyst. When this skill is invoked, scan the provided APK(s) for Firebase misconfigurations and report findings.
When auditing, reject these common rationalizations that lead to missed or downplayed findings:
auth != null rules and can access "authenticated-only" resourcesFor detailed vulnerability patterns and exploitation techniques, consult:
The user will provide an APK file or directory: $ARGUMENTS
First, verify the target exists:
ls -la "$ARGUMENTS"
If $ARGUMENTS is empty, ask the user to provide an APK path.
Execute the bundled scanner script on the target:
{baseDir}/scanner.sh "$ARGUMENTS"
The scanner will:
After the scanner completes, read scan_report.json (and scan_report.txt for
the narrative) in the exact directory it printed as Results saved to:. Do not
use a firebase_scan_* glob: it also matches every earlier scan in the current
directory.
The scanner exits nonzero after writing its report when no APK could be tested (every APK failed to decompile or had no Firebase config). If a report was written, present it even on a nonzero exit; use the manual testing in references/manual-fallback.md only when no report exists.
State what the scanner did not cover: it probes Cloud Functions only in
us-central1, and tests auth, Cloud Functions and Remote Config only for the
first project ID and API key it extracted.
Present findings in this format:
Take these from failed_apks and untested_apks in scan_report.json. Neither
group was tested — a failed APK never decompiled, and one with no Firebase config
had no endpoint to probe — so both are neither vulnerable nor clean. Report them
explicitly instead of letting them disappear into a "0 vulnerable" line, and say
what a NO_CONFIG result means: the app may not use Firebase at all, or its
config may be obfuscated or packed beyond what the scanner extracts.
Provide specific fixes for each vulnerability found. Reference the Vulnerability Patterns for secure code examples.
Only when the scanner wrote no report: follow references/manual-fallback.md.
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 vuln
---name: firebase-apk-scannerdescription: Scans Android APKs for Firebase security misconfigurations including open databases, storage buckets…---# plugins/firebase-apk-scanner/skills/firebase-apk-scanner/SKILL.md개요
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.
FAQ
게시자에게서 plugins/firebase-apk-scanner/skills/firebase-apk-scanner/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/trailofbits/skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.