supabase

Detect misconfigurations and vulnerabilities in Supabase deployments.

846|152|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill supabase-xalgord
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/technologies/supabase
Command: npx skills add https://github.com/xalgord/xalgorix --skill supabase-xalgord

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies misconfigurations and security gaps in Supabase projects that lead to unauthorized data access, tenant isolation failures, leaked service_role keys, unsafe RPCs, exposed storage, and Edge Function token misuse. It helps security engineers find practical attack vectors across REST/PostgREST, GraphQL, Realtime, Storage, Auth, and Edge Functions so vulnerabilities can be fixed before abuse.

Core Features & Use Cases

  • RLS and Tenant Isolation Testing: Checks missing or overly permissive Row Level Security policies, tenant filters, and IDOR patterns across select, insert, update, and delete actions.
  • PostgREST / RPC Auditing: Exercises filters, embeds, RPC endpoints (SECURITY DEFINER vs INVOKER), and mass-assignment vectors to reveal function-level bypasses.
  • Storage & Signed URL Analysis: Discovers public buckets, listing leaks, signed URL misuse, content-type abuse, and path normalization issues.
  • Edge Function & Auth Validation: Verifies Edge Functions do not expose service_role keys, enforce JWT issuer/audience, and avoid reflected secrets in responses.
  • Realtime & GraphQL Checks: Tests channel guards, subscription isolation, GraphQL overfetching, and schema-introspection risks.
  • Use Case: Security teams running a penetration test or CI security gate can use this Skill to map endpoints, validate principals (anon/user/admin), and produce minimal reproducible requests demonstrating unauthorized access.

Quick Start

Run a Supabase security sweep against https://example.supabase.co to detect RLS misconfigurations, exposed service_role keys, insecure storage buckets, unsafe RPCs, and Edge Function token misuse.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I test Supabase Row Level Security policies for bypass vulnerabilities?

Test Supabase RLS bypasses by validating tenant isolation and IDOR patterns across select, insert, update, and delete actions using anon, user, and admin principals. This identifies missing or overly permissive policies that lead to unauthorized data access during security audits.

How can I check if my Supabase service_role keys are leaked in edge functions?

Check for leaked Supabase service_role keys by scanning Edge Function artifacts and responses for reflected secrets. Verify that functions enforce JWT issuer and audience binding to prevent token misuse and unauthorized admin-level API access.

What is the best way to audit Supabase storage buckets for public access misconfigurations?

Audit Supabase storage by testing for public buckets, listing leaks, signed URL misuse, content-type abuse, and path normalization issues. This reveals insecure storage policies and exposed objects during penetration tests.

How do I pentest Supabase PostgREST RPC endpoints for security flaws?

Pentest Supabase PostgREST by exercising filters, embeds, and mass-assignment vectors against RPC endpoints. Validate SECURITY DEFINER versus INVOKER semantics to reveal function-level privilege bypasses and unsafe remote procedure calls.

Can I run a CI security gate to validate Supabase Realtime and GraphQL channel guards?

You can run CI security gates to validate Supabase Realtime channel guards, subscription isolation, GraphQL overfetching, and schema-introspection risks. This ensures tenant separation and prevents unauthorized data subscriptions in automated pipelines.

Why does my Supabase security sweep fail to detect insecure PostgREST filter behavior?

A Supabase security sweep might miss insecure PostgREST filter behavior if it does not exercise embedding vectors or validate principal context across anon, user, and admin roles. Proper sweeps map endpoints and produce minimal reproducible requests demonstrating unauthorized access.