hunt-ssrf

Detects and confirms SSRF vulnerabilities using OOB callbacks, cloud metadata payloads, and bypass variants.

2|1|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/lycheer1126/xs-bigdan --skill hunt-ssrf-lycheer1126
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-ssrf
Source: https://github.com/lycheer1126/xs-bigdan/tree/main/knowledge/skills/hunt_ssrf
Command: npx skills add https://github.com/lycheer1126/xs-bigdan --skill hunt-ssrf-lycheer1126

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? SSRF is a low-cost, high-impact vulnerability class, but blind SSRF is frequently misreported because error messages and status-code differences look like confirmation when they are not. This Skill provides a disciplined hunting methodology that separates real server-side fetches from false positives and escalates confirmed bugs toward cloud credential impact. ## Core Features & Use Cases - Signal-based detection: Identifies SSRF-prone parameters (url, callback, webhook_url, avatar_url) and functional patterns like link previews, PDF rendering, and low-code API debuggers. - OOB confirmation gate: Enforces dnslog/interactsh callback verification with per-sink subdomains, plus official SRC intranet targets (JD, Baidu, Tencent, ByteDance, Meituan) as authoritative proof. - Cloud metadata exploitation: Provides payload tables for AWS, Azure, GCP, Alibaba Cloud, and Tencent Cloud IMDS endpoints, including IMDSv2 token handling and CAM credential paths. - Bypass variants: Covers decimal/hex/octal IP encodings, IPv6 mapping, DNS rebinding, 302 redirect chains, and short-link bypasses for blacklist-filtered targets. - Use Case: During authorized SRC testing, you find an avatar upload feature accepting a URL. You plant a tagged dnslog callback, confirm the server-side fetch, then retrieve Tencent Cloud CAM temporary credentials via the metadata endpoint and stop to report at credential tier. ## Quick Start Use the hunt-ssrf skill to test this target's URL-fetching parameters for SSRF, confirm any hits with OOB callbacks, and check cloud metadata endpoints for credential exposure.

Frequently Asked Questions about hunt-ssrf

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

FAQPage Schema
How do I confirm a blind SSRF vulnerability?

Blind SSRF confirmation requires an out-of-band callback from dnslog.cn, ceye.io, or interactsh with a unique per-sink subdomain. Error messages echoing your URL, status code differences, or response delays do not count as confirmation. Zero callback means withdraw the finding.

What parameters and features indicate SSRF risk?

Test parameters named url, uri, callback, webhook_url, avatar_url, redirect, and fetch. Functional signals are more reliable: link previews, image upload/watermarking, PDF or screenshot generation, webhook registration, and low-code platform API debuggers all trigger server-side fetches.

How do I bypass SSRF blacklists blocking 169.254.169.254?

Try decimal (2852039166), hexadecimal (0xA9FEA9FE), or octal IP encodings, IPv6-mapped forms like [::ffff:a9fe:a9fe], DNS wildcard domains such as nip.io, 302 redirect chains from a controlled server, or DNS rebinding with TTL=0 domains.

Which cloud metadata endpoints should I test after confirming SSRF?

Test AWS at 169.254.169.254/latest/meta-data/, Azure with the Metadata:true header, GCP with Metadata-Flavor:Google, Alibaba Cloud at 100.100.100.200, and Tencent Cloud at metadata.tencentyun.com. Stop and report immediately upon obtaining temporary credentials.

Why does my SSRF finding get rejected as a false positive?

Rejections usually come from treating error-message URL echoes or timing differences as proof of a server-side fetch. Only an OOB callback showing the target server's source IP, or readable metadata content, qualifies as confirmed evidence.

Can I use gopher or file protocol SSRF payloads in bug bounty testing?

Protocol confusion payloads like gopher-to-Redis or file:// reads are restricted to explicitly authorized penetration tests or lab environments. Standard SRC programs prohibit them; stick to HTTP-based proof of reachability and stop at credential-level evidence.