Bolt.new · Next.js · Supabase · Tailwind
Quarantining Leaked Service Keys & Securing Auth in a Fintech MVP
Client: B2B Financial Analytics Platform
Key Metric
100% Vulnerability Remediation
System Reliability
SOC2-Ready Architecture
The Problem & Bottleneck
The founder built an impressive analytics dashboard using Bolt.new. However, during a third-party security review, they discovered that the client-side JavaScript bundle included the Supabase service_role secret key, and Row Level Security (RLS) policies were never configured — allowing any authenticated user to query all tenant databases.
The Technical Solution
A matched Skilancer Principal Engineer immediately rotated the compromised service keys, migrated all sensitive queries from client components to authenticated Server Actions, instituted strict tenant-isolated PostgreSQL RLS policies, and set up automated security linting in CI/CD.
Production Impact
- ✓Zero client-side secrets exposure; zero unauthorized data access.
- ✓Tenant isolation enforced at the PostgreSQL database level.
- ✓Passed founder's investor due diligence technical audit.
- ✓Delivered in 4 business days under a fixed audit & sprint package.