vibe-audit-technique
White-box auditing methodology for AI-generated ('vibe-coded') applications from Lovable, Bolt.new, v0, Cursor, Replit Agent, and Claude Code. Focuses on modern stack misconfigurations (Supabase, Firebase, Next.js, Vercel, Expo).
v2026.11.13-21cd5683 installs+3 in 7 days39 Starssynced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/vibe-audit-techniqueWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package6efdc88e…036744fa
6efdc88ec95e…b488036744fa10 files · 11.7 KBScanHigh3 findings
- injection.ignore_instructionsreferences/ai-integration.md:31
- No license found
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-techniques/vibe-audit-technique@21cd568
On this page
Goal: Identify critical, high-frequency security omissions in modern web/mobile stacks (Next.js, Firebase, Supabase, Vite, Expo) that are typically generated by AI coding assistants (Lovable, Bolt.new, v0, Cursor, Replit Agent, Claude Code).
When this technique applies
- You have source-code access to a modern web application or mobile app backend.
- The stack relies heavily on BaaS (Backend-as-a-Service) like Supabase, Firebase, or Clerk.
- You are reviewing Next.js Server Actions, tRPC routers, React Server Components, or Expo/React Native apps.
- The repo shows AI-generator fingerprints (Lovable/Bolt/v0/Cursor commit messages, one-shot scaffolded migrations,
.cursor/,mcp.json,.bolt/).
Pair with sibling techniques
- For LLM-assisted taint tracing from source to sink across large repos, drive the pass with
offensive-techniques/source-review-technique/SKILL.md. This skill supplies the vibe-code sink catalogue; that skill supplies the AI-assisted data-flow discipline. - Do not re-derive general SAST here.
The Audit Workflow
1. The BaaS Access Control Trap
AI code generators frequently scaffold databases without strict Row-Level Security (RLS). This is the canonical vibe-code failure — see CVE-2025-48757 (Lovable + Supabase, mass RLS-off exposure across hundreds of live apps).
- Check: Are tables missing RLS entirely (default state for
publicschema tables in Supabase)? - Check: Are existing RLS policies set to
USING (true)orUSING (auth.uid() IS NOT NULL)for convenience? - Check: Cross-tenant IDOR — do policies scope to the row owner / organization, or only to "any authenticated user"?
- Action: Load
references/database-security.md. If ORM (Prisma/Drizzle) or raw SQL is layered on top, also loadreferences/data-access.md.
2. The Client-Side Secret Leak
AI often pushes server-side secrets to the client to quickly bypass CORS or backend proxy errors.
- Check: Grep for
NEXT_PUBLIC_,VITE_, orEXPO_PUBLIC_. - Check: Ensure OpenAI, Anthropic, or Stripe secret keys are not bundled in these variables.
- Action: Load
references/secrets-and-env.mdandreferences/ai-integration.md.
3. Server Action / API Auth Bypass
In Next.js, Server Actions are hidden API endpoints. They must be authenticated individually.
- Check: Does the endpoint or Server Action assume the user is trusted simply because middleware exists? Middleware is often bypassed or overly permissive.
- Action: Load
references/authentication.md.
4. Billing and Rate Limits
AI assistants build features, not defenses.
- Check: Are AI query routes (e.g., text generation, image generation) protected by rate limits?
- Check: Are payment webhooks properly verifying signatures?
- Action: Load
references/rate-limiting.mdandreferences/payments.md.
5. Mobile Bundle & Deployment Surface
Expo/React Native apps generated by AI ship with embedded secrets and insecure storage. Vercel/Netlify preview and prod configs are often mixed.
- Check: Any
EXPO_PUBLIC_*referencing a secret key; use ofAsyncStoragefor tokens; deep links used for auth. - Check: Preview deployments sharing production credentials; source maps or
.git/exposed in prod; permissive CORS. - Action: Load
references/mobile.mdfor the bundle surface,references/deployment.mdfor the hosting surface.
Quality Gates
- Context matters: A leaked
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEYis not a vulnerability (it is meant to be public). A leakedSTRIPE_SECRET_KEYis critical. Verify before reporting. - Do not report generic 'missing headers': Focus strictly on the critical gaps caused by "vibe-coding" (Direct DB exposure, unauthorized server actions, secret leakage).
Files in this version
references/925.0 KB
- ai-integration.md2.4 KB
- authentication.md3.3 KB
- data-access.md2.5 KB
- database-security.md5.5 KB
- deployment.md2.0 KB
- mobile.md2.5 KB
- payments.md2.5 KB
- rate-limiting.md2.2 KB
- secrets-and-env.md2.1 KB
- SKILL.md4.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- HighPrompt injection · injection.ignore_instructionsreferences/ai-integration.md:31
- MediumLicense · No license found
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 6efdc88e | Signed | – |
More from AeonDave
All from this publisherMore in AI, agents and MCP
See the category- fal-assetsrehan-remade/fal-assets5
- ai-system-prompt-leakagenoorqureshi/ai-system-prompt-leakage4
- ai-prompt-injectionnoorqureshi/ai-prompt-injection4
- testing-prompt-injection-in-rag-pipelinesmukul975/testing-prompt-injection-in-rag-pipelines4
- implementing-llm-guardrails-for-securitymukul975/implementing-llm-guardrails-for-security4
- defending-llms-with-guardrailsmukul975/defending-llms-with-guardrails4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login