supabase-security
Audited by Socket on Oct 10, 2026
6 alerts found:
Anomalyx3Securityx3No clear malware behavior is present. The primary security issue is an injection risk if result fields, especially summary counts or probe fields, can be attacker-controlled. Validate numeric fields and safely encode all dynamic values for their output context.
The code implements a plausible browser-based Supabase exposure scan, but its weak URL validation can disclose the supplied anon key to an arbitrary host. Unescaped HTML rendering of table and column names also permits injection into the results view. The optional signup sends email and project URL to a third party. These are concrete security and privacy concerns, but the fragment does not show clear malware behavior.
The action's stated audit and migration-lint behavior is plausible, and this YAML provides no evidence of deliberate malware or obfuscation. However, direct shell interpolation of webhook inputs creates command-injection risk, and the floating npx @latest package receives a Supabase access token, adding material supply-chain exposure. Pin the CLI to a reviewed version and pass webhook values through safely quoted environment variables.
No malicious behavior is evident. The grant of all privileges on private.billing to anon is a significant least-privilege concern and should be removed unless explicitly justified; its effective accessibility cannot be determined from this fragment because schema USAGE may be controlled elsewhere.
The principal security issue is an exposed data-disclosure function: anon can execute a SECURITY DEFINER function that returns every user's email address. Restrict execution and/or enforce appropriate row-level filtering. The order totals view also warrants an authorization review. The fragment shows no clear malware behavior.
No malware, credential theft, or destructive behavior is present. The script creates a significant database access-control risk through broad grants, especially unrestricted access to public.notes and public read access to all posts. Review and narrow the privileges and policies before deployment.