Sabitlenmiş Tweet
Don Cristos
2.1K posts

Don Cristos
@CristosDon
Full stack web developer: JavaScript (reactjs nodejs), PHP (Laravel)🌞🌞 HTML 🌞🌞CSS. And fast learning always derived with curiosity to learn and team work.
Lagos, Nigeria Katılım Nisan 2018
1.1K Takip Edilen396 Takipçiler

3️⃣ Anonymize: Keep financial records for tax, but scrub PII.
Distributed systems require distributed cleanup. 🛠️ #SaaS #Backend #SystemDesign
English

@Akintola_steve Redis, database jwt.
Store the session on the database use redis for quick access catching,
English

@MrOlibaba Hmm
Wait let me get they don't pay or they have bad culture
English

@CristosDon @joni_vrbt Everything. All of it. You in?
English

@just_andydev Oo yes as a file but we can write logic to exclude . Env files from the project or specifically informed AI not to include it. But it's a security flaw that needs to be addressed
English

@CristosDon This vulnerability goes beyond that.
I've tested this after I made the tweet I ask claude to create a project and they all had the .env file passed to the frontend container. It's a major security flaw
English

AI is building insecure apps and founders are paying for it. Literally.
I just spent 10 hours debugging a client's AWS server. They got a $3000 bill because of a vulnerability AI introduced and never flagged.
If you are running Next.js and Docker, do this right now.
1. Check if you are on Next.js below version 16.2.4
2. Confirm with your dev if your entire .env file is being passed to Next.js via Docker
3. Ask AI to scan your project for RSC vulnerabilities that allow attackers to access your nextjs server
This is especially critical if AI built your project or you are vibe coding.
LLMs are backdated. They do not always use the latest, most secure versions.
If AI created your containers, ask it to check for RSC vulnerabilities immediately.
If the vulnerability exists, rotate all your env files and consider taking the server down entirely.
Everything on a compromised server should be treated as exposed.
Do not wait.
English

@CaptainInsightX With my years of experience checking logs first to get the actual error but timeouts are usually caused by external dependency. Especially if you are on vpc
English

@gozkybrain4u I usually have these issues most of my works based on strict NDA and don't know what to do
English

@Gamingtronium Relying on IP addresses is insufficient because of proxy rotation. In production, I would implement Layer 7 rate limiting keyed by User IDs or API Keys. For unauthenticated traffic, I’d use Device Fingerprinting and TLS JA3 signatures to identify unique clients.
English














