Use when detect and exploit blind Server-Side Request Forgery vulnerabilities
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill performing-blind-ssrf-exploitation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Performing Blind Ssrf Exploitation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-performing-blind-ssrf-exploitation)More formats (shields.io, HTML) on the badges page.
---
name: performing-blind-ssrf-exploitation
description: Use when detect and exploit blind Server-Side Request Forgery vulnerabilities
using out-of-band techniques, DNS interactions, and timing analysis to access internal
services and cloud metadata endpoints. Use when detecting and exploit blind server-side
request forgery vulnerabilities using out-of-band.
domain: cybersecurity
tags:
- blind-ssrf
- ssrf
- out-of-band
- burp-collaborator
- cloud-metadata
- internal-network
- oob-detection
subdomain: web-application-security
version: '1.0'
author: oyi77
license: Apache-2.0
nist_csf:
- PR.PS-01
- ID.RA-01
- PR.DS-10
- DE.CM-01
category: cybersecurity
---
# Performing Blind Ssrf Exploitation
## Overview
Cybersecurity skill for performing blind ssrf exploitation. Follows industry best practices and security standards.
## When to Use
**Trigger phrases:**
- "performing blind ssrf exploitation"
- "Detect and exploit blind Server-Side Request Forgery vulnerabilities using out-o"
- When testing URL/webhook input parameters where server-side responses are not reflected
- During assessment of applications that fetch external resources (avatars, previews, imports)
- When testing PDF generators, image processors, or document converters for SSRF
- During cloud security assessments to detect metadata endpoint access
- When evaluating webhook functionality and URL validation implementations
## When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
## Prerequisites
- Burp Suite Professional with Burp Collaborator for OOB detection
- interact.sh or webhook.site for external callback monitoring
- Understanding of SSRF attack vectors and internal network enumeration
- Knowledge of cloud metadata endpoints (AWS, GCP, Azure)
- VPS or controlled server for advanced exploitation callback handling
- Python with requests library for automation scripts
## Workflow
```python
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```
1. **Plan Operations** — Define objectives, scope, and success criteria for blind ssrf exploitation operations.
2. **Prepare Environment** — Set up tools, access, and data sources required for blind ssrf exploitation.
3. **Execute Core Workflow** — Perform the blind ssrf exploitation operations following established procedures.
4. **Validate Results** — Verify that results meet quality standards and objectives.
5. **Report Findings** — Document results, observations, and recommendations.
6. **Follow Up** — Track remediation actions and verify fixes where applicable.
## Tools
- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing
## Process
1. **Reconnaissance** — Gather target information, identify attack surface, enumerate services
1. **Analysis/Exploitation** — Execute the technique, analyze results, document findings
1. **Reporting** — Document IOCs, write findings, provide remediation recommendations
## Verification
- [ ] All blind ssrf exploitation procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!