Reverse Engineering Malware With Ghidra

Reverse Engineering Malware With Ghidra

Overview

Cybersecurity skill for reverse engineering malware with ghidra. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "reverse engineering malware with ghidra"

• "reverseing engineering malware with ghidra"

• "Reverse engineers malware binaries using NSA''s Ghidra disassembler and decompil"

• Static and dynamic analysis have identified suspicious functionality that requires deeper code-level understanding

• You need to reverse engineer C2 communication protocols, encryption algorithms, or custom obfuscation

• Understanding the exact exploit mechanism or vulnerability targeted by a malware sample

• Extracting hardcoded configuration data (C2 addresses, encryption keys, campaign IDs) embedded in compiled code

• Developing precise YARA rules or detection signatures based on unique code patterns

Do not use for initial triage of unknown samples; perform static analysis with PEStudio and behavioral analysis with Cuckoo first.

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Ghidra 11.x installed (download from https://ghidra-sre.org/) with JDK 17+
• Analysis VM isolated from production network (Windows or Linux host)
• Familiarity with x86/x64 assembly language and Windows API conventions
• PDB symbol files for Windows system DLLs to improve decompilation accuracy
• Ghidra scripts repository (ghidra_scripts) for automated analysis tasks
• Secondary reference: IDA Free or Binary Ninja for cross-validation of analysis results

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}

1. Define Objectives — Clarify the goals and scope for engineering malware.
2. Gather Resources — Collect tools, data, and access needed for engineering malware.
3. Execute Process — Carry out engineering malware operations methodically.
4. Verify Quality — Check results against acceptance criteria.
5. Document Outcomes — Record findings, decisions, and next steps.

Tools

• ghidra — Primary tool for this skill
• Analysis Platform — Data processing and visualization
• Collaboration Tools — Team coordination and knowledge sharing

Process

1. Reconnaissance — Gather target information, identify attack surface, enumerate services
2. Analysis/Exploitation — Execute the technique, analyze results, document findings
3. Reporting — Document IOCs, write findings, provide remediation recommendations

Verification

• All engineering malware procedures executed completely and documented
• Findings validated against multiple data sources
• False positives identified and filtered
• Results documented with evidence and timestamps
• Recommendations provided with risk-based prioritization

Anti-Rationalization Table