injection-hunter

Trace user-controlled input from sources to dangerous sinks to detect injection vulnerabilities.

1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/MAF2414/kyco --skill injection-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: injection-hunter
Source: https://github.com/MAF2414/kyco/tree/main/.claude/skills/injection-hunter
Command: npx skills add https://github.com/MAF2414/kyco --skill injection-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Injection vulnerabilities arise when untrusted user input flows into sensitive operations, enabling attackers to manipulate behavior or exfiltrate data. This Skill helps identify and trace tainted data from sources to dangerous sinks across the codebase, covering SQL injection, OS command injection, XSS, SSTI, path traversal, LDAP and XML injections.

Core Features & Use Cases

  • Taint-tracking across input sources to dangerous sinks (SQL, command, XSS, SSTI, path traversal, LDAP/XML)
  • Identify common insecure patterns and provide remediation guidance
  • Generate structured findings suitable for remediation planning and compliance

Quick Start

Analyze a codebase to locate and report injection flaws from user input to dangerous sinks.

Frequently Asked Questions about injection-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace user-controlled input to find injection vulnerabilities in my codebase?

Taint tracking traces user-controlled input from sources to dangerous sinks to uncover injection vulnerabilities. This process enforces data flow analysis across web applications, APIs, and services to identify where untrusted inputs interact with databases, shells, or templates.

What types of injection flaws can taint analysis detect in web applications?

Taint analysis detects SQL injection, OS command injection, XSS, SSTI, path traversal, LDAP, and XML injections. It asserts common insecure patterns by tracing how untrusted user input flows into sensitive operations across multiple application layers.

Does this injection analysis work for APIs and services or just web applications?

Injection analysis applies to web applications, APIs, and services where inputs flow through multiple layers. It traces tainted data regardless of the entry point, covering interactions with databases, shells, and templates across diverse service architectures.

How do I get structured findings for remediation after identifying injection vulnerabilities?

Injection vulnerability analysis generates structured findings suitable for remediation planning and compliance. It identifies insecure patterns from user input sources to dangerous sinks and outputs actionable data to guide code fixes.

What is the best way to detect SSTI and path traversal flaws in user input?

Taint analysis is the best way to detect SSTI and path traversal flaws by tracing untrusted user input from sources to template engines or file system sinks. It identifies common insecure patterns and provides remediation guidance.