How to not get hacked when vibe coding an app

@swerikcodes

84.7K followers · usually 16.3K views a post

Views

81.9K

Likes

6.6K

Comments

39

Shares

508

Selling · SaaS › Other SaaS

Clerkseen in 5 videos →

Why it worked

The video offers practical, actionable security advice for app developers, addressing common vulnerabilities in a concise and easy-to-understand format. The use of numbered points and clear explanations makes the information digestible and memorable, while the creator's demonstrated experience adds credibility.

Summary

The video provides five key security tips for app developers: implement rate limiting, use production-grade authentication systems like Clerk, Supabase, or Firebase, lock down your database with row-level security, never expose secrets by storing them server-side, and monitor for errors to prevent user impact. Following these steps helps prevent security breaches and ensures a more robust application.

Structure

1Intro and credibility
2Rate limiting
3Production-grade authentication
4Database security
5Secret management
6Monitoring and error alerts

Product placement

Original caption

99% of vibecoded apps don’t have all 5 of these built in, which causes majority security problems… #app #vibecoding #coding #learntocode #softwareengineer

More from @swerikcodes

Their other posts in the index, biggest breakout first.

Clerk: acts as an authentication system for apps. Removing it would change how users log in and sign up. It acts. Supabase: acts as a backend-as-a-service platform, including authentication. Removing it would change how users log in and sign up. It acts. Firebase: acts as a backend-as-a-service platform, including authentication. Removing it would change how users log in and sign up. It acts.

Call to action

Keep on building and follow for more.

On-screen text

How to not get hacked when vibe coding an app 1. Add rate limiting 2. Implementing Production Grade Authentication 3. Lock down your database 4. Never expose your secrets 5. Monitor what's breaking down

Transcript

I've built multiple apps to thousands of users and generated thousands of dollars in revenue. Here's how to not get hacked when vibe coding your app. First, add rate limiting. If someone can open your login, signup, AI, etc. endpoints, they will. So make sure you put limits in place before it becomes a problem that you're actively paying for. Next, implement a production grade authentication. If you're moving fast, use something like Clerk, Supabase, or Firebase auth system, because it works out of the box and you don't have to focus on it. Lock down your database. This is a mistake that I see so many people making. Make sure users can only ever access their own data, using stuff like row-level security or specific scoped permissions. Never expose your secrets. Now this is an obvious one, but I see it all the time: Never expose your secrets. If an API key, private token, or database secret gets leaked, you're exposing your entire app and all of your users to getting hacked. Make sure you're storing all your secrets in a server-side environment variable file. Now finally, it's the most obvious but is often skipped, monitoring what's breaking. Use something like error alerts directly to your inbox, whenever something goes wrong, so you don't actually end up impacting your users. Keep on building and follow for more.