hunt-firebase

Detect exposed Firebase API keys and GCP service account credentials in client-side assets.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill hunt-firebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-firebase
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/hunt-firebase
Command: npx skills add https://github.com/uphiago/recon-skills --skill hunt-firebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Firebase and GCP services are frequently misconfigured by developers, leading to critical public exposure of sensitive user data, unauthorized access to cloud resources, and full GCP compromise when API keys or service account credentials are leaked in client-side assets or exposed configuration files.

Core Features & Use Cases

  • Firebase Asset Discovery: Locates Firebase API keys in JS bundles, source maps, .env files, and public config endpoints, plus identifies Firebase service endpoints across target infrastructure.
  • Multi-Service Exploitation: Tests and exploits misconfigurations in Firestore, Realtime Database, Firebase Storage, Firebase Auth, and GCP IAM to extract data, gain write access, or escalate privileges.
  • GCP Service Account Abuse: Leverages leaked GCP service account JSON keys to enumerate IAM policies, access cloud resources, and export sensitive data via gcloud CLI.
  • Use Case: A penetration tester assessing a healthcare mobile app can use this skill to extract a Firebase API key from the app's JS bundle, then dump all public Firestore collections containing patient PII to demonstrate a critical data breach.

Quick Start

Use the hunt-firebase skill to scan a target's public web and mobile assets for exposed Firebase API keys and validate if associated Firestore databases are publicly readable.

Frequently Asked Questions about hunt-firebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find exposed Firebase API keys during a penetration test?

To validate Firebase misconfigurations like public Firestore read access, extract the Firebase API key from the target's client-side assets and attempt to query the associated database directly. This confirms unauthorized data exposure and open access rules quickly.

What Firebase misconfigurations can be exploited using extracted API keys?

Firebase misconfigurations that can be exploited using extracted API keys include public Firestore and Realtime Database read or write access, open Firebase Auth sign-up endpoints, and exposed GCP service account keys allowing IAM policy enumeration and privilege escalation.

Does this Firebase security testing approach work for mobile app assessments?

Yes, this Firebase security testing approach works for mobile app assessments by extracting Firebase API keys and GCP service account credentials from mobile app assets. It targets organizations using Firebase, Firestore, Realtime Database, or GCP cloud infrastructure to validate critical data exposure.

Can I use leaked GCP service account keys to enumerate IAM policies?

You can use leaked GCP service account JSON keys to enumerate IAM policies and access cloud resources by leveraging the gcloud CLI. This allows testers to export sensitive data and demonstrate full GCP compromise during offensive security engagements.

When should I test for Firebase Realtime Database public access?

You should test for Firebase Realtime Database public access when an organization uses Firebase services and exposes API keys in client-side code. Validating these misconfigurations prevents unauthorized data extraction and identifies critical security breaches.