Skip to main content
skill CX Codex

hunt-clickjacking — Claude Code skill for clickjacking checks

hunt-clickjacking is a Claude Code skill that checks whether a page can be framed and used to trigger a sensitive action. It investigates clickjacking in web applications.

MIT ★ 16,193 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsouls
Open on GitHub

What hunt-clickjacking does

This skill guides clickjacking checks for sign-in flows, transfers, account settings, and OAuth approvals. It starts by examining X-Frame-Options and CSP frame-ancestors, then calls for a real-browser test: the page must render in a frame, and a sensitive action must still work across sites.

Missing headers alone do not prove a vulnerability. Frame-blocking JavaScript can stop the attack, while SameSite=Lax or SameSite=Strict cookies may not accompany a cross-site framed request. Test with the victim authenticated and verify an action that changes state; a screenshot or recording is also part of the proof.

In Claude Code, add the repository as a marketplace and install the plugin, or use npx skills add. Without the browser proof, a missing header is only a lead to investigate, not a confirmed finding.

What it helps with

  • spot pages that lack framing protection
  • test whether a page renders in a real-browser iframe
  • verify that a framed click triggers a sensitive action
  • rule out cases blocked by SameSite cookies or framebusting

Example prompts for the agent

  • Check the transfer page for clickjacking and verify that the action works in a frame.
  • Review the OAuth approval page: inspect its headers, then test it in a browser.
  • Test whether an authenticated user’s password change can be triggered through clickjacking.

How to install hunt-clickjacking

1Plugin marketplace

/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsouls

This installs the whole claude-bughunter plugin with all its skills

2Skills CLI (Vercel)

npx skills add elementalsouls/Claude-BugHunter --skill hunt-clickjacking -a claude-code

3Manually: put the files in place

~/.claude/skills/hunt-clickjacking/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hunt-clickjacking/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hunt-clickjacking

How do I install hunt-clickjacking in Claude Code?

Add the marketplace with /plugin marketplace add elementalsouls/Claude-BugHunter, then install the plugin with /plugin install claude-bughunter@elementalsouls.

What does hunt-clickjacking do?

It guides checks for clickjacking by inspecting framing headers and testing in a real browser whether a sensitive action works inside a frame.

Why aren’t missing headers enough to confirm clickjacking?

JavaScript can prevent framing, and SameSite=Lax or SameSite=Strict cookies may not be sent with a cross-site framed request. The test must show that a sensitive action succeeds in the authenticated state.

Source text

SKILL.md · MIT
---
name: hunt-clickjacking
description: "Hunt Clickjacking — missing X-Frame-Options / CSP frame-ancestors lets an attacker embed the target page in an invisible iframe and trick victims into clicking buttons they cannot see (UI redressing). Targets: login flows, money transfers, account settings, OAuth confirmation pages. Confirm by fetching the page, then PROVE it frames in a real browser and a sensitive state-changing action survives the cross-site context (SameSite cookies / framebusting JS can defeat it) — header-absence alone is not a finding."
sources: hackerone_public, public_research
report_count: 6
---

## What is Clickjacking

Clickjacking (UI Redressing) lets an attacker load a target page inside a transparent iframe on a malicious site. The victim sees the attacker's decoy UI but clicks the hidden target UI beneath it. No JavaScript on the target is required.

**Highest-value targets:**
- Login / authentication pages — force login with attacker credentials
- Money transfer / checkout / "confirm payment" buttons
- Account settings (email change, password change, 2FA disable)
- OAuth / social-login "Authorize app" confirmation dialogs
- Admin actions (delete, promote user, change role)

## Protection Headers

Two mechanisms prevent framing:

```
X-Frame-Options: DENY              # strongest — blocks all framing
X-Frame-Options: SAMEORIGIN        # allows same-origin frames only
Content-Security-Policy: frame-ancestors 'none'     # CSP equivalent of DENY
Content-Security-Policy: frame-ancestors 'self'     # CSP equivalent of SAMEORIGIN
```

If NEITHER is present, the page is frameable from any origin.

## How to Test

