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.