security-arsenal

Provides payloads, bypass tables, and wordlists for web vulnerability testing in authorized bug bounty engagements.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill security-arsenal-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-arsenal
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/security-arsenal
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill security-arsenal-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers waste time recalling or reconstructing correct payload syntax for each vulnerability class, and risk submitting findings that bug bounty programs always reject, hurting their validity ratio. ## Core Features & Use Cases - Payload Library by Vulnerability Class: Ready-to-use payloads for XSS, SSRF, SQLi, XXE, NoSQLi, command injection, SSTI, IDOR, path traversal, HTTP smuggling, WebSocket attacks, MFA bypass, and SAML attacks, each with detection, exploitation, and WAF-bypass variants. - Submission Decision Tables: An always-rejected list (e.g., missing security headers, self-XSS, clickjacking without PoC) and a conditionally-valid table showing which chains turn weak findings into reportable ones. - Recon Integration: gf pattern names, wordlist references, and built-in paths for fuzzing map recon output directly to the right payload section. - Use Case: During an authorized engagement, you find a URL parameter classified by gf ssrf; open the SSRF section to get cloud metadata endpoints, IP bypass encodings, and redirect-chain techniques, then confirm with an OOB callback before reporting. ## Quick Start Ask the assistant to load the security-arsenal skill and give you SSRF payloads and bypass techniques for testing a URL-fetching parameter on an authorized target.

Frequently Asked Questions about security-arsenal

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

FAQPage Schema
How do I test for SSRF vulnerabilities in a web application?

Start with cloud metadata endpoints like http://169.254.169.254/latest/meta-data/ for AWS, then try IP bypass encodings such as decimal (2130706433), octal, hex, or IPv6 loopback forms. Confirm blind SSRF with an out-of-band callback via Burp Collaborator or interactsh before reporting.

What payloads detect SQL injection across different databases?

Use time-based payloads specific to each engine: SLEEP(5) for MySQL, pg_sleep(5) for PostgreSQL, WAITFOR DELAY for MSSQL, and dbms_pipe.receive_message for Oracle. Union-based payloads with incrementing NULL columns determine the column count for data extraction.

Which bug bounty findings are always rejected by programs?

Always-rejected findings include missing security headers, SPF/DKIM/DMARC issues, self-XSS, logout CSRF, open redirects without a chain, clickjacking without a sensitive-action PoC, and banner disclosure without a working CVE exploit. Submitting these hurts your validity ratio.

Do classic HTTP request smuggling payloads still work against modern servers?

Classic CL.TE and TE.CL payloads no longer work against Nginx 1.21+, Caddy 2.x, or Envoy 1.20+, but remain effective against HAProxy 2.4 and older, older F5 BIG-IP, Citrix ADC, and some AWS ALB configurations. Fingerprint the front-end server before attempting smuggling.

How do I confirm blind vulnerabilities without false positives?

Use out-of-band confirmation: trigger a DNS or HTTP callback to Burp Collaborator or interactsh and verify the interaction before filing. For timing-based oracles, run at least 10 interleaved trials and require a Welch's t-statistic above 3 to separate signal from noise.

When is an open redirect reportable in bug bounty programs?

An open redirect alone is always rejected. It becomes reportable only when chained into proven impact, such as OAuth authorization code theft via redirect_uri abuse leading to account takeover, which typically rates Critical.