# hunt-rce

hunt-rce — a skill for hunting remote code execution bugs: it points to likely RCE spots across web apps, CI/CD, containers and ML services, with ready grep signatures.

- skill · `type=skill` · Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 1298 repo stars
- Author: H-mmer
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/H-mmer/pentest-agents/tree/HEAD/providers/cursor/.cursor/skills/pentest-agents-hunt-rce/SKILL.md
- Updated: 2026-06-12
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/hunt-rce

## What it does

The skill draws on 1,218 public RCE reports from HackerOne, Project Zero, Intigriti and GitHub Security Advisories, with recent entries cross-checked against NVD. It walks through target classes: deserialization bugs in React Server Components, takeovers of CI/CD runners and GitOps controllers, container runtime escapes (runc, BuildKit, NVIDIA Container Toolkit), pickle-based deserialization in ML inference pipelines, and prompt injection into agentic LLM tools like PythonREPLTool. Each class comes with named CVEs, CVSS scores and disclosure sources.

A separate section lists grep signatures: `rg` patterns for spotting risky sinks such as `ObjectInputStream`/`readObject` in Java or `pickle.loads`/`yaml.load` in Python directly in a codebase. Treat it as a bounty-hunting checklist rather than a scanner — it's built for targets where user input can actually reach a shell, deserializer, template engine or git/curl/tar call.

The skill is written for bug bounty and penetration testing work within an authorized scope.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add H-mmer/pentest-agents --skill hunt-rce -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/pentest-agents-hunt-rce/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/pentest-agents-hunt-rce/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add H-mmer/pentest-agents --skill hunt-rce -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/pentest-agents-hunt-rce/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add H-mmer/pentest-agents --skill hunt-rce -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/pentest-agents-hunt-rce/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install H-mmer/pentest-agents providers/cursor/.cursor/skills/pentest-agents-hunt-rce
```

2. **Manually: put the files in place**
- File: `.github/skills/pentest-agents-hunt-rce/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add H-mmer/pentest-agents --skill hunt-rce -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/H-mmer/pentest-agents --path providers/cursor/.cursor/skills/pentest-agents-hunt-rce
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/pentest-agents-hunt-rce/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/H-mmer/pentest-agents/tree/HEAD/providers/cursor/.cursor/skills/pentest-agents-hunt-rce/SKILL.md

## When to use it
- spot an RCE path in a modern JS stack using React Server Components
- check a CI/CD runner or GitOps controller for a git-resolver takeover
- assess container escape risk through runc or BuildKit
- find unsafe pickle deserialization in an ML inference server
- catch prompt injection reaching agentic LLM tools like PythonREPLTool

## Example prompts
- Run hunt-rce against this Next.js app to check for an RCE path through React Server Components
- Use hunt-rce to scan this Java service for risky deserialization signatures
- Apply hunt-rce to the CI pipeline to check the GitOps resolvers for argument injection

## Similar
- [hunt-deserialization](https://affpapa.org/en/nevibecode/skills/hunt-deserialization.md) — skill · ★ 16193 repo stars
- [hunt-ssti](https://affpapa.org/en/nevibecode/skills/hunt-ssti.md) — skill · ★ 16193 repo stars
- [arbitrary-write-to-rce](https://affpapa.org/en/nevibecode/skills/arbitrary-write-to-rce.md) — skill · 3900 installs
- [deserialization-insecure](https://affpapa.org/en/nevibecode/skills/deserialization-insecure.md) — skill · 4000 installs
- [exploiting-insecure-deserialization](https://affpapa.org/en/nevibecode/skills/exploiting-insecure-deserialization.md) — skill · 256 installs
- [bounty-deep-hunt](https://affpapa.org/en/nevibecode/skills/bounty-deep-hunt.md) — skill · ★ 326 repo stars

From the same set: [h-mmer/pentest-agents](https://affpapa.org/en/nevibecode/by/h-mmer/pentest-agents.md) — 43 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
