MCP Tool Poisoning: How AI Coding Assistants Get Hijacked Through the Tools You Install
We tested 6 MCP attack scenarios against AI coding assistants. All 6 were fully exploitable. Here's what we found and how to protect yourself.
Read postPractical security advice for modern development teams. No jargon, no fluff, just actionable guidance.
We tested 6 MCP attack scenarios against AI coding assistants. All 6 were fully exploitable. Here's what we found and how to protect yourself.
Read postAutomated scanners find known vulnerabilities fast. But they miss business logic flaws, context-dependent issues, and the AI-specific security gaps that matter most in vibe-coded apps.
Read postYour AI coding assistant was trained 6 months ago. New CVEs come out every day. That gap is where attackers live.
Read postWe tested 3 AI assistants on security headers. All 3 gave us instructions. All 3 were wrong in different ways.
Read postYou used Cursor, Claude Code, or Bolt to build your app. It works. You shipped fast. But AI coding tools optimize for functionality, not security.
Read postRun this in your terminal and find out if your Content-Security-Policy is actually protecting you.
Read postClickjacking is one of the oldest tricks in the book. And it still works on thousands of websites.
Read postActionable security insights for vibe coders, delivered every Thursday. No spam, unsubscribe anytime.
By subscribing, you agree to receive marketing emails from VibeSec Advisory. You can unsubscribe at any time. Privacy Policy
Get a comprehensive security assessment with actionable fix prompts.
Scan Your App FreeWe use Cloudflare Analytics, which is cookieless and does not track individual users. No cookies are set for analytics purposes. Privacy Policy