# Looking for someone to audit my Supabase setup + check if signup/referral attribution can be manipulated — retained record

> Retained reddit record from reddit:SaaS.

Canonical: https://highsignal.app/data/records/5036305645e10dc1

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:SaaS)  published 2026-09-20 12:44 ingested 2026-09-21 02:36

[original source ↗](https://www.reddit.com/r/SaaS/comments/1wlg4q6/looking_for_someone_to_audit_my_supabase_setup/)

## retained text



```
I’m looking for someone experienced with **Supabase, Postgres, Next.js, and auth/referral systems** to audit a production project.

The main thing I’m trying to figure out is whether there’s any way users, bots, or another site could be **manipulating signup attribution, referral codes, affiliate parameters, or account creation flows**.

I’ve already found one issue with an external platform where a referral code is visible/autofilled during signup, but using Google OAuth appears to create the account without actually attaching the referrer. That got me wondering whether I could have similar attribution issues or exploitable flows on my own site.

I’d want the audit to look at:

* Supabase Auth signup/login flows
* Google/OAuth callbacks
* Referral code handling before and after signup
* Whether referral parameters can be changed, stripped, overwritten, or spoofed
* Whether someone can create accounts in a way that bypasses referral attribution
* Whether another site could call my public Supabase endpoints directly
* Whether outbound affiliate URLs/parameters can be manipulated
* RLS policies and `anon` / `authenticated` permissions
* Public `/rest/v1/` exposure
* `SECURITY DEFINER` RPC functions
* Anonymous inserts / click tracking
* Bots, scraping, fake signups, or automated account creation
* Any obvious way someone could hijack attribution or make signups appear unattributed
* General Supabase security issues

I’ve also had unusually high Supabase API/egress usage, so I’d like to determine whether that’s normal traffic, bots/scrapers, or someone consuming my API externally.

I can provide relevant code, schema, RLS policies, logs, and auth flow details privately. I will **not** share service-role keys, database passwords, or production secrets.

If you’ve specifically audited **Supabase auth/referral/affiliate systems**, comment or DM me with your experience and what you’d want access to. Paid audit is fine.
```



document fetched 2026-09-21 00:27 · canonical https://reddit.com/r/SaaS/comments/1wlg4q6/looking_for_someone_to_audit_my_supabase_setup
