Skip to content
Skillpedia
Misc42k · #4737

competition-ssrf-metadata-pivot

Helps your agent trace SSRF vulnerabilities and metadata access. It allows understanding how a server can be tricked into accessing internal resources or sensitive credentials.

What it does

This tool helps understand how a 'Server-Side Request Forgery' (SSRF) attack can be used to access sensitive information or credentials within a network. It traces the path a malicious request might take.

When to use it

  • ✓When you suspect a request sent to a server was used to access other internal systems.
  • ✓When investigating how credentials or sensitive information might have been stolen through a server.
  • ✓To understand attack paths that exploit a server's ability to make requests to other locations.

Example of what to ask your AI

“How can I trace a request that might have accessed internal server information?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/zhaoxuya520/reverse-skill/blob/main/CTF-Sandbox-Orchestrator/competition-ssrf-metadata-pivot/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/zhaoxuya520/reverse-skill/blob/main/CTF-Sandbox-Orchestrator/competition-ssrf-metadata-pivot/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool analyzes the original request, identifies where it was sent within the network, and checks if it managed to access sensitive data points or credentials. It maps this entire path to show how access was possible.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add zhaoxuya520/reverse-skill --skill competition-ssrf-metadata-pivot

Or download just the file:

curl -L https://raw.githubusercontent.com/zhaoxuya520/reverse-skill/main/CTF-Sandbox-Orchestrator/competition-ssrf-metadata-pivot/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Competition SSRF Metadata Pivot

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive path runs through server-side request capability, internal service reachability, or metadata-derived credentials.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Separate the SSRF source, forwarding layer, reachable target, and accepted downstream credential edge.
  2. Record request method, URL construction, header behavior, redirects, DNS or host overrides, and response shaping before mutation.
  3. Map internal host, metadata endpoint, token extraction, and accepting service as one chain.
  4. Distinguish read-only reachability from credential-bearing access.
  5. Reproduce the smallest SSRF-to-accepted-access path.

Workflow

1. Map SSRF Reachability

  • Record source primitive: URL parameter, webhook, image fetcher, importer, proxy endpoint, or backend callback.
  • Note normalization steps: scheme filtering, host allowlists, redirects, DNS resolution, path rewrite, and header injection.
  • Keep target host, protocol, and response behavior tied to the exact SSRF source.

2. Trace Metadata And Credential Pivot

  • Show whether metadata endpoints, internal control APIs, or workload identity services are reachable.
  • Record token fields, role scope, service account, expiration, and where the token is accepted.
  • Distinguish credential extraction success from accepted privilege at a downstream service.

3. Reduce To Decisive SSRF Chain

  • Compress to: SSRF source -> internal or metadata target -> credential or sensitive response -> accepted replay or API access.
  • State whether the decisive edge is parser bypass, allowlist bypass, redirect abuse, header confusion, or metadata trust.
  • If the task becomes mostly cloud identity policy analysis, hand off to the tighter cloud metadata skill.

Read This Reference

  • Load references/ssrf-metadata-pivot.md for SSRF checklists, metadata pivots, and evidence packaging.

What To Preserve

  • SSRF source point, URL construction rules, reachable hosts, and response deltas
  • Extracted token or credential fields, scope, and accepting service
  • One minimal SSRF-to-accepted-access replay path
FAQ

What is SSRF?

SSRF is a type of attack where an attacker tricks a web server into making requests to other services or systems, often within the server's private network, which would normally be inaccessible.

What are 'metadata endpoints'?

These are special addresses that servers (especially in clouds like AWS, GCP, Azure) use to provide information about themselves and the environment they are running in, including access credentials.

What does 'credential pivoting' mean?

It's the act of using credentials obtained from a compromised system to access other systems or services, as if 'pivoting' or moving from one point to another.

Details

Original description by the author

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSRF reachability, internal route probing, metadata-service access, credential pivoting, and token-to-accepted-privilege chains. Use when the user asks to trace SSRF sources, internal hosts, metadata endpoints, link-local tokens, service-account credentials, or explain how a server-side fetch edge turns into accepted

repo: zhaoxuya520/reverse-skill

Popularity

GitHub stars
42k
Ranking position
#4737
License
MIT
Updated
9/22/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills