HexCore Binary Analysis
Provides binary analysis, disassembly, and emulation for security research and reverse engineering.
Install
mkdir -p .claude/skills/hexcore-binary-analysis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14853" && unzip -o skill.zip -d .claude/skills/hexcore-binary-analysis && rm skill.zipInstalls to .claude/skills/hexcore-binary-analysis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Skill para analise de binarios com ferramentas HexCore integradas ao editorKey capabilities
- →Disassemble binary files for multiple architectures
- →Emulate CPU execution flow for various architectures
- →Lift binary code to LLVM IR for x86, x64, and ARM64
- →Decompile LLVM IR to pseudo-C for x86 and x64
- →Detect and filter junk instructions in binaries
- →Perform static PRNG pattern detection
How it works
This skill integrates multiple native engines like Capstone for disassembly and Unicorn for CPU emulation within a VS Code fork to perform binary analysis.
Inputs & outputs
When to use HexCore Binary Analysis
- →Disassemble binary files
- →Emulate CPU execution flow
- →Lift binary code to LLVM IR
- →Identify junk code or VM detection
About this skill
HexCore Binary Analysis Skill - v3.8.3 RC
Scope
HexCore is a VS Code-based reverse-engineering environment. Use it only for binaries the user owns or is authorized to analyze, including CTF/HTB challenges, controlled game research, malware triage, and bug-bounty artifacts within scope.
The automation source of truth is extensions/hexcore-disassembler/src/automationPipelineRunner.ts. Validate jobs before treating examples in prose as executable contracts.
Release train: HexCore
3.8.3RC, "Honest Analysis at Scale".Important:
hexcore-helixstill reports package version0.9.2in the IDE tree while the Helix v2 sandbox is being qualified as the future0.9.3. Do not describe the sandbox as a separately shipped product.
Engine Routing
| Input / goal | Primary route | Notes |
|---|---|---|
| Native PE/ELF machine code | Remill -> Helix | Use hexcore.helix.decompile or explicit lift + decompileIR. |
| Classic CLR PE or .NET single-file apphost | Revenant | Use hexcore.revenant.decompile for C# or decompileIL for IL. Helix intentionally returns a managed-input honesty marker with confidence 0. |
| LLVM IR optimization experiment | Souper | Use explicitly on .ll, or Helix souper: "auto". Do not force it on every function. |
| Semantic pattern scan | HQL | Scans Helix HAST, not regex over rendered pseudo-C. |
ELF .ko/vmlinux types | BTF/DWARF extraction | Run ELF/deep analysis first, then hexcore.extractStructInfo. |
| Broad emulation | Debugger/Unicorn | Stable general route; use the full one-shot command unless session state is required. |
| Isolated native instrumentation | Elixir/Azoth | Worker-isolated alternative; select with hexcore.emulator. |
| Legacy Rellic jobs | Rellic, compatibility only | Disabled legacy surface. Do not use in new jobs or claim a scheduled removal version. |
Current native package versions
capstone 1.3.5, unicorn 1.3.0, remill 0.5.1, llvm-mc 1.0.1, better-sqlite3 2.0.2, souper 0.2.0, elixir 1.0.0, common 1.1.1.
Current integrated extensions relevant to automation: hexcore-disassembler 1.4.27, hexcore-debugger 2.1.9, hexcore-yara 2.1.3, hexcore-revenant 0.4.0, and IDE hexcore-helix 0.9.2 metadata.
Job Rules
- Put the canonical job at
.hexcore_job.json, or use a descriptive*.hexcore_job.jsonname. - Keep
outDirinside the workspace or the job-file directory. External output is rejected unless the user deliberately enableshexcore.pipeline.allowExternalOutDir. - Use
hexcore.pipeline.validateJoborvalidateWorkspacebefore expensive runs. - Prefer a single job plus
$step[N].outputwhen one step consumes another step's artifact. $step[prev]is valid except in step0; forward references are invalid. Conditional jumps that may skip a referenced producer are reported by validation.- Top-level
continueOnErroris inherited by steps unless a step overrides it. - Set realistic timeouts. Static analysis and full emulation of large binaries can legitimately take minutes.
- Inspect both
hexcore-pipeline.logandhexcore-pipeline.status.json. The status records attempts, output bytes, totals, slowest step, and queue snapshot. - A command disabled by
hexcore.emulatorisskipped, not a tool failure. - Do not invoke
hexcore.pipeline.runJobfrom a pipeline step; recursive pipeline execution is blocked. - Preflight is mandatory and prevents command dispatch on validation errors. Do not bypass it to obtain a partial artifact.
- Semantic child failures fail by default. Use
allowPartial: trueonly when incomplete coverage is intentional, and preserve the terminalpartialstatus. - Verify each artifact's
.provenance.jsonsidecar before cross-run comparison.
Watcher and queue behavior
- On startup, root-level canonical/named jobs are auto-discovered.
- The recursive watcher reacts to later create/change events under the workspace.
- Watch events are debounced and content-deduplicated; outputs are protected from re-trigger loops.
- Queue slots are configured by
hexcore.pipeline.queue.poolSize(default2, range1..16). Stateful jobs serialize across the shared Extension Host; only audited stateless tools use parallel slots. - Use
sessionIdfor sticky routing when multiple queued jobs share akeepAliveemulation session.
Pipeline-Safe Commands
This list mirrors the v3.8.3 RC capability registry. Aliases are listed separately.
Static, format, and reporting
hexcore.filetype.detecthexcore.hashcalc.calculatehexcore.entropy.analyzehexcore.strings.extracthexcore.strings.extractAdvancedhexcore.peanalyzer.analyzehexcore.disasm.analyzePEHeadlesshexcore.elfanalyzer.analyzehexcore.disasm.analyzeELFHeadlesshexcore.base64.decodeHeadlesshexcore.yara.scanhexcore.yara.updateRuleshexcore.ioc.extracthexcore.hexview.dumpHeadlesshexcore.hexview.searchHeadlesshexcore.minidump.parsehexcore.minidump.threadshexcore.minidump.moduleshexcore.minidump.memoryhexcore.pipeline.composeReport
Disassembly, decompilation, and semantic analysis
hexcore.disasm.analyzeAllhexcore.disasm.detectPacker- detection only; no unpacking or external UPX dependency.hexcore.disasm.buildFormulahexcore.disasm.checkConstantshexcore.disasm.searchStringHeadlesshexcore.disasm.exportASMHeadlesshexcore.disasm.disassembleAtHeadlesshexcore.disasm.rttiScanHeadlesshexcore.disasm.searchBytesHeadlesshexcore.disasm.extractStringshexcore.disasm.liftToIRhexcore.helix.decompilehexcore.helix.decompileIRhexcore.revenant.decompilehexcore.revenant.decompileILhexcore.hql.scanHeadlesshexcore.souper.optimizehexcore.extractStructInfohexcore.audit.refcountScanhexcore.rellic.decompileandhexcore.rellic.decompileIR- legacy compatibility only.
Persistent analysis session
hexcore.disasm.getSessionDbPathhexcore.disasm.renameFunctionhexcore.disasm.renameVariablehexcore.disasm.retypeFunctionhexcore.disasm.retypeVariablehexcore.disasm.setBookmark
Annotations are stored in .hexcore_session.db, keyed to the binary, and may be applied to later Helix/HQL work.
Debugger / Unicorn
hexcore.debug.emulateFullHeadlesshexcore.debug.emulateHeadlesshexcore.debug.continueHeadlesshexcore.debug.stepHeadlesshexcore.debug.readMemoryHeadlesshexcore.debug.writeMemoryHeadlesshexcore.debug.searchMemoryHeadlesshexcore.debug.getRegistersHeadlesshexcore.debug.setRegisterHeadlesshexcore.debug.setStdinHeadlesshexcore.debug.setBreakpointHeadlesshexcore.debug.getStateHeadlesshexcore.debug.snapshotHeadlesshexcore.debug.restoreSnapshotHeadlesshexcore.debug.exportTraceHeadlesshexcore.debug.disposeHeadless
Use emulateFullHeadless for a one-shot load/run/collect/dispose workflow. Use granular commands only with keepAlive: true, explicit cleanup, and session-aware queue routing.
Elixir / Azoth
hexcore.elixir.emulateHeadlesshexcore.elixir.stalkerDrcovHeadlesshexcore.elixir.snapshotRoundTripHeadlesshexcore.elixir.smokeTestHeadless
Elixir emulation runs in a worker process to isolate native crashes. Set hexcore.emulator to azoth or both; otherwise these steps are skipped.
Pipeline administration
hexcore.pipeline.listCapabilitieshexcore.pipeline.validateJobhexcore.pipeline.validateWorkspacehexcore.pipeline.createPresetJobhexcore.pipeline.saveJobAsProfilehexcore.pipeline.doctorhexcore.pipeline.queueJobhexcore.pipeline.cancelJobhexcore.pipeline.jobStatus
Oracle preview
hexcore.oracle.inspectConfig, hexcore.oracle.listSessions, and hexcore.oracle.demoHeadless are v3.9.0-preview.oracle, gated by hexcore.oracle.enabled. Do not depend on them for a 3.8.3 release-validation job.
Interactive-only registry entries
These commands are declared but blocked in pipeline mode because they depend on pickers, active editors, notifications, or report UI:
hexcore.disasm.openFilehexcore.disasm.analyzeFilehexcore.debug.emulatehexcore.debug.emulateWithArchhexcore.elfanalyzer.analyzeActivehexcore.hql.scanFunctionhexcore.yara.quickScanhexcore.yara.scanWorkspacehexcore.yara.loadDefenderhexcore.yara.loadCategoryhexcore.yara.createRulehexcore.yara.threatReporthexcore.pipeline.runJobwhen attempted recursively from a step
Important Aliases
| Alias | Resolves to |
|---|---|
hexcore.decompile | hexcore.helix.decompile |
hexcore.decompile.ir | hexcore.helix.decompileIR |
hexcore.liftir | hexcore.disasm.liftToIR |
hexcore.souper, hexcore.optimize, hexcore.superoptimize | hexcore.souper.optimize |
hexcore.dotnet.decompile, hexcore.decompile.dotnet, hexcore.revenant.decompileCSharp | hexcore.revenant.decompile |
hexcore.dotnet.decompileIL, hexcore.decompile.il | hexcore.revenant.decompileIL |
hexcore.hql.scan, hexcore.hql.scanFunctions | hexcore.hql.scanHeadless |
hexcore.struct, hexcore.structInfo | hexcore.extractStructInfo |
hexcore.debug.run, hexcore.debug.emulate.full | hexcore.debug.emulateFullHeadless |
hexcore.disasm.rttiScan, hexcore.disasm.scanRtti | hexcore.disasm.rttiScanHeadless |
hexcore.disasm.searchBytes, hexcore.disasm.aobScan | hexcore.disasm.searchBytesHeadless |
Prefer canonical command names in durable jobs. Aliases are useful interactively but hide less context in a report.
Recommended Workflows
Hard / Insane reverse challenge
- File type, hashes, format-specific deep analysis, entropy, and packer detection.
analyzeAll, strings, AOB search, assembly export, and candidate-function identification.- Decompile only selected functions; retain their
.ll, pseudo-C, address, and
Content truncated.
Limitations
- →LLVM IR lifting is supported only for x86, x64, and ARM64 architectures.
- →Symbolic expression extraction is supported only for x86/x64 architectures.
- →The `hexcore-rellic` decompiler is deprecated and will be removed in v3.8.0.
How it compares
This skill provides a specialized environment with integrated tools for reverse engineering, offering advanced analysis features like junk filtering and VM detection beyond standard disassemblers.
Compared to similar skills
HexCore Binary Analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| HexCore Binary Analysis (this skill) | 0 | 4mo | No flags | Advanced |
| reverse-engineering-tools | 73 | 4mo | No flags | Advanced |
| ghidra | 16 | 7mo | Review | Advanced |
| firmware-analyst | 9 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
reverse-engineering-tools
gmh5225
Guide for reverse engineering tools and techniques used in game security research. Use this skill when working with debuggers, disassemblers, memory analysis tools, binary analysis, or decompilers for game security research.
ghidra
mitsuhiko
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.
firmware-analyst
sickn33
Expert firmware analyst specializing in embedded systems, IoT security, and hardware reverse engineering. Masters firmware extraction, analysis, and vulnerability research for routers, IoT devices, automotive systems, and industrial controllers. Use PROACTIVELY for firmware security audits, IoT penetration testing, or embedded systems research.
memory-forensics
wshobson
Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.
binary-analysis-patterns
wshobson
Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
security-scanning-tools
davila7
This skill should be used when the user asks to "perform vulnerability scanning", "scan networks for open ports", "assess web application security", "scan wireless networks", "detect malware", "check cloud security", or "evaluate system compliance". It provides comprehensive guidance on security scanning tools and methodologies.