What Is Vibe Coding?
Vibe coding is building software by describing what you want to an AI coding tool and accepting the code it writes, without reading or fully understanding it. The term was coined by Andrej Karpathy in February 2025, and it now raises real security questions as vibe-coded apps reach production.
Also known as:
Where the Term Comes From
In a post on X on February 3, 2025, Andrej Karpathy described a new kind of coding where he talks to an AI editor, always accepts its changes, no longer reads the diffs and pastes error messages back until things work. He framed it as fine for throwaway weekend projects. The name stuck, and it is now used for any workflow where AI writes most of the code and humans mainly judge whether the result appears to work.
Why Vibe Coding Is a Security Risk
The defining feature of vibe coding, not reading the code, removes the step where a developer would notice a security flaw. Code that runs and looks right can still be unsafe.
- Missing authorization. Endpoints that work in a demo but let any user read or change another user's data.
- Injection flaws. User input passed into queries, commands or templates without validation.
- Hardcoded secrets. API keys and credentials pasted into code or config to make something work.
- Risky dependencies. Packages added without review, including outdated or nonexistent ones a model suggested.
- Insecure defaults. Debug modes, open CORS policies and permissive cloud settings left on.
Vibe Coding vs AI-Assisted Development
Using AI to write code is not the problem. Professional teams that use AI coding assistants still review diffs, run tests and keep code review and security checks in the pipeline. Vibe coding is the version where those checks are skipped, which is why secure-by-design guidance from CISA and frameworks such as NIST's Secure Software Development Framework still apply to AI-written code.
How to Make Vibe-Coded Software Safer
- Scan every change. Run static analysis, dependency checks and secrets detection on each pull request.
- Review what ships. Have a person approve anything that reaches production, especially auth and data access.
- Test behavior, not appearance. Check that users cannot reach each other's data, not only that the page loads.
How Nullify Helps
Nullify scans every default-branch commit and pull request with AI-native static analysis across 20 languages, including business-logic and authorization flaws, finds exposed secrets and verifies which keys are still active. Fixes arrive as validated pull requests, and developers approve every merge. See how Nullify secures AI-written code.
Key Takeaways
- Vibe coding means accepting AI-written code without reading or fully understanding it.
- Andrej Karpathy coined the term in February 2025.
- Skipping review lets authorization flaws, injection, secrets and risky dependencies through.
- Scan every change and keep human review on what ships.
Read More About Vibe Coding
Code Security
See Nullify in Action
Nullify reviews every AI-written pull request for the flaws a quick demo will not show.