Static Analysis of 48 AI-Generated Apps: 90% Had Security Vulnerabilities
A developer recently shared results from running static analysis on 48 public GitHub repos built with Lovable, Bolt, or Replit. The findings: 90% had at least one security vulnerability. The breakdown of issues:
- 44% — authentication gaps: routes unprotected despite a login system
- 33% — Postgres functions marked
SECURITY DEFINER, bypassing row-level security - 25% — BOLA/IDOR: missing ownership checks in database queries
- 25% — committed .env or config files
The auth gap is instructive: AI tools generate working login flows (registration, email verification, sessions, password reset) but often fail to protect individual API routes or pages. The prompt was "build a dashboard with auth" — the LLM built both, but didn't implicitly verify every route is behind a guard. The pattern is systematic, not random.
SECURITY DEFINER is the hidden one: AI tools generate these to resolve permission errors locally. The function runs as DB superuser, bypassing all RLS policies. The app works perfectly locally but is exploitable in production — no error or warning.
The author notes this isn't a Claude-specific problem; it's a constraint of LLMs generating code from "write me a working app" prompts without adversarial thinking.
📖 Read the full source: r/ClaudeAI
👀 See Also

Clawvisor: Purpose-Based Authorization Layer for OpenClaw Agents
Clawvisor is an authorization layer that sits between AI agents and APIs, enforcing purpose-based authorization where agents declare intentions, users approve specific purposes, and an AI gatekeeper verifies every request against that purpose. Credentials never leave Clawvisor and agents never see them.

AI Agent Guardrails Decay Over Time Without Active Maintenance
AI agent guardrails degrade over time as system prompts accumulate updates, model versions change, and new tools are added, often resulting in contradictory or ignored safety rules that require regular review and testing.

Security Analysis of Extracting OpenClaw Components for Custom AI Agents
A developer analyzed OpenClaw's source code to determine which components can be safely extracted for use in custom AI agents, scoring each using the Lethal Quartet framework. The analysis reveals significant security risks in components like Semantic Snapshots and BrowserClaw.
AI Agent Security: Token Budget Determines Data Exfiltration Risk
A developer tested AI agents connected to Gmail: frontier models caught phishing, mid-tier was unstable, cheap models silently forwarded malicious emails. Architectural protections (sandboxing, permissions) stopped zero attempts.