<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🤖 Tool: MEDUSA — AI-first Security Scanner]]></title><description><![CDATA[<p>----------------</p><p><img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f916.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--robot_face" style="height:23px;width:auto;vertical-align:middle" title="🤖" alt="🤖" /> Tool: MEDUSA — AI-first Security Scanner</p><p>Overview</p><p>MEDUSA is presented as an AI-first security scanner with more than 9,600 detection patterns focused on AI/ML applications, LLM agents, RAG pipelines, MCP servers and traditional codebases. The release v2026.5.0 emphasizes AI supply-chain coverage with a new Git scanning capability and repo poisoning detection.</p><p>Key technical facts<br />• Detection surface: 9,600+ AI security patterns targeting agent frameworks, MCP protocols, RAG components and editor/IDE config files.  <br />• CVE coverage: Product claims detection of 133 CVEs, with named detections including Log4Shell, Spring4Shell, XZ Utils backdoor, LangChain RCE, MCP remote code execution and React2Shell.  <br />• New rules: v2026.5.0 adds 45 attack rules for repo poisoning and 11 rules for MCP advanced attacks (schema poisoning, sampling injection, cross-server manipulation, Flowise RCE).  <br />• Repo poisoning specifics: Detection across 28+ AI editor and IDE file types (examples enumerated include Cursor, Cline, Copilot, Claude Code, Gemini CLI, Kiro, Codex CLI, Windsurf, Amazon Q, Roo Code).  <br />• Performance &amp; outputs: Parallel processing for multi-core scanning, smart caching to skip unchanged files, and multiple export formats (JSON, HTML, Markdown, SARIF).</p><p>Technical implications (reporting the release)</p><p>The release documents a focused effort on AI supply-chain tactics: repo poisoning heuristics, editor-config weaponization, and MCP-targeted attack rules. The product adds path-relative FP filtering to reduce false positives when repo names previously matched heuristics. The Git scanning feature is described as a single-step repo analysis for supply-chain indicators.</p><p>Constraints and scope</p><p>The documentation frames MEDUSA as cross-platform (Windows/macOS/Linux) with IDE integrations and optional linter enhancements. The release notes list capabilities and detection counts; they do not provide operational deployment commands or step‑by‑step setup details.</p><p><img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f539.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--small_blue_diamond" style="height:23px;width:auto;vertical-align:middle" title="🔹" alt="🔹" /> medusa <a href="https://infosec.exchange/tags/ai_security" rel="tag">#<span>ai_security</span></a> <a href="https://infosec.exchange/tags/repo_poisoning" rel="tag">#<span>repo_poisoning</span></a> <a href="https://infosec.exchange/tags/log4shell" rel="tag">#<span>log4shell</span></a> <a href="https://infosec.exchange/tags/langchain" rel="tag">#<span>langchain</span></a></p><p><img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f517.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--link" style="height:23px;width:auto;vertical-align:middle" title="🔗" alt="🔗" /> Source: <a href="https://github.com/Pantheon-Security/medusa" rel="nofollow noopener"><span>https://</span><span>github.com/Pantheon-Security/m</span><span>edusa</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/ade763a5-e460-4195-b93a-11997e36b569/tool-medusa-ai-first-security-scanner</link><generator>RSS for Node</generator><lastBuildDate>Mon, 06 Apr 2026 07:57:30 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/ade763a5-e460-4195-b93a-11997e36b569.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 31 Mar 2026 13:24:23 GMT</pubDate><ttl>60</ttl></channel></rss>