Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
claude-project-scanner — Read-only safety scanner for Claude Code projects. Catches CVE-2025-59536, statusLine injection, prompt injection, and more. | Kitploit
Tools/GitHubGitHub/razi-interactive/claude-project-scanner
Static AnalysisVulnerability ScannersCode AnalysisSupply Chain SecurityMisconfigurationLearning & EducationAI Security
GitHubrazi-interactive/claude-project-scanner

claude-project-scanner

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Read-only safety scanner for Claude Code projects. Catches CVE-2025-59536, statusLine injection, prompt injection, and more.

View Repository
3 months agoNot yet reviewed

Claude Project Scanner

Read-only Claude Code skill that scans third-party projects for known security risks before you open them.

Catches the attack patterns documented in:

  • CVE-2025-59536 (Claude Code Lifecycle Hooks injection)
  • CVE-2025-61260 (OpenAI Codex CODEX_HOME injection)
  • CVE-2025-54136 (Cursor plugin validation bypass)

Plus statusLine.command execution, additionalDirectories escape, prompt injection in agents/skills/commands/output-styles, suspicious MCP servers, and hidden base64-shaped payloads.


⚠️ Read this first

1. Hygiene check, not a complete security tool. This is one defensive layer. It does not replace manual review of files it flags.

2. Based on attack patterns known as of April 2026. New attack vectors will require updates. If you find a pattern this scan misses, please open an issue.

3. No warranty (MIT License). Use at your own risk. The author accepts no liability for damages arising from use of this tool.


What it checks

SurfaceWhat's flagged
.claude/settings.json, settings.local.jsonhooks, statusLine.command, additionalDirectories, broad permissions like Bash(*)
.mcp.jsonMCP servers pointing at /tmp/, ~/Downloads/, http://, suspicious payload URLs
CLAUDE.md, AGENTS.mdPrompt injection patterns ("ignore previous instructions", "you are now", HTML-comment hidden instructions)
.claude/agents/*.md, skills/*.md, commands/*.md, output-styles/*.mdSame prompt injection patterns
.claude-plugin/plugin.jsonPlugin manifests declaring hooks
.env, .env.localCODEX_HOME= pointing inside the project, exposed secrets
.cursor/, .codex/Marker directories from other AI tools (worth a manual look)
Any of the aboveLong alphanumeric runs (80+ chars) hinting at base64-encoded payloads

What it does NOT check

  • Encoded payloads (it flags long alphanumeric runs but does not decode them)
  • package.json preinstall, pyproject.toml scripts (out of scope - relevant only when you run npm install / pip install)
  • Polyglot files
  • Attack vectors not yet published as of April 2026
  • Your global ~/.claude/settings.json (the scanner targets project directories, not the machine)

Installation

Two files. No dependencies.

1. Save the skill globally:

root@kitploit:~
mkdir -p ~/.claude/skills
cp scan-project-skill.md ~/.claude/skills/

2. Save the slash command globally:

root@kitploit:~
mkdir -p ~/.claude/commands
cp scan-project.md ~/.claude/commands/

3. Open a new Claude Code session (so the new skill loads).

That's it.


Usage

root@kitploit:~
/scan-project /absolute/path/to/some-cloned-repo

Or with a ~ path:

root@kitploit:~
/scan-project ~/Downloads/some-skill-folder

You'll get a Hebrew report with one of four verdicts:

  • 🔴 RED - do not open. Findings match known attack patterns.
  • 🟠 ORANGE - review the flagged files manually before opening.
  • 🟡 YELLOW - notable but probably fine.
  • 🟢 GREEN - no findings. Still no substitute for manual review.

The report always includes a "limitations" section so you know what the scan can and cannot catch.


Self-test

Two example fixtures are included so you can see the scanner work:

root@kitploit:~
/scan-project ./example-fixtures/clean-example

Expected: 🟢 GREEN

root@kitploit:~
/scan-project ./example-fixtures/red-example

Expected: 🔴 RED with multiple findings


Why I built this

I'm Razi Dolev. I build AI agent systems for businesses (in Israel and beyond), run Google Ads campaigns, and consult on digital marketing. I also write in Hebrew about AI for businesses on my blog.

After Check Point published the April 2026 research on AI coding tool vulnerabilities, I needed a quick way to scan repos before opening them. This is the tool I built for myself, sharing publicly because the threat affects everyone using these tools.

The scan logic is in plain markdown - read it before you install. That's the point.


Get in touch

If you want help building AI agent systems for your business (marketing automation, content workflows, lead generation), running Google Ads campaigns, or digital marketing consulting, get in touch via razi.co.il.

For Hebrew insights on AI for businesses, subscribe to the newsletter.


License

MIT. See LICENSE.

Source research

Vanunu, Oded. "AI Agent Configuration Files as Attack Vectors." Check Point Research, April 2026.

Download Tool