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 installazioni+3 in 7 giorni39 Stellesincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/vibe-audit-techniqueScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto6efdc88e…036744fa
6efdc88ec95e…b488036744fa10 file · 11.7 KBScansioneAlto3 segnalazioni
- injection.ignore_instructionsreferences/ai-integration.md:31
- Nessuna licenza trovata
- Link a domini esterni
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-techniques/vibe-audit-technique@21cd568
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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).
File di questa versione
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
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- AltaPrompt injection · injection.ignore_instructionsreferences/ai-integration.md:31
- MediaLicenza · Nessuna licenza trovata
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 6efdc88e | Firmata | – |
Altro da AeonDave
Tutto da questo editoreAltro in IA, agenti e MCP
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login