Header-absence is the **trigger for investigation, not the finding**. Two steps:

**Step 1 — Header check (screening).** Fetch the target page and inspect the response headers:

```
curl -sI https://target.example/account/transfer | grep -iE 'x-frame-options|content-security-policy'
```
If BOTH `X-Frame-Options` and CSP `frame-ancestors` are absent, the page is a *candidate*. If either is present and restrictive (`DENY`/`SAMEORIGIN`/`frame-ancestors 'none'|'self'`), stop — it's protected.

**Step 2 — Prove it actually frames and clicks (required for a real finding).** Build a minimal PoC and load it in a real browser:

```html
<!doctype html>
<h1>Win a prize — click below</h1>
<iframe src="https://target.example/account/transfer"
        style="opacity:0.1;position:absolute;top:0;left:0;width:1000px;height:800px"></iframe>
```
Confirm ALL of the following, or it is not exploitable:
- The page **actually renders inside the iframe** (no framebusting JS that blanks/redirects it — e.g. `if(top!==self)` breakout, or a `Sec-Fetch-Dest`/JS frame check).
- The **sensitive action still works while framed** — critically, the action must succeed *cross-site*. If it relies on a session cookie set `SameSite=Lax` or `SameSite=Strict` (the modern default), the cookie is **not** sent on the cross-site framed request, and the clickjack fails. Verify the victim's authenticated state carries into the frame.
- The target is a **state-changing action** (transfer, settings/email/password change, 2FA disable, OAuth authorize, admin action), not a read-only page.

**Strategy:** target the most sensitive action pages first — severity scales directly with what the victim is tricked into doing.

## False Positives

- Public, read-only pages (home/marketing) lacking frame protection are low/informational — no sensitive action to redress.
- APIs and non-HTML endpoints (JSON, images) are not clickjacking targets.
- **Header-absence alone is NOT a finding.** SameSite cookies, framebusting JS, or the lack of any sensitive framed action can each fully defeat it — which is why Step 2 is mandatory.

## Proof Requirements

A valid clickjacking report shows: (1) the target page rendered inside an attacker-controlled iframe in a real browser, (2) a sensitive state-changing action reachable by a framed click while the victim is authenticated (cookies survive the cross-site context), and (3) a screenshot/recording of the overlay. Reporting missing headers with no working frame PoC is a documentation-quality issue, not a vulnerability.

© Sachin Sharma · MIT · elementalsouls/Claude-BugHunter

Similar skills

All skills for Security →

From the same set92

The whole set →
triage triage evaluates security findings through a 7-question gate before you write a bug report. It helps bug bounty hunters discard invalid submissions immediately. CX Codex +1 ★ 16,193repo stars report Builds a submission-ready bug bounty report. Generates CVSS 3.1 score, proof of concept, impact statement, and fix in HackerOne, Bugcrowd, Intigriti, or Immunefi format. CX Codex +1 ★ 16,193repo stars validate validate — a validation command that culls weak findings before report writing. Runs a 7-Question Gate and 4-gate checklist to prevent submissions that damage your validity ratio. CX Codex +1 ★ 16,193repo stars autopilot autopilot is a Claude Code command for autonomous vulnerability hunting. It checks scope, ranks targets, validates findings, and drafts reports. CX Codex +1 ★ 16,193repo stars hunt hunt dispatches vulnerability assessments across Red Team and WAPT workflows with scope boundaries. CX Codex +1 ★ 16,193repo stars token-scan token-scan — a Claude slash command that hunts rug-pull vectors in token and meme coin contracts on Solidity and Solana. Useful before you buy an unknown token or ship your own. CX Codex +1 ★ 16,193repo stars chain Takes a confirmed bug A and finds B and C to combine into a higher-severity chain. For bug hunters stuck with Low or conditionally valid findings. CX Codex +1 ★ 16,193repo stars hunt-nosqli hunt-nosqli helps detect NoSQL injection flaws in MongoDB, CouchDB, and Redis. It assists developers and testers during API security reviews and auth auditing. CX Codex +1 ★ 16,193repo stars

Project sponsors

Companies that keep this analytics open