Reverse Engineering Router: Master Entry for RE Operations
Determines the artifact type, selects the correct specialized reverse engineering skill, and enforces methodology before tooling. All 48 RE skills in the catalog are reachable through this router.
Overview
reverse-engineering-router is the master entry for reverse engineering work: it classifies the target artifact (file format, architecture, platform), routes to the correct specialized skill, and ensures structured methodology over random tool usage. It maps 48 reverse-engineering skills into a deterministic decision tree.
When NOT to Use
- Authorized testing already scoped to a single deep technique — load the specialized skill directly (e.g., known Android malware: load
reverse-engineering-android-malware-with-jadx)
- Source code analysis — use static analysis tools instead (Semgrep, CodeQL)
- No artifact available (requirements-only tasks)
Verification
- Feed the router a scenario for each artifact class (native binary, Android APK, iOS app, JavaScript bundle, firmware image, .NET assembly, packed binary, malware sample) and confirm it routes to the correct specialist skill each time.
- Verify fallback to
reverse-engineer-anything-with-rea for unknown/ambiguous artifacts
Anti-Rationalization Table
| Excuse |
Reality |
Rule |
| "I'll just open it in Ghidra" |
Without identifying the format first, you'll waste hours on wrong architecture or wrong tool |
Route by artifact signature first |
| "The decompiler will figure it out" |
A PE binary opened as ELF produces garbage; wrong platform = wrong results |
Verify file type before tool selection |
| "I'll try all tools" |
Trial-and-error is not a methodology; it produces incomplete coverage |
Use the routing table below |
Routing Decision Table
The routing table is a lookup, not judgment-by-hand. Model it as data so the same decision is repeatable.
ROUTING_TABLE = [
# (matchers, primary_skill, fallback_skill)
({"ext": [".apk", ".dex", ".aab", ".smali"], "magic": ["PK\\x03\\x04"]},
"reverse-engineering-android-malware-with-jadx",
"analyzing-android-malware-with-apktool"),
({"ext": [".ipa", ".app"], "magic": ["Mach-O"]},
"reverse-engineering-ios-app-with-frida",
"analyzing-ios-app-security-with-objection"),
({"ext": [".exe", ".dll", ".sys"], "magic": ["MZ"]},
"binary-breaker",
"reverse-engineering-malware-with-ghidra"),
({"ext": [".so", ".bin", ".elf"], "magic": ["\\x7fELF"]},
"analyzing-linux-elf-malware",
"reverse-engineering-malware-with-ghidra"),
({"ext": [".js", ".mjs", ".ts", ".wasm"], "magic": []},
"js-reverse",
"dsl-vm-reverse"),
({"ext": [".bin", ".img", ".hex"], "magic": ["U-Boot", "squashfs", "cramfs", "jffs2"]},
"performing-firmware-extraction-with-binwalk",
"performing-firmware-malware-analysis"),
({"ext": [".exe", ".dll"], "magic": ["MZ"], "dotnet": True},
"reverse-engineering-dotnet-malware-with-dnspy",
"reverse-engineering-malware-with-ghidra"),
({"keywords": ["packed", "upx", "obfuscated", "stripped"]},
"analyzing-packed-malware-with-upx-unpacker",
"reverse-engineering-malware-with-ghidra"),
({"keywords": ["cobalt strike", "beacon", "c2"]},
"analyzing-cobalt-strike-beacon-configuration",
"reverse-engineering-malware-with-ghidra"),
({"keywords": ["agent tesla", "rat config"]},
"extracting-config-from-agent-tesla-rat",
"reverse-engineering-malware-with-ghidra"),
({"keywords": ["ransomware", "encryption routine"]},
"reverse-engineering-ransomware-encryption-routine",
"analyzing-ransomware-encryption-mechanisms"),
({"keywords": ["sandbox evasion", "anti-vm", "anti-debug"]},
"analyzing-malware-sandbox-evasion-techniques",
"performing-automated-malware-analysis-with-cape"),
({"keywords": ["yara", "ioc extraction", "malware triage"]},
"performing-malware-triage-with-yara",
"performing-malware-ioc-extraction"),
({"keywords": ["network traffic", "pcap", "covert channel"]},
"analyzing-network-traffic-of-malware",
"analyzing-network-covert-channels-in-malware"),
({"keywords": ["memory dump", "volatility", "forensics"]},
"performing-memory-forensics-with-volatility3-plugins",
"analyzing-disk-image-with-autopsy"),
({"keywords": ["go binary", "golang", "pclntab"]},
"go-rust-reverse",
"analyzing-golang-malware-with-ghidra"),
({"keywords": ["rust binary", "panic strings"]},
"reverse-engineering-rust-malware",
"go-rust-reverse"),
({"keywords": ["browser extension", "crx", "xpi"]},
"browser-extension-reverse",
"js-reverse"),
({"keywords": ["powershell", "obfuscated"]},
"deobfuscating-powershell-obfuscated-malware",
"deobfuscating-javascript-malware"),
({"keywords": ["plc", "s7comm", "ot", "ics"]},
"performing-plc-firmware-security-analysis",
"performing-firmware-malware-analysis"),
({"ext": [".pdf"], "keywords": ["peepdf", "malicious pdf", "stream"]},
"analyzing-malicious-pdf-with-peepdf",
"reverse-engineer-anything-with-rea"),
({"keywords": ["heap spray", "heap exploitation"]},
"analyzing-heap-spray-exploitation",
"performing-binary-exploitation-analysis"),
({"keywords": ["rootkit", "kernel module", "lkm", "vmlinux"]},
"analyzing-linux-kernel-rootkits",
"analyzing-linux-elf-malware"),
({"keywords": ["fuzzing", "afl", "harness", "crash triage"]},
"performing-fuzzing-with-aflplusplus",
"binary-breaker"),
({"keywords": ["persistence", "autoruns", "registry run"]},
"analyzing-malware-persistence-with-autoruns",
"performing-static-malware-analysis-with-pe-studio"),
({"keywords": ["supply chain", "malicious package", "typosquatting"]},
"analyzing-supply-chain-malware-artifacts",
"reverse-engineer-anything-with-rea"),
({"keywords": ["malware pipeline", "automated submission"]},
"building-automated-malware-submission-pipeline",
"performing-automated-malware-analysis-with-cape"),
({"keywords": ["virustotal", "hash enrichment", "reputation"]},
"performing-malware-hash-enrichment-with-virustotal",
"performing-malware-ioc-extraction"),
({"keywords": ["iot", "embedded device", "uart", "jtag"]},
"performing-iot-security-assessment",
"performing-firmware-extraction-with-binwalk"),
({"keywords": ["thick client", "fat client", "wpf", "electron"]},
"performing-thick-client-application-penetration-test",
"reverse-engineering-dotnet-malware-with-dnspy"),
({"keywords": ["prefetch", "windows execution artifact", "shimcache"]},
"analyzing-windows-prefetch-with-python",
"analyzing-malware-persistence-with-autoruns"),
]
def route(artifact_info: dict) -> tuple[str, str]:
"""Return (primary_skill, fallback_skill) or (None, 'reverse-engineer-anything-with-rea')"""
for matchers, primary, fallback in ROUTING_TABLE:
if all(artifact_info.get(k) in v for k, v in matchers.items() if k != "keywords"):
if "keywords" not in matchers or any(kw in artifact_info.get("text", "").lower() for kw in matchers["keywords"]):
return primary, fallback
return None, "reverse-engineer-anything-with-rea"
When to Use
Use when:
- Starting a new reverse engineering task with an artifact (binary, APK, firmware, etc.)
- You have a file but don't know which specialized RE skill applies
- You need a structured methodology before diving into tools
- The task involves multiple RE domains and you need coordination
Don't use for:
- Unauthorized reverse engineering (only authorized targets, bug bounty programs, defensive validation)
- Pure source code review tasks
- When you already know the exact skill needed
Workflow
- Classify Artifact — Identify file type via extension, magic bytes, and keywords from user prompt
- Route — Look up in routing table above; if ambiguous or no match, route to
reverse-engineer-anything-with-rea
- Execute — Invoke the primary skill with artifact context; if primary fails or is unavailable, use fallback
- Iterate — If deeper analysis needed, the primary skill can invoke sub-skills per its own workflow
Skill Map (48 Skills)
Native Binary Analysis (ELF / PE / Mach-O)
binary-breaker — Binary exploitation & RE for zero-days
reverse-engineering-malware-with-ghidra — Ghidra-based malware RE
analyzing-linux-elf-malware — Linux ELF malware (botnets, cryptominers, rootkits)
analyzing-golang-malware-with-ghidra — Go malware with Ghidra
go-rust-reverse — Go/Rust binary RE (pclntab, symbol recovery)
reverse-engineering-rust-malware — Rust malware RE
analyzing-packed-malware-with-upx-unpacker — UPX/packed binary unpacking
performing-static-malware-analysis-with-pe-studio — PE static analysis
performing-binary-exploitation-analysis — Binary exploitation analysis
.NET / Managed Code
reverse-engineering-dotnet-malware-with-dnspy — .NET malware with dnSpy
Android / Mobile
reverse-engineering-android-malware-with-jadx — Android malware with JADX
analyzing-android-malware-with-apktool — Android malware with Apktool
performing-android-app-static-analysis-with-mobsf — MobSF static analysis
performing-dynamic-analysis-of-android-app — Frida/Objection dynamic analysis
testing-android-intents-for-vulnerabilities — Android IPC intent testing
detecting-mobile-malware-behavior — Mobile malware behavior detection
iOS / macOS
reverse-engineering-ios-app-with-frida — iOS app with Frida
analyzing-ios-app-security-with-objection — iOS with Objection
JavaScript / Web / WASM
js-reverse — Frontend JavaScript RE (signing, anti-bot)
dsl-vm-reverse — Custom DSL/VM reverse engineering
browser-extension-reverse — Browser extension RE
deobfuscating-javascript-malware — JS malware deobfuscation
deobfuscating-powershell-obfuscated-malware — PowerShell deobfuscation
PDF / Document Malware
analyzing-malicious-pdf-with-peepdf — PDF malware with peepdf
Exploitation & Kernel Analysis
analyzing-heap-spray-exploitation — Heap spray exploitation
analyzing-linux-kernel-rootkits — Linux kernel rootkit analysis
performing-fuzzing-with-aflplusplus — AFL++ fuzzing for zero-days
Malware Enrichment & Supply Chain
analyzing-malware-persistence-with-autoruns — Autoruns persistence analysis
analyzing-supply-chain-malware-artifacts — Supply chain malware artifacts
building-automated-malware-submission-pipeline — Automated submission pipeline
Host Artifact Analysis
analyzing-windows-prefetch-with-python — Windows Prefetch execution artifacts
IoT / Thick Client
performing-iot-security-assessment — IoT device RE and security assessment
performing-thick-client-application-penetration-test — Thick client RE
Firmware / Embedded / OT
performing-firmware-extraction-with-binwalk — Firmware extraction with Binwalk
performing-firmware-malware-analysis — Firmware malware analysis
performing-plc-firmware-security-analysis — PLC/OT firmware security
Malware Behavior & Configuration
performing-automated-malware-analysis-with-cape — CAPE sandbox analysis
analyzing-cobalt-strike-beacon-configuration — Cobalt Strike beacon config
extracting-config-from-agent-tesla-rat — Agent Tesla RAT config
reverse-engineering-ransomware-encryption-routine — Ransomware encryption RE
analyzing-ransomware-encryption-mechanisms — Ransomware encryption analysis
analyzing-malware-sandbox-evasion-techniques — Sandbox evasion analysis
analyzing-network-covert-channels-in-malware — Covert channel analysis
performing-malware-ioc-extraction — IOC extraction
performing-malware-triage-with-yara — YARA-based triage
Network & Forensics
analyzing-network-traffic-of-malware — Network traffic analysis
performing-memory-forensics-with-volatility3-plugins — Memory forensics
Unified Artifact Evidence (REA Integration)
reverse-engineer-anything-with-rea — REA MCP/CLI artifact evidence workflow
Core Skill References
All skills above exist in cybersecurity/ category and are registered in SKILLS.json.
Deliberately Out of Scope
These RE-adjacent skills are reachable through cybersecurity-router but are response/defense workflows, not reverse engineering. This router does not claim them:
conducting-malware-incident-response — incident response lifecycle, not artifact analysis
implementing-ransomware-kill-switch-detection — defensive detection control
investigating-ransomware-attack-artifacts — forensic investigation, not RE
Operating Model
Phase 1: Artifact Identification (Always First)
Collect before analysis:
- File extension and magic bytes (
file, xxd, binwalk)
- Architecture (
file, readelf -h, objdump -f)
- Platform hints from user prompt (keywords, context)
- Packing/obfuscation detection (entropy,
upx -l, peid)
Phase 2: Route by Artifact Class
Use the routing table above. Exact match wins; keyword match is secondary.
Phase 3: Execute Specialized Skill
Invoke the primary skill. If primary fails (tool unavailable, unsupported format), use fallback.
Phase 4: Deepen or Iterate
The specialized skill handles its own deepening. If new artifacts discovered, re-enter Phase 1.
High-Value Expert Intuitions
- Magic bytes never lie — extension can be wrong; always verify with
file and hex dump
- Packing is the norm, not exception — assume packed; unpacking first saves hours
- Platform dictates toolchain — Android ≠ iOS ≠ Linux ≠ Windows ≠ firmware
- Fallback is a feature —
reverse-engineer-anything-with-rea prevents dead ends for unknown artifacts
- REA for evidence preservation — when behavior must be cited, use
reverse-engineer-anything-with-rea for evidence IDs and snapshots
Suggested Prompts
- "Route this reverse engineering task: I have a suspicious ELF binary"
- "I need to analyze an APK for malware — which skill?"
- "Route this: firmware image from IoT device, need extraction and analysis"
- "Classify this binary and tell me the right RE skill"
Verification Checklist
References
- Cybersecurity parent router:
cybersecurity-router (routes to this skill for Binary/ELF/PE cases)
- REA integration:
reverse-engineer-anything-with-rea (artifact evidence backend)
- All skills: 39 skills in
cybersecurity/ category with reverse-engineering tag
- Schema:
depends_on links children → this router; triggers define activation phrases
1---2name: reverse-engineering-router3description: Use when starting any reverse engineering task — master router that classifies the target artifact and routes to the correct specialized RE skill (native binaries, Android, iOS, JavaScript, firmware, .NET, malware behavior, forensics).4domain: cybersecurity5category: cybersecurity6version: 1.0.07author: oyi778license: Apache-2.09subdomain: reverse-engineering10tags:11 - reverse-engineering12 - binary-analysis13 - malware-analysis14 - firmware-analysis15 - mobile-security16 - router17depends_on:18 - cybersecurity-router19triggers:20 - "reverse engineer"21 - "analyze binary"22 - "decompile"23 - "disassemble"24 - "reverse engineering"25 - "unpack firmware"26 - "analyze apk"27 - "analyze malware"28 - "firmware extraction"29 - "binary analysis"30metadata:31 source: https://skillmd.com/skills/oyi77/reverse-engineering-router32---3334# Reverse Engineering Router: Master Entry for RE Operations3536Determines the artifact type, selects the correct specialized reverse engineering skill, and enforces methodology before tooling. All 48 RE skills in the catalog are reachable through this router.3738## Overview3940reverse-engineering-router is the master entry for reverse engineering work: it classifies the target artifact (file format, architecture, platform), routes to the correct specialized skill, and ensures structured methodology over random tool usage. It maps 48 reverse-engineering skills into a deterministic decision tree.4142## When NOT to Use4344- Authorized testing already scoped to a single deep technique — load the specialized skill directly (e.g., known Android malware: load `reverse-engineering-android-malware-with-jadx`)45- Source code analysis — use static analysis tools instead (Semgrep, CodeQL)46- No artifact available (requirements-only tasks)4748## Verification4950- Feed the router a scenario for each artifact class (native binary, Android APK, iOS app, JavaScript bundle, firmware image, .NET assembly, packed binary, malware sample) and confirm it routes to the correct specialist skill each time.51- Verify fallback to `reverse-engineer-anything-with-rea` for unknown/ambiguous artifacts5253## Anti-Rationalization Table5455| Excuse | Reality | Rule |56|---|---|---|57| "I'll just open it in Ghidra" | Without identifying the format first, you'll waste hours on wrong architecture or wrong tool | Route by artifact signature first |58| "The decompiler will figure it out" | A PE binary opened as ELF produces garbage; wrong platform = wrong results | Verify file type before tool selection |59| "I'll try all tools" | Trial-and-error is not a methodology; it produces incomplete coverage | Use the routing table below |6061---6263## Routing Decision Table6465The routing table is a lookup, not judgment-by-hand. Model it as data so the same decision is repeatable.6667```python68ROUTING_TABLE = [69 # (matchers, primary_skill, fallback_skill)70 ({"ext": [".apk", ".dex", ".aab", ".smali"], "magic": ["PK\\x03\\x04"]},71 "reverse-engineering-android-malware-with-jadx",72 "analyzing-android-malware-with-apktool"),73 ({"ext": [".ipa", ".app"], "magic": ["Mach-O"]},74 "reverse-engineering-ios-app-with-frida",75 "analyzing-ios-app-security-with-objection"),76 ({"ext": [".exe", ".dll", ".sys"], "magic": ["MZ"]},77 "binary-breaker",78 "reverse-engineering-malware-with-ghidra"),79 ({"ext": [".so", ".bin", ".elf"], "magic": ["\\x7fELF"]},80 "analyzing-linux-elf-malware",81 "reverse-engineering-malware-with-ghidra"),82 ({"ext": [".js", ".mjs", ".ts", ".wasm"], "magic": []},83 "js-reverse",84 "dsl-vm-reverse"),85 ({"ext": [".bin", ".img", ".hex"], "magic": ["U-Boot", "squashfs", "cramfs", "jffs2"]},86 "performing-firmware-extraction-with-binwalk",87 "performing-firmware-malware-analysis"),88 ({"ext": [".exe", ".dll"], "magic": ["MZ"], "dotnet": True},89 "reverse-engineering-dotnet-malware-with-dnspy",90 "reverse-engineering-malware-with-ghidra"),91 ({"keywords": ["packed", "upx", "obfuscated", "stripped"]},92 "analyzing-packed-malware-with-upx-unpacker",93 "reverse-engineering-malware-with-ghidra"),94 ({"keywords": ["cobalt strike", "beacon", "c2"]},95 "analyzing-cobalt-strike-beacon-configuration",96 "reverse-engineering-malware-with-ghidra"),97 ({"keywords": ["agent tesla", "rat config"]},98 "extracting-config-from-agent-tesla-rat",99 "reverse-engineering-malware-with-ghidra"),100 ({"keywords": ["ransomware", "encryption routine"]},101 "reverse-engineering-ransomware-encryption-routine",102 "analyzing-ransomware-encryption-mechanisms"),103 ({"keywords": ["sandbox evasion", "anti-vm", "anti-debug"]},104 "analyzing-malware-sandbox-evasion-techniques",105 "performing-automated-malware-analysis-with-cape"),106 ({"keywords": ["yara", "ioc extraction", "malware triage"]},107 "performing-malware-triage-with-yara",108 "performing-malware-ioc-extraction"),109 ({"keywords": ["network traffic", "pcap", "covert channel"]},110 "analyzing-network-traffic-of-malware",111 "analyzing-network-covert-channels-in-malware"),112 ({"keywords": ["memory dump", "volatility", "forensics"]},113 "performing-memory-forensics-with-volatility3-plugins",114 "analyzing-disk-image-with-autopsy"),115 ({"keywords": ["go binary", "golang", "pclntab"]},116 "go-rust-reverse",117 "analyzing-golang-malware-with-ghidra"),118 ({"keywords": ["rust binary", "panic strings"]},119 "reverse-engineering-rust-malware",120 "go-rust-reverse"),121 ({"keywords": ["browser extension", "crx", "xpi"]},122 "browser-extension-reverse",123 "js-reverse"),124 ({"keywords": ["powershell", "obfuscated"]},125 "deobfuscating-powershell-obfuscated-malware",126 "deobfuscating-javascript-malware"),127 ({"keywords": ["plc", "s7comm", "ot", "ics"]},128 "performing-plc-firmware-security-analysis",129 "performing-firmware-malware-analysis"),130 ({"ext": [".pdf"], "keywords": ["peepdf", "malicious pdf", "stream"]},131 "analyzing-malicious-pdf-with-peepdf",132 "reverse-engineer-anything-with-rea"),133 ({"keywords": ["heap spray", "heap exploitation"]},134 "analyzing-heap-spray-exploitation",135 "performing-binary-exploitation-analysis"),136 ({"keywords": ["rootkit", "kernel module", "lkm", "vmlinux"]},137 "analyzing-linux-kernel-rootkits",138 "analyzing-linux-elf-malware"),139 ({"keywords": ["fuzzing", "afl", "harness", "crash triage"]},140 "performing-fuzzing-with-aflplusplus",141 "binary-breaker"),142 ({"keywords": ["persistence", "autoruns", "registry run"]},143 "analyzing-malware-persistence-with-autoruns",144 "performing-static-malware-analysis-with-pe-studio"),145 ({"keywords": ["supply chain", "malicious package", "typosquatting"]},146 "analyzing-supply-chain-malware-artifacts",147 "reverse-engineer-anything-with-rea"),148 ({"keywords": ["malware pipeline", "automated submission"]},149 "building-automated-malware-submission-pipeline",150 "performing-automated-malware-analysis-with-cape"),151 ({"keywords": ["virustotal", "hash enrichment", "reputation"]},152 "performing-malware-hash-enrichment-with-virustotal",153 "performing-malware-ioc-extraction"),154 ({"keywords": ["iot", "embedded device", "uart", "jtag"]},155 "performing-iot-security-assessment",156 "performing-firmware-extraction-with-binwalk"),157 ({"keywords": ["thick client", "fat client", "wpf", "electron"]},158 "performing-thick-client-application-penetration-test",159 "reverse-engineering-dotnet-malware-with-dnspy"),160 ({"keywords": ["prefetch", "windows execution artifact", "shimcache"]},161 "analyzing-windows-prefetch-with-python",162 "analyzing-malware-persistence-with-autoruns"),163]164165def route(artifact_info: dict) -> tuple[str, str]:166 """Return (primary_skill, fallback_skill) or (None, 'reverse-engineer-anything-with-rea')"""167 for matchers, primary, fallback in ROUTING_TABLE:168 if all(artifact_info.get(k) in v for k, v in matchers.items() if k != "keywords"):169 if "keywords" not in matchers or any(kw in artifact_info.get("text", "").lower() for kw in matchers["keywords"]):170 return primary, fallback171 return None, "reverse-engineer-anything-with-rea"172```173174---175176## When to Use177178**Use when:**179180- Starting a new reverse engineering task with an artifact (binary, APK, firmware, etc.)181- You have a file but don't know which specialized RE skill applies182- You need a structured methodology before diving into tools183- The task involves multiple RE domains and you need coordination184185**Don't use for:**186187- Unauthorized reverse engineering (only authorized targets, bug bounty programs, defensive validation)188- Pure source code review tasks189- When you already know the exact skill needed190191---192193## Workflow1941951. **Classify Artifact** — Identify file type via extension, magic bytes, and keywords from user prompt1962. **Route** — Look up in routing table above; if ambiguous or no match, route to `reverse-engineer-anything-with-rea`1973. **Execute** — Invoke the primary skill with artifact context; if primary fails or is unavailable, use fallback1984. **Iterate** — If deeper analysis needed, the primary skill can invoke sub-skills per its own workflow199200---201202## Skill Map (48 Skills)203204### Native Binary Analysis (ELF / PE / Mach-O)205- `binary-breaker` — Binary exploitation & RE for zero-days206- `reverse-engineering-malware-with-ghidra` — Ghidra-based malware RE207- `analyzing-linux-elf-malware` — Linux ELF malware (botnets, cryptominers, rootkits)208- `analyzing-golang-malware-with-ghidra` — Go malware with Ghidra209- `go-rust-reverse` — Go/Rust binary RE (pclntab, symbol recovery)210- `reverse-engineering-rust-malware` — Rust malware RE211- `analyzing-packed-malware-with-upx-unpacker` — UPX/packed binary unpacking212- `performing-static-malware-analysis-with-pe-studio` — PE static analysis213- `performing-binary-exploitation-analysis` — Binary exploitation analysis214215### .NET / Managed Code216- `reverse-engineering-dotnet-malware-with-dnspy` — .NET malware with dnSpy217218### Android / Mobile219- `reverse-engineering-android-malware-with-jadx` — Android malware with JADX220- `analyzing-android-malware-with-apktool` — Android malware with Apktool221- `performing-android-app-static-analysis-with-mobsf` — MobSF static analysis222- `performing-dynamic-analysis-of-android-app` — Frida/Objection dynamic analysis223- `testing-android-intents-for-vulnerabilities` — Android IPC intent testing224- `detecting-mobile-malware-behavior` — Mobile malware behavior detection225226### iOS / macOS227- `reverse-engineering-ios-app-with-frida` — iOS app with Frida228- `analyzing-ios-app-security-with-objection` — iOS with Objection229230### JavaScript / Web / WASM231- `js-reverse` — Frontend JavaScript RE (signing, anti-bot)232- `dsl-vm-reverse` — Custom DSL/VM reverse engineering233- `browser-extension-reverse` — Browser extension RE234- `deobfuscating-javascript-malware` — JS malware deobfuscation235- `deobfuscating-powershell-obfuscated-malware` — PowerShell deobfuscation236237### PDF / Document Malware238- `analyzing-malicious-pdf-with-peepdf` — PDF malware with peepdf239240### Exploitation & Kernel Analysis241- `analyzing-heap-spray-exploitation` — Heap spray exploitation242- `analyzing-linux-kernel-rootkits` — Linux kernel rootkit analysis243- `performing-fuzzing-with-aflplusplus` — AFL++ fuzzing for zero-days244245### Malware Enrichment & Supply Chain246- `analyzing-malware-persistence-with-autoruns` — Autoruns persistence analysis247- `analyzing-supply-chain-malware-artifacts` — Supply chain malware artifacts248- `building-automated-malware-submission-pipeline` — Automated submission pipeline249250### Host Artifact Analysis251- `analyzing-windows-prefetch-with-python` — Windows Prefetch execution artifacts252253### IoT / Thick Client254- `performing-iot-security-assessment` — IoT device RE and security assessment255- `performing-thick-client-application-penetration-test` — Thick client RE256257### Firmware / Embedded / OT258- `performing-firmware-extraction-with-binwalk` — Firmware extraction with Binwalk259- `performing-firmware-malware-analysis` — Firmware malware analysis260- `performing-plc-firmware-security-analysis` — PLC/OT firmware security261262### Malware Behavior & Configuration263- `performing-automated-malware-analysis-with-cape` — CAPE sandbox analysis264- `analyzing-cobalt-strike-beacon-configuration` — Cobalt Strike beacon config265- `extracting-config-from-agent-tesla-rat` — Agent Tesla RAT config266- `reverse-engineering-ransomware-encryption-routine` — Ransomware encryption RE267- `analyzing-ransomware-encryption-mechanisms` — Ransomware encryption analysis268- `analyzing-malware-sandbox-evasion-techniques` — Sandbox evasion analysis269- `analyzing-network-covert-channels-in-malware` — Covert channel analysis270- `performing-malware-ioc-extraction` — IOC extraction271- `performing-malware-triage-with-yara` — YARA-based triage272273### Network & Forensics274- `analyzing-network-traffic-of-malware` — Network traffic analysis275- `performing-memory-forensics-with-volatility3-plugins` — Memory forensics276277### Unified Artifact Evidence (REA Integration)278- `reverse-engineer-anything-with-rea` — REA MCP/CLI artifact evidence workflow279280---281282## Core Skill References283284All skills above exist in `cybersecurity/` category and are registered in `SKILLS.json`.285286### Deliberately Out of Scope287288These RE-adjacent skills are reachable through `cybersecurity-router` but are **response/defense** workflows, not reverse engineering. This router does not claim them:289290- `conducting-malware-incident-response` — incident response lifecycle, not artifact analysis291- `implementing-ransomware-kill-switch-detection` — defensive detection control292- `investigating-ransomware-attack-artifacts` — forensic investigation, not RE293294---295296## Operating Model297298### Phase 1: Artifact Identification (Always First)299300Collect before analysis:301- File extension and magic bytes (`file`, `xxd`, `binwalk`)302- Architecture (`file`, `readelf -h`, `objdump -f`)303- Platform hints from user prompt (keywords, context)304- Packing/obfuscation detection (entropy, `upx -l`, `peid`)305306### Phase 2: Route by Artifact Class307308Use the routing table above. Exact match wins; keyword match is secondary.309310### Phase 3: Execute Specialized Skill311312Invoke the primary skill. If primary fails (tool unavailable, unsupported format), use fallback.313314### Phase 4: Deepen or Iterate315316The specialized skill handles its own deepening. If new artifacts discovered, re-enter Phase 1.317318---319320## High-Value Expert Intuitions3213221. **Magic bytes never lie** — extension can be wrong; always verify with `file` and hex dump3232. **Packing is the norm, not exception** — assume packed; unpacking first saves hours3243. **Platform dictates toolchain** — Android ≠ iOS ≠ Linux ≠ Windows ≠ firmware3254. **Fallback is a feature** — `reverse-engineer-anything-with-rea` prevents dead ends for unknown artifacts3265. **REA for evidence preservation** — when behavior must be cited, use `reverse-engineer-anything-with-rea` for evidence IDs and snapshots327328---329330## Suggested Prompts331332- "Route this reverse engineering task: I have a suspicious ELF binary"333- "I need to analyze an APK for malware — which skill?"334- "Route this: firmware image from IoT device, need extraction and analysis"335- "Classify this binary and tell me the right RE skill"336337---338339## Verification Checklist340341- [ ] Artifact type identified via magic bytes before tool selection342- [ ] Routing table lookup returns a primary skill for the artifact343- [ ] Fallback skill specified for every primary344- [ ] Primary skill exists in SKILLS.json and passes lint345- [ ] All 39 mapped skills are current catalog entries346347---348349## References350351- **Cybersecurity parent router**: `cybersecurity-router` (routes to this skill for Binary/ELF/PE cases)352- **REA integration**: `reverse-engineer-anything-with-rea` (artifact evidence backend)353- **All skills**: 39 skills in `cybersecurity/` category with `reverse-engineering` tag354- **Schema**: `depends_on` links children → this router; `triggers` define activation phrases