[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M798MSZR174KZ5H9PRDYAQK5":3,"skill-same:01M798MSZR174KZ5H9PRDYAQK5":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},"01M798MSZR174KZ5H9PRDYAQK5","deep-analysis",null,"Depth-first RE investigation loop for a single binary or function cluster: decompile→rename→retype→comment→re-read, with context-rot guards and on-task checks. Use when triage has already identified the interesting area and the goal is full understanding: what does function X do, identify cryptographic primitives, locate C2 protocol, recover data structures. Triggers on: 'deep analysis', 'understand function', 'recover struct', 'crypto identification', 'C2 protocol', 'reverse this binary fully', 'what does this function do'.","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\u002Freverser\u002Fdeep-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deep-analysis\ndescription: \"Depth-first RE investigation loop for a single binary or function cluster: decompile→rename→retype→comment→re-read, with context-rot guards and on-task checks. Use when triage has already identified the interesting area and the goal is full understanding: what does function X do, identify cryptographic primitives, locate C2 protocol, recover data structures. Triggers on: 'deep analysis', 'understand function', 'recover struct', 'crypto identification', 'C2 protocol', 'reverse this binary fully', 'what does this function do'.\"\nallowed-tools: Bash Read Write\nmetadata:\n  subdomain: reverse-engineering\n  when_to_use: \"deep analysis understand function recover struct crypto identification C2 protocol reverse binary fully decompile rename retype comment ghidra\"\n  tags: reverse-engineering, ghidra, decompilation, static-analysis, deep-re\n  mitre_attack: T1027, T1055, T1129\n---\n\n# Deep Binary Analysis Loop\n\nDepth-first RE for full understanding of a specific target area. Distinct from\nbreadth-first triage (`reverser\u002Ftriage`) — here you don't stop at a signal,\nyou keep iterating until the function is fully understood.\n\n## Core Principle: Narrow → Deep\n\nTriage finds the surface; deep-analysis excavates one shaft. Commit to one\nquestion at a time. Context-rot (losing track of what you've already renamed\nor retyped) is the primary failure mode — guard against it explicitly.\n\n## 1. Entry Point\n\nBefore decompiling anything, state the question in writing:\n\n```\nkg_add_node(\"hypothesis\", \"deep-analysis target\",\n  props={\"question\": \"\u003Cexact question, e.g. 'what does sub_401A20 do'>\",\n         \"binary\": \"\u002Fworkspace\u002Ftarget\",\n         \"entry_function\": \"\u003Chex addr or name>\",\n         \"key\": \"deep-analysis:entry\"})\n```\n\nCommit to one question. Do not pivot mid-session unless the current\nfunction is fully annotated and the answer is \"it delegates to X\".\n\n## 2. Decompile→Rename→Retype→Comment Loop\n\nFor each function under analysis, follow this cycle exactly:\n\n### 2a. Decompile\n```\nghidra_decompile(binary=\"\u002Fworkspace\u002Ftarget\", function=\"\u003Caddr_or_name>\")\n```\nRead the full output before touching anything.\n\n### 2b. Rename all locals and parameters\nAs soon as you understand a variable's purpose, rename it immediately:\n```bash\n# Via Ghidra MCP batch rename (preferred — one round trip)\n# collect all your renames first, then batch:\nghidra_batch_rename(binary=\"\u002Fworkspace\u002Ftarget\", renames={\n  \"sub_401A20\": \"decrypt_config_blob\",\n  \"local_18\": \"key_len\",\n  \"param_1\": \"encrypted_buf\",\n  \"param_2\": \"buf_len\"\n})\n```\nDo not leave a decompiled function with placeholder names (`param_1`,\n`local_8`, `uVar1`) if you know what they are.\n\n### 2c. Retype parameters and locals\nCorrect types catch bugs in decompiler reasoning:\n```bash\n# If param_1 is char* not int\nghidra_retype(binary=\"\u002Fworkspace\u002Ftarget\", symbol=\"decrypt_config_blob::param_1\", type=\"char *\")\nghidra_retype(binary=\"\u002Fworkspace\u002Ftarget\", symbol=\"decrypt_config_blob::local_18\", type=\"uint32_t\")\n```\nPay special attention to: size_t vs int (sign confusion), pointer-as-int\npatterns, struct pointer vs void*, callback function pointers.\n\n### 2d. Add inline comments\nAt every branch point whose purpose is now understood:\n```bash\nghidra_set_comment(binary=\"\u002Fworkspace\u002Ftarget\", address=\"0x401A3C\",\n  comment=\"XOR-decrypts single byte: key[i % key_len] ^ buf[i]\")\n```\n\n### 2e. Re-read the decompilation\nAfter rename+retype, decompile again. The output will often look\ndramatically cleaner and reveal previously hidden logic.\n\nRepeat 2a–2e until the function's purpose is unambiguous.\n\n## 3. On-Task Check (every 3–5 tool calls)\n\nAfter each batch of tool calls, answer explicitly:\n\n1. Is the current function still the right place to dig?\n2. Have I renamed every local\u002Fparam I now understand?\n3. Have I documented what this function does (even partially) in the KG?\n4. Am I still working toward the original question, or have I drifted?\n\nIf you've called into a callee 3+ levels deep without updating the KG,\nthat's context-rot — surface the findings upward before going deeper.\n\n```\nkg_add_node(\"note\", \"deep-analysis progress\",\n  props={\"function\": \"decrypt_config_blob\",\n         \"finding\": \"RC4 variant — XOR stream cipher, 16-byte key from .rdata:0x40D0C0\",\n         \"status\": \"complete\",\n         \"key\": \"deep-analysis:decrypt_config_blob\"})\n```\n\n## 4. Per-Question Strategies\n\n### \"What does function X do?\"\n\n1. Decompile X.\n2. List all callees: `ghidra_xrefs(binary=..., address=X)`.\n3. For each callee, check if it's a library stub (look up import table) or\n   custom code. Library stubs → infer semantics from function name. Custom\n   code → recurse one level.\n4. Draw the call path as a KG `calls` edge chain.\n5. Answer: input\u002Foutput contract, side effects, return value semantics.\n\n### \"Identify crypto primitive\"\n\nHigh-entropy constants are the fastest path:\n```bash\n# Search for known crypto constants (AES S-box, RC4 init, ChaCha sigma, etc.)\ngrep -r \"0x63636363\\|0x6B617479\\|0xE2280613\\|0xDB3D18\\|0x61707865\\|0x3320646E\" \\\n  \u002Fworkspace\u002Ftarget.bin 2>\u002Fdev\u002Fnull || true\n\n# Capa identifies crypto more reliably\ncapa \u002Fworkspace\u002Ftarget --json > \u002Fworkspace\u002Fcapa_crypto.json\ncat \u002Fworkspace\u002Fcapa_crypto.json | python3 -c \"\nimport json, sys\nd = json.load(sys.stdin)\nfor r in d.get('rules', {}).values():\n    if 'crypto' in r.get('rule',{}).get('namespace','').lower():\n        print(r['rule']['name'])\n\"\n```\n\nConstants to recognize:\n| Constant | Algorithm |\n|----------|-----------|\n| `0x61707865` \u002F `expand 32-byte k` | ChaCha20 \u002F Salsa20 |\n| AES S-box start `0x63,0x7c,0x77,0x7b` | AES |\n| `0x67452301,0xEFCDAB89` | MD5 init |\n| `0x6A09E667,0xBB67AE85` | SHA-256 init |\n| `0x9E3779B9` | TEA \u002F XTEA Δ |\n| `0xB7E15163,0x9E3779B9` | RC5\u002FRC6 magic |\n| Byte-by-byte XOR loop with index-mod key | RC4 or custom XOR |\n\nOnce identified, rename the function accordingly and document the key\nschedule location if observable.\n\n### \"Find C2 protocol \u002F config decryption\"\n\n1. Start from network sinks: search imports for `connect`, `WSAConnect`,\n   `send`, `write`, `curl_easy_perform`.\n2. Follow xrefs upward from the sink to find the function that builds the\n   buffer — that's likely the protocol serializer.\n3. Look for the decryption stub called at startup or on first network\n   connect — it usually reads from a hardcoded blob in `.data` or `.rdata`.\n4. Identify config blob location:\n   ```bash\n   # Find all large-ish .rdata blobs (>16 bytes, high entropy)\n   python3 -c \"\n   import pefile, math\n   pe = pefile.PE('\u002Fworkspace\u002Ftarget.exe')\n   for s in pe.sections:\n       if b'.rdata' in s.Name:\n           data = s.get_data()\n           # scan in 16-byte windows\n           for off in range(0, len(data)-16, 4):\n               chunk = data[off:off+16]\n               counts = [chunk.count(bytes([b])) for b in range(256)]\n               ent = -sum((c\u002F16)*math.log2(c\u002F16) for c in counts if c)\n               if ent > 7.0:\n                   print(hex(s.VirtualAddress + off), 'entropy', round(ent,2))\n   \" 2>\u002Fdev\u002Fnull | head -20\n   ```\n5. Decompile the decrypt stub. Rename it `decrypt_c2_config`. Document\n   algorithm + key in KG.\n\n## 5. Struct Recovery\n\nWhen you see pointer arithmetic into a struct you don't have a definition for:\n\n1. Note the maximum offset accessed (e.g. `[param_1 + 0x28]`).\n2. Create a Ghidra struct: `ghidra_create_struct(name=\"Config\", size=0x30)`.\n3. Add fields as you discover their types:\n   ```\n   ghidra_add_field(struct=\"Config\", offset=0x00, type=\"char[16]\", name=\"key\")\n   ghidra_add_field(struct=\"Config\", offset=0x10, type=\"char[64]\", name=\"c2_host\")\n   ghidra_add_field(struct=\"Config\", offset=0x50, type=\"uint16_t\", name=\"c2_port\")\n   ```\n4. Apply the struct type to all uses of param_1.\n5. Re-decompile — member names will appear in the pseudocode.\n\n## 6. Context-Rot Prevention Rules\n\n- Never go more than 3 callees deep without writing a KG note.\n- If you have renamed 5+ functions, update the entry hypothesis with a\n  \"state_so_far\" field.\n- If a function's purpose is \"unclear after full loop\", mark it `status:blocked`\n  and surface to orchestrator rather than spiraling.\n- Keep a breadcrumb: before entering a callee, record the parent and\n  what you expect to learn from the callee.\n\n## 7. Completion Gate\n\nThe deep-analysis session is done when:\n- The original question is answered and documented in KG\n- All functions touched have at least a rename + one-line comment\n- Crypto primitives identified (or confirmed absent)\n- C2 config location\u002Fformat documented (if applicable)\n- Struct definitions created for all major data types\n\n```\nkg_add_node(\"finding\", \"deep-analysis complete\",\n  props={\"question\": \"\u003Coriginal question>\",\n         \"answer\": \"\u003Cconcise answer>\",\n         \"key_functions\": [\"decrypt_config_blob\", \"build_beacon_packet\"],\n         \"crypto\": \"ChaCha20 — key at .data:0x40E0A0\",\n         \"c2_format\": \"TLV over TCP port 4444\",\n         \"key\": \"deep-analysis:complete\"})\n```\n\n## Tools\n\n| Tool | Purpose |\n|------|---------|\n| `ghidra_decompile` | C pseudocode for a function |\n| `ghidra_batch_rename` | Rename multiple symbols in one call |\n| `ghidra_retype` | Fix type annotations |\n| `ghidra_xrefs` | Callers \u002F callees of an address |\n| `ghidra_create_struct` | Define a data structure |\n| `capa` | High-level capability + crypto detection |\n| `pefile` \u002F `lief` | PE\u002FELF structure access from Python |\n","# Deep Binary Analysis Loop\n\nDepth-first RE for full understanding of a specific target area. Distinct from\nbreadth-first triage (`reverser\u002Ftriage`) — here you don't stop at a signal,\nyou keep iterating until the function is fully understood.\n\n## Core Principle: Narrow → Deep\n\nTriage finds the surface; deep-analysis excavates one shaft. Commit to one\nquestion at a time. Context-rot (losing track of what you've already renamed\nor retyped) is the primary failure mode — guard against it explicitly.\n\n## 1. Entry Point\n\nBefore decompiling anything, state the question in writing:\n\n```\nkg_add_node(\"hypothesis\", \"deep-analysis target\",\n  props={\"question\": \"\u003Cexact question, e.g. 'what does sub_401A20 do'>\",\n         \"binary\": \"\u002Fworkspace\u002Ftarget\",\n         \"entry_function\": \"\u003Chex addr or name>\",\n         \"key\": \"deep-analysis:entry\"})\n```\n\nCommit to one question. Do not pivot mid-session unless the current\nfunction is fully annotated and the answer is \"it delegates to X\".\n\n## 2. Decompile→Rename→Retype→Comment Loop\n\nFor each function under analysis, follow this cycle exactly:\n\n### 2a. Decompile\n```\nghidra_decompile(binary=\"\u002Fworkspace\u002Ftarget\", function=\"\u003Caddr_or_name>\")\n```\nRead the full output before touching anything.\n\n### 2b. Rename all locals and parameters\nAs soon as you understand a variable's purpose, rename it immediately:\n```bash\n# Via Ghidra MCP batch rename (preferred — one round trip)\n# collect all your renames first, then batch:\nghidra_batch_rename(binary=\"\u002Fworkspace\u002Ftarget\", renames={\n  \"sub_401A20\": \"decrypt_config_blob\",\n  \"local_18\": \"key_len\",\n  \"param_1\": \"encrypted_buf\",\n  \"param_2\": \"buf_len\"\n})\n```\nDo not leave a decompiled function with placeholder names (`param_1`,\n`local_8`, `uVar1`) if you know what they are.\n\n### 2c. Retype parameters and locals\nCorrect types catch bugs in decompiler reasoning:\n```bash\n# If param_1 is char* not int\nghidra_retype(binary=\"\u002Fworkspace\u002Ftarget\", symbol=\"decrypt_config_blob::param_1\", type=\"char *\")\nghidra_retype(binary=\"\u002Fworkspace\u002Ftarget\", symbol=\"decrypt_config_blob::local_18\", type=\"uint32_t\")\n```\nPay special attention to: size_t vs int (sign confusion), pointer-as-int\npatterns, struct pointer vs void*, callback function pointers.\n\n### 2d. Add inline comments\nAt every branch point whose purpose is now understood:\n```bash\nghidra_set_comment(binary=\"\u002Fworkspace\u002Ftarget\", address=\"0x401A3C\",\n  comment=\"XOR-decrypts single byte: key[i % key_len] ^ buf[i]\")\n```\n\n### 2e. Re-read the decompilation\nAfter rename+retype, decompile again. The output will often look\ndramatically cleaner and reveal previously hidden logic.\n\nRepeat 2a–2e until the function's purpose is unambiguous.\n\n## 3. On-Task Check (every 3–5 tool calls)\n\nAfter each batch of tool calls, answer explicitly:\n\n1. Is the current function still the right place to dig?\n2. Have I renamed every local\u002Fparam I now understand?\n3. Have I documented what this function does (even partially) in the KG?\n4. Am I still working toward the original question, or have I drifted?\n\nIf you've called into a callee 3+ levels deep without updating the KG,\nthat's context-rot — surface the findings upward before going deeper.\n\n```\nkg_add_node(\"note\", \"deep-analysis progress\",\n  props={\"function\": \"decrypt_config_blob\",\n         \"finding\": \"RC4 variant — XOR stream cipher, 16-byte key from .rdata:0x40D0C0\",\n         \"status\": \"complete\",\n         \"key\": \"deep-analysis:decrypt_config_blob\"})\n```\n\n## 4. Per-Question Strategies\n\n### \"What does function X do?\"\n\n1. Decompile X.\n2. List all callees: `ghidra_xrefs(binary=..., address=X)`.\n3. For each callee, check if it's a library stub (look up import table) or\n   custom code. Library stubs → infer semantics from function name. Custom\n   code → recurse one level.\n4. Draw the call path as a KG `calls` edge chain.\n5. Answer: input\u002Foutput contract, side effects, return value semantics.\n\n### \"Identify crypto primitive\"\n\nHigh-entropy constants are the fastest path:\n```bash\n# Search for known crypto constants (AES S-box, RC4 init, ChaCha sigma, etc.)\ngrep -r \"0x63636363\\|0x6B617479\\|0xE2280613\\|0xDB3D18\\|0x61707865\\|0x3320646E\" \\\n  \u002Fworkspace\u002Ftarget.bin 2>\u002Fdev\u002Fnull || true\n\n# Capa identifies crypto more reliably\ncapa \u002Fworkspace\u002Ftarget --json > \u002Fworkspace\u002Fcapa_crypto.json\ncat \u002Fworkspace\u002Fcapa_crypto.json | python3 -c \"\nimport json, sys\nd = json.load(sys.stdin)\nfor r in d.get('rules', {}).values():\n    if 'crypto' in r.get('rule',{}).get('namespace','').lower():\n        print(r['rule']['name'])\n\"\n```\n\nConstants to recognize:\n| Constant | Algorithm |\n|----------|-----------|\n| `0x61707865` \u002F `expand 32-byte k` | ChaCha20 \u002F Salsa20 |\n| AES S-box start `0x63,0x7c,0x77,0x7b` | AES |\n| `0x67452301,0xEFCDAB89` | MD5 init |\n| `0x6A09E667,0xBB67AE85` | SHA-256 init |\n| `0x9E3779B9` | TEA \u002F XTEA Δ |\n| `0xB7E15163,0x9E3779B9` | RC5\u002FRC6 magic |\n| Byte-by-byte XOR loop with index-mod key | RC4 or custom XOR |\n\nOnce identified, rename the function accordingly and document the key\nschedule location if observable.\n\n### \"Find C2 protocol \u002F config decryption\"\n\n1. Start from network sinks: search imports for `connect`, `WSAConnect`,\n   `send`, `write`, `curl_easy_perform`.\n2. Follow xrefs upward from the sink to find the function that builds the\n   buffer — that's likely the protocol serializer.\n3. Look for the decryption stub called at startup or on first network\n   connect — it usually reads from a hardcoded blob in `.data` or `.rdata`.\n4. Identify config blob location:\n   ```bash\n   # Find all large-ish .rdata blobs (>16 bytes, high entropy)\n   python3 -c \"\n   import pefile, math\n   pe = pefile.PE('\u002Fworkspace\u002Ftarget.exe')\n   for s in pe.sections:\n       if b'.rdata' in s.Name:\n           data = s.get_data()\n           # scan in 16-byte windows\n           for off in range(0, len(data)-16, 4):\n               chunk = data[off:off+16]\n               counts = [chunk.count(bytes([b])) for b in range(256)]\n               ent = -sum((c\u002F16)*math.log2(c\u002F16) for c in counts if c)\n               if ent > 7.0:\n                   print(hex(s.VirtualAddress + off), 'entropy', round(ent,2))\n   \" 2>\u002Fdev\u002Fnull | head -20\n   ```\n5. Decompile the decrypt stub. Rename it `decrypt_c2_config`. Document\n   algorithm + key in KG.\n\n## 5. Struct Recovery\n\nWhen you see pointer arithmetic into a struct you don't have a definition for:\n\n1. Note the maximum offset accessed (e.g. `[param_1 + 0x28]`).\n2. Create a Ghidra struct: `ghidra_create_struct(name=\"Config\", size=0x30)`.\n3. Add fields as you discover their types:\n   ```\n   ghidra_add_field(struct=\"Config\", offset=0x00, type=\"char[16]\", name=\"key\")\n   ghidra_add_field(struct=\"Config\", offset=0x10, type=\"char[64]\", name=\"c2_host\")\n   ghidra_add_field(struct=\"Config\", offset=0x50, type=\"uint16_t\", name=\"c2_port\")\n   ```\n4. Apply the struct type to all uses of param_1.\n5. Re-decompile — member names will appear in the pseudocode.\n\n## 6. Context-Rot Prevention Rules\n\n- Never go more than 3 callees deep without writing a KG note.\n- If you have renamed 5+ functions, update the entry hypothesis with a\n  \"state_so_far\" field.\n- If a function's purpose is \"unclear after full loop\", mark it `status:blocked`\n  and surface to orchestrator rather than spiraling.\n- Keep a breadcrumb: before entering a callee, record the parent and\n  what you expect to learn from the callee.\n\n## 7. Completion Gate\n\nThe deep-analysis session is done when:\n- The original question is answered and documented in KG\n- All functions touched have at least a rename + one-line comment\n- Crypto primitives identified (or confirmed absent)\n- C2 config location\u002Fformat documented (if applicable)\n- Struct definitions created for all major data types\n\n```\nkg_add_node(\"finding\", \"deep-analysis complete\",\n  props={\"question\": \"\u003Coriginal question>\",\n         \"answer\": \"\u003Cconcise answer>\",\n         \"key_functions\": [\"decrypt_config_blob\", \"build_beacon_packet\"],\n         \"crypto\": \"ChaCha20 — key at .data:0x40E0A0\",\n         \"c2_format\": \"TLV over TCP port 4444\",\n         \"key\": \"deep-analysis:complete\"})\n```\n\n## Tools\n\n| Tool | Purpose |\n|------|---------|\n| `ghidra_decompile` | C pseudocode for a function |\n| `ghidra_batch_rename` | Rename multiple symbols in one call |\n| `ghidra_retype` | Fix type annotations |\n| `ghidra_xrefs` | Callers \u002F callees of an address |\n| `ghidra_create_struct` | Define a data structure |\n| `capa` | High-level capability + crypto detection |\n| `pefile` \u002F `lief` | PE\u002FELF structure access from Python |\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"mitre_attack":28},"reverse-engineering, ghidra, decompilation, static-analysis, deep-re","reverse-engineering","deep analysis understand function recover struct crypto identification C2 protocol reverse binary fully decompile rename retype comment ghidra","T1027, T1055, T1129","Bash Read Write","main","42b918525fb79065e730da3da997bffb33fcd414","packages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Freverser\u002Fdeep-analysis",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 deep-analysis",{"tool":43,"command":44},"bunx","bunx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill deep-analysis",{"tool":46,"command":47},"pnpm","pnpm dlx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill deep-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Freverser\u002Fdeep-analysis\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",[],[]]