Перейти к содержимому
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/reverse-eng-ghidraРеверс-инжиниринг и фаззинг

reverse-eng-ghidra

⁨Reverse engineer with Ghidra (GUI, headless, or ghidra-mcp) — decompile, cross-references, scripting — when there's no IDA license, for batch/CI decompilation, or as a free second opinion. Load for "decompile without IDA", bulk analysis of many samples, analyzeHeadless, Ghidra scripts (Jython/PyGhid⁩

v2026.10.14-ee0e0c53 установки+3 за 7 дней27 ЗвездыMITсинхронизировано 22 часа назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reverse-eng-ghidra

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
1Dak5Gfv7Z…+VlRH6Ag==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакет0190672f…4172eb69
0190672f9448…d9a54172eb691 файл · ⁦2.2 KB⁩
ПроверкаСредний3 замечания
  • injection.no_confirmationSKILL.md:37
  • injection.no_confirmationSKILL.md:60
  • Ссылки на внешние домены
Вся проверка
Источникgithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-ghidra@ee0e0c5

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.

When it applies

You need decompiler-grade analysis of an in-scope binary (scope.txt / client-owned / your own sample — tradecraft-scope-roe) and there's no IDA license, or you need to process many samples in batch or CI. Also the right call when a conclusion from reverse-eng-ida or reverse-eng-radare2 deserves an independent cross-check with a different decompiler.

Why it works

Ghidra's P-code lifter gives one decompiler across dozens of architectures (x86/ARM/MIPS/PPC and obscure firmware targets IDA may not load well), and headless mode turns the whole import → analyze → decompile pipeline into a scriptable batch step — so bulk triage costs the same as single-file analysis.

Method

  1. Project, import, analyze. New project → import the file → run auto-analysis with the default analyzers. Record the language/compiler spec Ghidra picked and the base address — a wrong language guess (e.g. wrong ARM variant) silently produces garbage decompilation.
  2. Anchor on strings and imports. Search → For Strings, then right-click → References to find the code that uses an interesting string; double-click a function to decompile it. Same input → sink discipline as reverse-eng-binary-triage: record the import table before drawing conclusions.
  3. Read and annotate. Decompile window for logic; L to rename, ; for a comment, plate comments for function summaries. Rename/retype as you go — it compounds.
  4. Automate with scripts. Window → Script Manager for Jython (Python 2.7) scripts; for real Python 3 use PyGhidra, which bridges to CPython.
  5. Batch with headless when processing many files or running in CI:
    text
    analyzeHeadless /path/to/project Proj -import sample.bin -postScript ExportDecomp.py
    (analyzeHeadless lives in Ghidra's support/ dir — locate it on your install, don't guess paths.)
  6. MCP bridge (optional). If ghidra-mcp is configured, pull decompilations and xrefs through its tools — confirm the actual port from your own config (commonly 8765) rather than assuming.
  7. Hand off when static runs out — dynamic confirmation goes to gdb/Frida (reverse-eng-binary-triage step 4); patch diffing between two builds is ghidriff's job.

Gotchas

  • Wrong language/compiler spec on import → confident but wrong pseudocode; re-import with the correct variant if decompilation looks structurally impossible.
  • Default analyzers aren't always enough — for aggressive optimizations or unusual files, rerun analysis with more options enabled rather than accepting partial functions.
  • Jython is Python 2.7 — scripts written for modern Python silently fail; use PyGhidra for Python 3.
  • Large binaries are slow to analyze — scope analysis options, don't just wait and assume a hang.
  • Packed/obfuscated samples decompile to noise — unpack/deobfuscate first (reverse-eng-deobfuscation); don't read flattened junk as if it were logic.
  • Analyze untrusted binaries in an isolated VM.

Verify success

You can hand over named functions at concrete addresses with readable pseudocode for the key logic, plus reproducible steps (project/script/headless command) so a teammate gets the same result — or a headless run that emitted decompilations for every sample in the batch.

References

Ghidra docs (incl. the analyzeHeadless README); PyGhidra; ghidriff for patch diffing.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыНетНет
Выполняет команды shellНетНет
Ходит в сетьДаДа
Использует коннекторыНетНет
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

  1. СредняяPrompt injection · injection.no_confirmationSKILL.md:37
  2. СредняяPrompt injection · injection.no_confirmationSKILL.md:60
  3. ИнфоСсылка · Ссылки на внешние домены

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v2026.10.14-ee0e0c513 нояб. 2026 г.ee0e0c50190672fПодписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login