Загрузка видео...

Не удалось загрузить видео

На главную

🏴‍☠️this is how your vibecoded app gets hacked... let's hack a website together i'll show you why "trusting client" fallacy can cost you 1000s of dollars thread to learn how to avoid this:

236,017 просмотров • 10 месяцев назад •via X (Twitter)

Комментарии: 44

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

rule #1: treat every client as hostile never trust roles, prices, user ids, flags, or limits coming from the frontend. the client only requests. the server decides.

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

rule #2: enforce everything server side auth, authorization, validation, rate limits. recalculate sensitive values. check ownership. assume requests can be replayed, modified, or forged.

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

rule #3: ui restrictions are not security hidden buttons, disabled inputs, and “this won’t be called” assumptions do nothing. if it matters, enforce it on the backend.

Фото профиля Michael Stan
Michael Stan10 месяцев назад

Rule #1 should be tattooed on every founder's forehead. I trusted my retail system's frontend validation in 2015. "Nobody would manipulate inventory counts through the browser, right?" Wrong. Lost £14k to a single compromised session before I caught it. Server-side everything. No exceptions. Ever.

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

wow 🤯 sorry to hear that. an expensive lesson

Фото профиля ronald jabouin
ronald jabouin10 месяцев назад

I found a similar trick on an AI tool. They gave non logged in users a few free uses but the endpoint was unprotected, so I could run it as many times as I wanted via the API

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

number of apps with these critical vulnerabilities is insane

Фото профиля OKTRA
OKTRA10 месяцев назад

Server side validation has to be done

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

non negotiable

Фото профиля bmj🐂🀄️
bmj🐂🀄️10 месяцев назад

Dropped a follow. would love to ask a few questions about an app I’m building if possible🙏🏼

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

feel free to ask them here if they are not private so others can benefit as well if they are, my dms are open

Фото профиля viswC
viswC10 месяцев назад

im going to use rule #2 to tell claude to remove these if vulnerablities exist. thanks

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

💪

Фото профиля Can (ジャン)
Can (ジャン)10 месяцев назад

Yeah, I feel like this was engraved to me in college and masters by our professors. So these kind of secure coding practices feels like second nature now.

Фото профиля yotam
yotam10 месяцев назад

Was just thinking about how valuable it is for someone to do what you’re doing in this way, thanks for this Amazing lessons Would be cool to see your vibe coding approach to security for non tech users of Claude maybe in the form of a SKILL

Фото профиля Eduardo Borges
Eduardo Borges10 месяцев назад

very cool, but I think AI will do a better job than humans tbh AI knows client is not safe (at least recent models like opus 4.5 are good at protecting it) and even if a few models might still fail, it’s just a matter of time (months) for vibe coding be safer than any manual senior dev coding just like tesla cars will be safer than regular ones, they are less prone to errors when tired

Фото профиля Nathan
Nathan10 месяцев назад

Good breakdown. So how do you fix this? Send a check to your auth base and check how many credits that user has before firing?

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

client sends a request to backend to start generation backend checks the database to see if user has an active subscription and enough credits if so, backend starts the generion frontend must be as dumb as possible. just shows stuff on UI and makes requests, not decisions

Фото профиля Nathan
Nathan10 месяцев назад

Legend, thanks for clarifying. Created my first app last week, 99% sure it's set like that.

Фото профиля Ben
Ben10 месяцев назад

This is more about basic programming knowledge than vibe coding per se. The backend should always be in control. Basic.

Фото профиля max (hey)
max (hey)10 месяцев назад

flabbergasting how people miss this. ALWAYS restrict sensitive database actions to backend only. As a rule of thumb, backend methods can only be called form the backend. If you need changes, pass the data from the front end, validate, and let your backend execute.

Фото профиля stexz
stexz10 месяцев назад

tbh, i never seen opus 4.5 make an mistake of sending user_subscription_type in json payload might me different model built this, no security modals still giving security prompt to model is better

Фото профиля Jurre
Jurre10 месяцев назад

So happy you are sharing these insights! Thanks:)

Фото профиля Burak Eregar
Burak Eregar10 месяцев назад

ahh hearing this makes me happy 😊

Фото профиля ManuAlzuru🥑
ManuAlzuru🥑10 месяцев назад

Really good tip. Just followed you! The prompt should include something like: always validate permissions on the server side before executing any service.

Фото профиля Sam
Sam10 месяцев назад

Great advice! For my mobile apps I keep all the credit tracking/consuming server side

Фото профиля Alex
Alex10 месяцев назад

i learned such thing while i vibecode, and from AI, as once i have started my apps, from the very beginning AIs told me and insisted on using server-side auth, middleware, etc which they did properly (i hope :) ). Still not fininshed apps, but initial security seems decent and i can't imagine launching without properly checking it. Good video and explanation👍

Фото профиля Mike Baptiste
Mike Baptiste10 месяцев назад

Great post. Thank you. How do we secure our vibe coded apps from this type of hacking?

Фото профиля Elton John Wayne Gretzky
Elton John Wayne Gretzky10 месяцев назад

Don't let amateur ignorant people use AI tools for vibe coding because then they believe they're better than actual professional devs. Or do it, I'm not your mom.

Фото профиля AlexTheBuilder
AlexTheBuilder10 месяцев назад

Actually vibe coding prevents this if you use good models it will not do it client side

Фото профиля HarwoodLabs
HarwoodLabs10 месяцев назад

Client side validation is UX, not security. Every input field is a potential injection point, every form submission an attack vector. Defense starts at the server boundary, not the browser.

Фото профиля Michael
Michael10 месяцев назад

Thats why you do verification on Server, not on frontend 😂😂

Фото профиля Brandon Veiseh
Brandon Veiseh10 месяцев назад

Great video, a lot of people have these issuws @mindfort agents do this for your app continuously

Фото профиля Jb
Jb9 месяцев назад

the backend is what you should validate therefore if someone messes with your frontend code it doesnt matter

Фото профиля B
B10 месяцев назад

That website UI’s deserved to be hacked

Фото профиля Ant Mancini
Ant Mancini10 месяцев назад

Dropped a follow. Security has been one area I’m constantly working on being militant about.

Фото профиля David Attias
David Attias10 месяцев назад

how come every post you make goes viral?

Фото профиля kolzuki
kolzuki10 месяцев назад

thats why you set a env

Фото профиля Scott (Human) - 𐌃𐌏ᖇ𐌉乙乙𐌃𐌕
Scott (Human) - 𐌃𐌏ᖇ𐌉乙乙𐌃𐌕10 месяцев назад

Joke's on you, buddy. Try hacking my website I just created. I dare you. I vibe-coded it to be protected online. Ai assures me you wont get access.

Фото профиля Suar
Suar10 месяцев назад

This is exactly why programming fundamentals matter before vibe coding

Фото профиля Esteban Feldman
Esteban Feldman10 месяцев назад

In Game development this is called Authoritative Server.

Фото профиля MaverickOps
MaverickOps10 месяцев назад

If anyone thinks vibe coding understands secure coding, you are all sadly mistaken.

Фото профиля The Open Web JP
The Open Web JP9 месяцев назад

This is crazy, it is such basic server security.

Фото профиля Waner Peña
Waner Peña10 месяцев назад

Those validations should ALWAYS happen on the server side.

Похожие видео