Analyze binaries via deterministic static reverse engineering across native, managed, JavaScript, and WebAssembly targets.
npx skills add https://github.com/Xerrion/opencode --skill rev-static
Please help me install this Agent Skill. Skill: rev-static Source: https://github.com/Xerrion/opencode/tree/main/skills/rev-static Command: npx skills add https://github.com/Xerrion/opencode --skill rev-static
Static reverse engineering is essential to understand binary behavior without executing code, enabling analysts to extract strings, imports, architecture details, and structure for security reviews and vulnerability assessment.
Run a static analysis workflow on a sample to generate reproducible disassembly and decompiled outputs.
High-intent search queries and answers about installing and using this skill.
Deterministic static reverse engineering applies consistent disassembly and decompilation across native, managed, JavaScript, and WebAssembly targets to generate reproducible outputs. It enforces a structured project layout to standardize analysis results for auditing and reporting.
Yes, automated malware decompilation and disassembly use Ghidra headless alongside rizin and radare2. This approach processes binaries deterministically, creating reproducible disassembly and decompiled files under structured project directories for threat profiling.
Binary analysis detects packers and identifies language fingerprints by applying compiler fingerprinting and capability-ID detection across native, managed, JavaScript, and WebAssembly targets. This process extracts strings and imports to rapidly profile potential threats.
Static binary analysis works with WebAssembly and managed code targets by applying deterministic disassembly and decompilation techniques. It extracts architecture details, strings, and imports across these formats to support security reviews without executing code.
To extract strings and cross-references reproducibly for a malware sample, apply deterministic static analysis to generate structured outputs in designated directories. This records language fingerprints, detected packers, and imports for consistent audit and reporting.
Static reverse engineering should not be used when assessing heavily obfuscated packed binaries requiring runtime unpacking, or when code behavior depends entirely on dynamic runtime state that static disassembly and decompilation cannot execute or observe.
Liberty91LTDIdentify malware samples and extract static and dynamic indicators from reports.
miunasuExtract disassembly, decompiled code, imports, strings, and cross-references from IDA Pro via IDAPython.
hypnguyen1209Reverse-engineer binaries and firmware through static and dynamic analysis.
philo-grovesAutomate binary reverse engineering tasks with Ghidra headless analysis.
