firebase-supabase-attack

Probe Firebase and Supabase backends for publicly exposed data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of identifying and exploiting publicly accessible Firebase and Supabase backend services that lack proper access controls, which are a leading source of large-scale data breaches in modern web applications using Backend-as-a-Service platforms.

Core Features & Use Cases

  • Extracts Firebase and Supabase configuration credentials from JavaScript bundles and source code leaks to identify target backend instances.
  • Tests for public access to Firestore databases, Cloud Storage buckets, and Authentication endpoints for Firebase, and enumerates Supabase REST API tables, tests CRUD operations, and checks for open signup flows when Row Level Security is misconfigured.
  • Use Case: For a target delivery platform using Firebase, this Skill can confirm if 200,000+ customer conversation records, store data, and audio files are publicly readable without authentication, as validated in real-world pentest engagements.

Quick Start

Use the firebase-supabase-attack skill to probe a target domain for exposed Firebase or Supabase backend data after extracting the platform configuration from the site's JavaScript bundles.

Frequently Asked Questions about firebase-supabase-attack

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

FAQPage Schema
How do I test Firebase Firestore databases for public access without user credentials?

Testing Firebase Firestore for public access involves probing exposed configuration credentials extracted from JavaScript bundles to validate unauthenticated read access to collections. This confirms whether misconfigured backend services allow retrieval of user data without valid authentication.

What is the best way to enumerate Supabase REST API tables during penetration testing?

Enumerating Supabase REST API tables requires testing CRUD operations against the backend endpoints using extracted configuration keys. This identifies misconfigured Row Level Security policies that expose database records and allow open signup flows without valid user credentials.

How does reconnaissance of JavaScript bundles expose Backend-as-a-Service configuration credentials?

Reconnaissance of JavaScript bundles exposes Backend-as-a-Service configuration by analyzing source code leaks for hardcoded Firebase and Supabase API keys. Finding these credentials allows penetration testers to identify target backend instances and test for misconfigured public access.

Can I check Firebase Cloud Storage buckets and authentication endpoints for data breaches without logging in?

Checking Firebase Cloud Storage buckets and authentication endpoints without logging in is possible by probing the backend services with extracted configuration credentials. This validates whether stored files and auth flows are publicly accessible due to missing access controls.

When do I need to probe BaaS platforms for misconfigured Row Level Security?

Probing BaaS platforms for misconfigured Row Level Security is needed when auditing modern web applications for data breaches. It validates if misconfigured Supabase and Firebase services expose sensitive user records and stored files to unauthenticated public access.