The "Human-Layer" Firewall: Why I'm building ScamShield

Hey everyone, I’m Khalil. For the last few months, I’ve been obsessed with a single statistic: 90% of data breaches are caused by social engineering.

As developers, we’ve gotten really good at hardening the stack. We have automated dependency scanning, robust OAuth, and encrypted databases. But while our code is getting harder to hack, our users are getting easier to manipulate.

I’m building ScamShield because traditional antivirus is a reactive relic. It scans for "bad files," but today’s most dangerous threats are "bad conversations." With the explosion of AI-generated phishing, scammers don't need a virus—they just need to vibe their way into a user's trust using high-pressure tactics.

The Vision

ScamShield moves beyond the hardware to protect the person. It’s a sophisticated heuristics engine that identifies the linguistic markers of social engineering—urgency, fear, and authority—in real-time.

• The Goal: A "set-it-and-forget-it" guardian for families, seniors, and non-tech-savvy users.

• The Differentiator: Our competitors protect your PC; we protect you.

The Tech Stack

I’m building this in the Next.js and TypeScript ecosystem, utilizing vibe coding to rapidly iterate on the analysis engine. I’ve just finished a Chrome Extension that allows users to send suspicious text directly to our analysis HUD for a "sanity check."

What's Next?

I’m currently looking for early feedback on our "Human-Layer" approach. If you’ve ever had to help a family member recover an account because of a "Verify Identity" scam, I’d love to chat