deep-analysis

Execute depth-first binary investigations with evidence-based conclusions in Ghidra.

797|69|Updated Aug 18, 2023
One-click install
npx skills add https://github.com/cyberkaida/reverse-engineering-assistant --skill deep-analysis-cyberkaida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-analysis
Source: https://github.com/cyberkaida/reverse-engineering-assistant/tree/main/ReVa/skills/deep-analysis
Command: npx skills add https://github.com/cyberkaida/reverse-engineering-assistant --skill deep-analysis-cyberkaida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables focused, depth-first reverse engineering investigations to answer specific questions about binaries while improving the Ghidra database for future analysis.

Core Features & Use Cases

  • Structured investigation loop: READ, UNDERSTAND, IMPROVE, VERIFY, and FOLLOW THREADS to produce incremental, evidence-based findings.
  • Evidence-driven conclusions: Every claim includes precise addresses, decompilation snippets, and cross-reference context.
  • Assistive instruction for focused analysis: Guides users to pursue unanswered threads with bookmarks and comments for traceability.
  • Use Case: When you want to drill into a suspicious function to determine if it performs cryptography or to identify data flows and key sources.

Quick Start

Start by identifying a target function, then run a short investigation loop: read decompilation, examine references, rename variables, and document evidence with bookmarks. For example: ask the model, "What does FUN_00401850 do?" and follow the investigation workflow to return a concise, evidence-backed answer.

Frequently Asked Questions about deep-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform evidence-based binary analysis to understand what a specific function does?

Evidence-based binary analysis uses a structured investigation loop of READ, UNDERSTAND, IMPROVE, VERIFY, and FOLLOW THREADS to examine decompilation snippets and cross-references. This produces precise, traceable conclusions about specific function behaviors.

What is the best way to trace data flow and identify cryptography in Ghidra decompilation?

Tracing data flow in Ghidra decompilation is achieved through a depth-first investigation that follows data threads iteratively. By reading decompilation, examining references, and renaming variables, you can identify key sources and cryptography with explicit evidence.

Can I use this approach for targeted reverse engineering after an initial binary triage?

Yes, this approach applies specifically to targeted binary areas after initial triage. It guides you to pursue unanswered threads by documenting evidence with bookmarks and comments, ensuring traceability for detailed function understanding.

How do I document reverse engineering findings with traceability in a Ghidra database?

You document reverse engineering findings by iteratively improving the Ghidra database with bookmarks and comments during the investigation loop. This process ensures every claim includes precise addresses, decompilation snippets, and cross-reference context for traceability.

Does focused reverse engineering work for answering specific questions about suspicious binary functions?

Focused reverse engineering works by executing a depth-first investigation to answer specific questions about suspicious binaries. It drills into targeted functions to determine behaviors like cryptography detection, returning concise, evidence-backed answers.

What are the limitations of depth-first binary analysis when investigating decompiled code?

Depth-first binary analysis focuses on specific targeted areas rather than broad binary coverage. It requires a preliminary triage to identify target functions first, and relies on iteratively refining findings within the decompilation to avoid missing unrelated execution threads.