[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PZFPV9RJHRD4RY3102DAH":3,"skill-same:01M75PZFPV9RJHRD4RY3102DAH":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75PZFPV9RJHRD4RY3102DAH","opsec",null,"Operational security management — traffic shaping, scan rate limiting, source IP management, tool signature avoidance, evidence handling, anti-detection patterns.","Iwakishirokoshu\u002FHermesUltimate","Iwakishirokoshu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194847626?v=4","01M75P4CVGA89TTCE8JGMNAQQ9","Around","01M75P4CWF85V6GVSEFKGGFZ03",0,"MIT","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fshared\u002Fopsec\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: opsec\ndescription: \"Operational security management — traffic shaping, scan rate limiting, source IP management, tool signature avoidance, evidence handling, anti-detection patterns.\"\nallowed-tools: Bash Read\nmetadata:\n  subdomain: opsec\n  when_to_use: \"OPSEC check, rate limit, stealth, detection avoidance, scan timing, user-agent, scope check, evidence handling, clean up, anti-detection\"\n  tags: opsec, stealth, rate-limit, user-agent, scope-check, evidence-handling, anti-detection\n  mitre_attack: T1562, T1070, T1036\n---\n\n# Operational Security (OPSEC) Knowledge Base\n\nOPSEC ensures the red team engagement remains covert, controlled, and within authorized scope. Poor OPSEC burns the engagement — detected scans alert the blue team, taint findings, and waste client resources. This skill applies across all recon phases.\n\n## 1. Core OPSEC Principles\n\n### The OPSEC Mindset\n1. **Every packet is a signal** — assume the target has IDS\u002FIPS, SIEM, and SOC analysts\n2. **Minimize footprint** — collect only what you need, no more\n3. **Blend with normal traffic** — timing, volume, and patterns should look legitimate\n4. **Know your tools' signatures** — every scanner has a fingerprint\n5. **Document everything** — if you can't prove it was authorized, it wasn't\n\n### Engagement Scope Awareness\nBefore ANY active operation:\n- [ ] Written Rules of Engagement (ROE) on file\n- [ ] Target IP ranges and domains explicitly listed\n- [ ] Out-of-scope assets clearly identified\n- [ ] Testing window defined (dates, times)\n- [ ] Emergency contact for the client (for accidental impact)\n- [ ] Get-out-of-jail letter accessible\n\n## 2. Network OPSEC\n\n### Scan Rate Limiting\n\n| Target Type | Recommended Rate | Timing Flag |\n|-------------|-----------------|-------------|\n| Production web server | 5-10 req\u002Fsec | nmap `-T2` |\n| Internal network | 50-100 req\u002Fsec | nmap `-T3` |\n| Development\u002Fstaging | 100+ req\u002Fsec | nmap `-T4` |\n| High-security target | 1-2 req\u002Fsec | nmap `-T1` |\n| WAF-protected | 1-5 req\u002Fsec | Custom delays |\n\n### Traffic Shaping\n```bash\n# nmap with specific rate limiting\nnmap -sS --max-rate 10 --max-retries 1 -p 80,443 \u003Ctarget>\n\n# ffuf with rate limiting\nffuf -u https:\u002F\u002F\u003Ctarget>\u002FFUZZ -w wordlist.txt -rate 5\n\n# nuclei with rate limiting\nnuclei -u https:\u002F\u002F\u003Ctarget> -rl 5 -c 2\n\n# curl with delay between requests\nfor url in $(cat urls.txt); do\n    curl -s -o \u002Fdev\u002Fnull -w \"%{http_code} $url\\n\" \"$url\"\n    sleep 2\ndone\n```\n\n### Timing Considerations\n- **Business hours (9am-5pm target timezone)**: Higher baseline traffic → scanning blends in\n- **Weekends\u002Fholidays**: Lower baseline → scans stand out more\n- **Maintenance windows**: If known, ideal for aggressive scanning\n- **Burst vs sustained**: Short bursts with long pauses are less detectable than sustained scanning\n\n## 3. HTTP OPSEC\n\n### User-Agent Management\n\n> **Important**: User-Agent strings become stale quickly. Always use **current** browser version strings that match real-world traffic at the time of engagement. Check your own browser's UA or query a live UA database before starting.\n\n```bash\n# Step 1: Get a current, real User-Agent from your own browser or a live source\n# Option A: Copy from your browser's DevTools (Network tab → Request Headers)\n# Option B: Use a curated list — update version numbers to match current releases\n\n# Step 2: Build a rotation list with CURRENT versions\n# Template — replace \u003CCHROME_VER> and \u003CFIREFOX_VER> with latest stable versions\nUA_LIST=(\n    \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36 (KHTML, like Gecko) Chrome\u002F\u003CCHROME_VER> Safari\u002F537.36\"\n    \"Mozilla\u002F5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit\u002F537.36 (KHTML, like Gecko) Chrome\u002F\u003CCHROME_VER> Safari\u002F537.36\"\n    \"Mozilla\u002F5.0 (X11; Linux x86_64; rv:\u003CFIREFOX_VER>) Gecko\u002F20100101 Firefox\u002F\u003CFIREFOX_VER>\"\n    \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64; rv:\u003CFIREFOX_VER>) Gecko\u002F20100101 Firefox\u002F\u003CFIREFOX_VER>\"\n)\nUA=\"${UA_LIST[$RANDOM % ${#UA_LIST[@]}]}\"\n\ncurl -s -A \"$UA\" https:\u002F\u002F\u003Ctarget>\u002F\n\n# ffuf with custom user agent\nffuf -u https:\u002F\u002F\u003Ctarget>\u002FFUZZ -w wordlist.txt -H \"User-Agent: $UA\"\n```\n\n### Header Hygiene\n```bash\n# Avoid tool-specific headers that reveal scanner identity\n# BAD: Default tool user agents\n# - \"Nmap Scripting Engine\"\n# - \"nikto\"\n# - \"gobuster\"\n# - \"sqlmap\"\n\n# GOOD: Mimic real browser headers (use current browser versions!)\ncurl -s https:\u002F\u002F\u003Ctarget>\u002F \\\n    -H \"User-Agent: Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36 Chrome\u002F\u003CCURRENT_VER> Safari\u002F537.36\" \\\n    -H \"Accept: text\u002Fhtml,application\u002Fxhtml+xml,application\u002Fxml;q=0.9,image\u002Fwebp,*\u002F*;q=0.8\" \\\n    -H \"Accept-Language: en-US,en;q=0.9\" \\\n    -H \"Accept-Encoding: gzip, deflate, br\"\n```\n\n## 4. Tool Signature Awareness\n\n### Common IDS\u002FWAF Signatures\n\n| Tool | Detection Signature | Mitigation |\n|------|-------------------|------------|\n| nmap | SYN scan pattern, probe ordering | Use `-T2`, `--data-length` |\n| nikto | Default User-Agent, predictable paths | Custom UA, selective tuning |\n| sqlmap | Parameter tampering patterns | Not applicable to recon phase |\n| ffuf | Rapid sequential requests | Rate limiting (`-rate`) |\n| nuclei | Template-specific payloads | Rate limiting (`-rl`), selective templates |\n| gobuster | Sequential path enumeration | Randomize wordlist, rate limit |\n\n### Reducing Scanner Fingerprint\n```bash\n# nmap — add random data to packets\nnmap -sS --data-length 24 -T2 \u003Ctarget>\n\n# nmap — randomize host order (for multi-target)\nnmap -sS --randomize-hosts -iL targets.txt\n\n# nmap — spoof source port (use common ports)\nnmap -sS -g 53 \u003Ctarget>  # Appear as DNS traffic\nnmap -sS -g 80 \u003Ctarget>  # Appear as HTTP traffic\n```\n\n## 5. Source Management\n\n### IP Awareness\n- **Know your egress IP**: `curl -s ifconfig.me`\n- **Single source**: All scans originate from the sandbox — the target will see one IP\n- **VPN\u002Fproxy considerations**: If engagement allows, rotate exit nodes\n- **Cloud instances**: Ephemeral cloud VMs provide disposable IPs\n\n### DNS OPSEC\n```bash\n# Use public resolvers to avoid leaking internal DNS queries\ndig @8.8.8.8 \u003Ctarget> A +short\ndig @1.1.1.1 \u003Ctarget> A +short\n\n# Don't use target's own DNS servers for recon queries\n# (they may log all queries from unknown sources)\n```\n\n## 6. Evidence & Data Handling\n\n### Engagement Documentation\nEvery action should be logged:\n```markdown\n| Timestamp (UTC) | Action | Target | Tool | Justification |\n|-----------------|--------|--------|------|---------------|\n| \u003CYYYY-MM-DD HH:MM> | SYN scan top 1000 | 10.0.1.50 | nmap | Passive recon identified as primary web server |\n| \u003CYYYY-MM-DD HH:MM> | Dir fuzzing | api.example.com | ffuf | Port 443 open, REST API suspected |\n```\n\n### Data Classification\n- **Workspace files**: All scan output goes to the engagement directory — treat as engagement artifacts\n- **Credentials found**: NEVER store in plaintext — immediately document and encrypt\n- **PII discovered**: Note existence, do not exfiltrate — document for client\n- **Client data**: Handle per engagement contract data handling requirements\n\n### Clean-Up Protocol\nAfter engagement:\n- [ ] All tools stopped\n- [ ] No persistent connections to target\n- [ ] Scan data secured per client requirements\n- [ ] Temporary files cleaned from sandbox\n- [ ] No data left on third-party services (Shodan searches, etc.)\n\n## 7. Scope Enforcement\n\n### Automated Scope Checking\n```bash\n# Before scanning, verify target is in scope\nSCOPE_FILE=\"scope.txt\"\nTARGET=\"10.0.1.50\"\n\nif grep -q \"$TARGET\" \"$SCOPE_FILE\" 2>\u002Fdev\u002Fnull; then\n    echo \"IN SCOPE — proceed\"\nelse\n    echo \"WARNING: $TARGET not found in scope file!\"\n    echo \"Verify before proceeding.\"\nfi\n```\n\n### Scope Boundaries\n- **IP ranges**: Only scan IPs explicitly listed in scope document\n- **Domains**: Only enumerate subdomains of authorized root domains\n- **Cloud resources**: Only test resources confirmed as client-owned\n- **Third-party services**: DO NOT test shared infrastructure (CDNs, SaaS platforms)\n- **Physical scope**: Only applicable if physical penetration test is authorized\n\n### Accidental Out-of-Scope\nIf you accidentally touch an out-of-scope system:\n1. **Stop immediately**\n2. **Document the incident** (timestamp, target, action taken)\n3. **Notify the engagement lead**\n4. **Do NOT attempt to \"clean up\" evidence** — this makes it worse\n\n## 8. Detection Indicators to Monitor\n\n### Signs You've Been Detected\n- **Connection resets**: Target suddenly dropping connections → firewall rule added\n- **Rate limiting**: 429 responses where 200s were before → WAF triggered\n- **IP block**: Timeouts on previously responsive hosts → IP banned\n- **Honeypot indicators**: Unusually easy targets, too-good-to-be-true services\n- **Tarpit responses**: Extremely slow responses → deliberately slowing scanner\n\n### Response to Detection\n1. **Pause all scanning** — at least 30 minutes\n2. **Assess what triggered detection** — review recent scan patterns\n3. **Reduce scan rate** by 50-75%\n4. **Consider different approach** — passive only for a period\n5. **Document the detection event** for engagement report\n\n## 9. OPSEC Checklist (Pre-Engagement)\n\n- [ ] ROE document reviewed and understood\n- [ ] Scope file created at `scope.txt`\n- [ ] Emergency client contact accessible\n- [ ] Egress IP noted: `curl -s ifconfig.me`\n- [ ] Tool user agents configured (non-default)\n- [ ] Scan rate limits configured per target type\n- [ ] Output directory structure created\n- [ ] Evidence logging template ready\n- [ ] Clean-up protocol documented\n","# Operational Security (OPSEC) Knowledge Base\n\nOPSEC ensures the red team engagement remains covert, controlled, and within authorized scope. Poor OPSEC burns the engagement — detected scans alert the blue team, taint findings, and waste client resources. This skill applies across all recon phases.\n\n## 1. Core OPSEC Principles\n\n### The OPSEC Mindset\n1. **Every packet is a signal** — assume the target has IDS\u002FIPS, SIEM, and SOC analysts\n2. **Minimize footprint** — collect only what you need, no more\n3. **Blend with normal traffic** — timing, volume, and patterns should look legitimate\n4. **Know your tools' signatures** — every scanner has a fingerprint\n5. **Document everything** — if you can't prove it was authorized, it wasn't\n\n### Engagement Scope Awareness\nBefore ANY active operation:\n- [ ] Written Rules of Engagement (ROE) on file\n- [ ] Target IP ranges and domains explicitly listed\n- [ ] Out-of-scope assets clearly identified\n- [ ] Testing window defined (dates, times)\n- [ ] Emergency contact for the client (for accidental impact)\n- [ ] Get-out-of-jail letter accessible\n\n## 2. Network OPSEC\n\n### Scan Rate Limiting\n\n| Target Type | Recommended Rate | Timing Flag |\n|-------------|-----------------|-------------|\n| Production web server | 5-10 req\u002Fsec | nmap `-T2` |\n| Internal network | 50-100 req\u002Fsec | nmap `-T3` |\n| Development\u002Fstaging | 100+ req\u002Fsec | nmap `-T4` |\n| High-security target | 1-2 req\u002Fsec | nmap `-T1` |\n| WAF-protected | 1-5 req\u002Fsec | Custom delays |\n\n### Traffic Shaping\n```bash\n# nmap with specific rate limiting\nnmap -sS --max-rate 10 --max-retries 1 -p 80,443 \u003Ctarget>\n\n# ffuf with rate limiting\nffuf -u https:\u002F\u002F\u003Ctarget>\u002FFUZZ -w wordlist.txt -rate 5\n\n# nuclei with rate limiting\nnuclei -u https:\u002F\u002F\u003Ctarget> -rl 5 -c 2\n\n# curl with delay between requests\nfor url in $(cat urls.txt); do\n    curl -s -o \u002Fdev\u002Fnull -w \"%{http_code} $url\\n\" \"$url\"\n    sleep 2\ndone\n```\n\n### Timing Considerations\n- **Business hours (9am-5pm target timezone)**: Higher baseline traffic → scanning blends in\n- **Weekends\u002Fholidays**: Lower baseline → scans stand out more\n- **Maintenance windows**: If known, ideal for aggressive scanning\n- **Burst vs sustained**: Short bursts with long pauses are less detectable than sustained scanning\n\n## 3. HTTP OPSEC\n\n### User-Agent Management\n\n> **Important**: User-Agent strings become stale quickly. Always use **current** browser version strings that match real-world traffic at the time of engagement. Check your own browser's UA or query a live UA database before starting.\n\n```bash\n# Step 1: Get a current, real User-Agent from your own browser or a live source\n# Option A: Copy from your browser's DevTools (Network tab → Request Headers)\n# Option B: Use a curated list — update version numbers to match current releases\n\n# Step 2: Build a rotation list with CURRENT versions\n# Template — replace \u003CCHROME_VER> and \u003CFIREFOX_VER> with latest stable versions\nUA_LIST=(\n    \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36 (KHTML, like Gecko) Chrome\u002F\u003CCHROME_VER> Safari\u002F537.36\"\n    \"Mozilla\u002F5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit\u002F537.36 (KHTML, like Gecko) Chrome\u002F\u003CCHROME_VER> Safari\u002F537.36\"\n    \"Mozilla\u002F5.0 (X11; Linux x86_64; rv:\u003CFIREFOX_VER>) Gecko\u002F20100101 Firefox\u002F\u003CFIREFOX_VER>\"\n    \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64; rv:\u003CFIREFOX_VER>) Gecko\u002F20100101 Firefox\u002F\u003CFIREFOX_VER>\"\n)\nUA=\"${UA_LIST[$RANDOM % ${#UA_LIST[@]}]}\"\n\ncurl -s -A \"$UA\" https:\u002F\u002F\u003Ctarget>\u002F\n\n# ffuf with custom user agent\nffuf -u https:\u002F\u002F\u003Ctarget>\u002FFUZZ -w wordlist.txt -H \"User-Agent: $UA\"\n```\n\n### Header Hygiene\n```bash\n# Avoid tool-specific headers that reveal scanner identity\n# BAD: Default tool user agents\n# - \"Nmap Scripting Engine\"\n# - \"nikto\"\n# - \"gobuster\"\n# - \"sqlmap\"\n\n# GOOD: Mimic real browser headers (use current browser versions!)\ncurl -s https:\u002F\u002F\u003Ctarget>\u002F \\\n    -H \"User-Agent: Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36 Chrome\u002F\u003CCURRENT_VER> Safari\u002F537.36\" \\\n    -H \"Accept: text\u002Fhtml,application\u002Fxhtml+xml,application\u002Fxml;q=0.9,image\u002Fwebp,*\u002F*;q=0.8\" \\\n    -H \"Accept-Language: en-US,en;q=0.9\" \\\n    -H \"Accept-Encoding: gzip, deflate, br\"\n```\n\n## 4. Tool Signature Awareness\n\n### Common IDS\u002FWAF Signatures\n\n| Tool | Detection Signature | Mitigation |\n|------|-------------------|------------|\n| nmap | SYN scan pattern, probe ordering | Use `-T2`, `--data-length` |\n| nikto | Default User-Agent, predictable paths | Custom UA, selective tuning |\n| sqlmap | Parameter tampering patterns | Not applicable to recon phase |\n| ffuf | Rapid sequential requests | Rate limiting (`-rate`) |\n| nuclei | Template-specific payloads | Rate limiting (`-rl`), selective templates |\n| gobuster | Sequential path enumeration | Randomize wordlist, rate limit |\n\n### Reducing Scanner Fingerprint\n```bash\n# nmap — add random data to packets\nnmap -sS --data-length 24 -T2 \u003Ctarget>\n\n# nmap — randomize host order (for multi-target)\nnmap -sS --randomize-hosts -iL targets.txt\n\n# nmap — spoof source port (use common ports)\nnmap -sS -g 53 \u003Ctarget>  # Appear as DNS traffic\nnmap -sS -g 80 \u003Ctarget>  # Appear as HTTP traffic\n```\n\n## 5. Source Management\n\n### IP Awareness\n- **Know your egress IP**: `curl -s ifconfig.me`\n- **Single source**: All scans originate from the sandbox — the target will see one IP\n- **VPN\u002Fproxy considerations**: If engagement allows, rotate exit nodes\n- **Cloud instances**: Ephemeral cloud VMs provide disposable IPs\n\n### DNS OPSEC\n```bash\n# Use public resolvers to avoid leaking internal DNS queries\ndig @8.8.8.8 \u003Ctarget> A +short\ndig @1.1.1.1 \u003Ctarget> A +short\n\n# Don't use target's own DNS servers for recon queries\n# (they may log all queries from unknown sources)\n```\n\n## 6. Evidence & Data Handling\n\n### Engagement Documentation\nEvery action should be logged:\n```markdown\n| Timestamp (UTC) | Action | Target | Tool | Justification |\n|-----------------|--------|--------|------|---------------|\n| \u003CYYYY-MM-DD HH:MM> | SYN scan top 1000 | 10.0.1.50 | nmap | Passive recon identified as primary web server |\n| \u003CYYYY-MM-DD HH:MM> | Dir fuzzing | api.example.com | ffuf | Port 443 open, REST API suspected |\n```\n\n### Data Classification\n- **Workspace files**: All scan output goes to the engagement directory — treat as engagement artifacts\n- **Credentials found**: NEVER store in plaintext — immediately document and encrypt\n- **PII discovered**: Note existence, do not exfiltrate — document for client\n- **Client data**: Handle per engagement contract data handling requirements\n\n### Clean-Up Protocol\nAfter engagement:\n- [ ] All tools stopped\n- [ ] No persistent connections to target\n- [ ] Scan data secured per client requirements\n- [ ] Temporary files cleaned from sandbox\n- [ ] No data left on third-party services (Shodan searches, etc.)\n\n## 7. Scope Enforcement\n\n### Automated Scope Checking\n```bash\n# Before scanning, verify target is in scope\nSCOPE_FILE=\"scope.txt\"\nTARGET=\"10.0.1.50\"\n\nif grep -q \"$TARGET\" \"$SCOPE_FILE\" 2>\u002Fdev\u002Fnull; then\n    echo \"IN SCOPE — proceed\"\nelse\n    echo \"WARNING: $TARGET not found in scope file!\"\n    echo \"Verify before proceeding.\"\nfi\n```\n\n### Scope Boundaries\n- **IP ranges**: Only scan IPs explicitly listed in scope document\n- **Domains**: Only enumerate subdomains of authorized root domains\n- **Cloud resources**: Only test resources confirmed as client-owned\n- **Third-party services**: DO NOT test shared infrastructure (CDNs, SaaS platforms)\n- **Physical scope**: Only applicable if physical penetration test is authorized\n\n### Accidental Out-of-Scope\nIf you accidentally touch an out-of-scope system:\n1. **Stop immediately**\n2. **Document the incident** (timestamp, target, action taken)\n3. **Notify the engagement lead**\n4. **Do NOT attempt to \"clean up\" evidence** — this makes it worse\n\n## 8. Detection Indicators to Monitor\n\n### Signs You've Been Detected\n- **Connection resets**: Target suddenly dropping connections → firewall rule added\n- **Rate limiting**: 429 responses where 200s were before → WAF triggered\n- **IP block**: Timeouts on previously responsive hosts → IP banned\n- **Honeypot indicators**: Unusually easy targets, too-good-to-be-true services\n- **Tarpit responses**: Extremely slow responses → deliberately slowing scanner\n\n### Response to Detection\n1. **Pause all scanning** — at least 30 minutes\n2. **Assess what triggered detection** — review recent scan patterns\n3. **Reduce scan rate** by 50-75%\n4. **Consider different approach** — passive only for a period\n5. **Document the detection event** for engagement report\n\n## 9. OPSEC Checklist (Pre-Engagement)\n\n- [ ] ROE document reviewed and understood\n- [ ] Scope file created at `scope.txt`\n- [ ] Emergency client contact accessible\n- [ ] Egress IP noted: `curl -s ifconfig.me`\n- [ ] Tool user agents configured (non-default)\n- [ ] Scan rate limits configured per target type\n- [ ] Output directory structure created\n- [ ] Evidence logging template ready\n- [ ] Clean-up protocol documented\n",{"name":5,"metadata":24,"description":7,"allowed-tools":28},{"tags":25,"subdomain":5,"when_to_use":26,"mitre_attack":27},"opsec, stealth, rate-limit, user-agent, scope-check, evidence-handling, anti-detection","OPSEC check, rate limit, stealth, detection avoidance, scan timing, user-agent, scope check, evidence handling, clean up, anti-detection","T1562, T1070, T1036","Bash Read","main","c0c483827a963764d5e1a663a9591867d47289e6","stack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fshared\u002Fopsec","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu","2026-06-15 13:48:41",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Iwakishirokoshu\u002FHermesUltimate --skill opsec",{"tool":41,"command":42},"bunx","bunx skills add Iwakishirokoshu\u002FHermesUltimate --skill opsec",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Iwakishirokoshu\u002FHermesUltimate --skill opsec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fshared\u002Fopsec\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M770W8JDE5EC1TJT4GSDWD78","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M770W4B7T5VCVHB88V1F02H1","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M770W093C8FAV8S34K8VB6T9","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M770VTNAQGZ3D0RQVFEKTE8Z","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M770VNG05ZX3CV84R9GX8PJN","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M770VHFH7N192V56PFSRXF5K","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]