# bluehammer-vulnerability-poc

A skill that walks the agent through the BlueHammer repo: building the C exploit, running it, and reading the vulnerability code. For isolated labs only.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 570 installs · ★ 88
- Author: reason-machines
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/reason-machines/trending-skills/tree/HEAD/skills/bluehammer-vulnerability-poc/SKILL.md
- Updated: 2026-10-09
- HTML: https://affpapa.org/en/nevibecode/skills/bluehammer-vulnerability-poc

## What it does

BlueHammer is a C proof-of-concept that demonstrates one specific vulnerability. The repo is a research artifact: it documents the bug, ships the exploit, and carries a PGP signature so you can check authenticity. The skill hands the agent that context instead of leaving it to guess how the code builds and runs.

Inside are working command patterns. Clone with `git clone`, verify the signed README against the author's key, build a single file with `gcc` and flags like `-fno-stack-protector` and `-no-pie`, then run the binary with a target argument. A separate section covers the usual mistakes in PoCs of this kind: off-by-one writes, a missing null terminator, a wrong size in `malloc`, a shifted offset in the payload. Debugging gets its own pass with `gdb`, `strace` and `checksec`, plus a Python harness that brute-forces the crash offset.

The author flags known bugs in the PoC, so it may not work as-is. That is the reason to read the source closely rather than expect a clean run. Keep it inside an authorized isolated environment — the code is a demonstration, meant for defense and study.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install reason-machines/trending-skills bluehammer-vulnerability-poc
```

2. **Manually: put the files in place**
- File: `.github/skills/bluehammer-vulnerability-poc/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/reason-machines/trending-skills --path skills/bluehammer-vulnerability-poc
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/bluehammer-vulnerability-poc/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a opencode
```

### 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/reason-machines/trending-skills/tree/HEAD/skills/bluehammer-vulnerability-poc/SKILL.md

## When to use it
- build a single-file C exploit with no documented build system
- verify the PGP signature on the README before running anything
- find the offset that overwrites the return address
- audit PoC source for size and bounds mistakes
- debug a crashing binary under gdb and strace

## Example prompts
- use bluehammer, help me build the PoC from source
- read the bluehammer vulnerability code and find the buffer size bug
- set up bluehammer in an isolated lab and run it with a target argument

## Similar
- [vulnerability-writeup](https://affpapa.org/en/nevibecode/skills/vulnerability-writeup.md) — skill · 25 installs
- [jndi-injection](https://affpapa.org/en/nevibecode/skills/jndi-injection.md) — skill · 3600 installs
- [format-string-exploitation](https://affpapa.org/en/nevibecode/skills/format-string-exploitation.md) — skill · 3600 installs
- [vulnerability-scanning](https://affpapa.org/en/nevibecode/skills/vulnerability-scanning.md) — skill · 611 installs
- [ghost-validate](https://affpapa.org/en/nevibecode/skills/ghost-validate.md) — skill · 3800 installs
- [penetration-test](https://affpapa.org/en/nevibecode/commands/penetration-test.md) — command · 434 installs

From the same set: [reason-machines/trending-skills](https://affpapa.org/en/nevibecode/by/reason-machines/trending-skills.md) — 42 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