hunt-rce

Identify remote code execution vectors across web and infrastructure endpoints.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jellaharshith/SWIFT --skill hunt-rce-jellaharshith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-rce
Source: https://github.com/jellaharshith/SWIFT/tree/main/swift/skills/cbh/skills/hunt-rce
Command: npx skills add https://github.com/jellaharshith/SWIFT --skill hunt-rce-jellaharshith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hunt-rce helps you identify, triage, and validate remote code execution opportunities across common web and infrastructure attack surfaces, reducing guesswork by requiring concrete impact evidence before reporting.

Core Features & Use Cases

  • Attack surface targeting for high-impact RCE classes: Focuses on management consoles, admin/config UIs, execution endpoints, and parsing-heavy surfaces such as YAML/XML, templates, and path-based dispatchers.
  • Evidence-driven validation workflow: Uses a clear validation gate to confirm attacker capability (command execution, file read, or out-of-band callbacks), articulate victim loss, and ensure fast reproducibility from scratch.
  • Triage-oriented hunting guidance and escalation logic: Provides signals, payload patterns, bypass ideas, and a discipline for escalating findings when the same primitive yields higher impact on a CGI-enabled or execution-capable surface.

Use it when you are conducting a bug bounty or red-team engagement and want a repeatable method to move from reconnaissance signals to confirmed RCE with minimal ambiguity.

Quick Start

Use the hunt-rce skill to locate RCE-by-construction surfaces on the target, then confirm exploitability with an output or out-of-band callback before writing the report.

Frequently Asked Questions about hunt-rce

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

FAQPage Schema
How do I validate remote code execution vulnerabilities with out-of-band confirmation?

Remote code execution validation requires proving attacker capability through command execution, file read, or out-of-band callbacks, articulating victim impact, and ensuring reproducibility within ten minutes from scratch.

What surfaces are most likely to yield RCE during a bug bounty hunt?

Template injection, unsafe YAML or XML parsing, traversal-to-execution chains, and dependency confusion across management consoles, admin UIs, and execution endpoints are the primary RCE-by-construction surfaces to target.

How do I triage and escalate an RCE primitive found on a web endpoint?

Triage RCE primitives by mapping execution contexts and selecting likely payloads, then escalate findings when the same primitive yields higher impact on CGI-enabled or execution-capable surfaces.

Can I use this approach for both web and infrastructure targets during red-team engagements?

Yes, this method applies to both web and infrastructure scenarios, targeting execution-adjacent surfaces like config UIs and parsing-heavy endpoints to map execution contexts and confirm exploitability.

Does template injection always lead to remote code execution?

Template injection is an execution-adjacent surface that can lead to RCE, but it requires validation through concrete output or out-of-band callbacks to confirm actual code execution before reporting.

Why do I need to prove attacker capability before reporting an RCE finding?

Proving attacker capability reduces guesswork by demanding concrete impact evidence—command execution, file read, or out-of-band callbacks—ensuring deterministic triage and minimal ambiguity in bug bounty reports.