Skip to content
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-binary-triageReverse engineering and fuzzing

reverse-eng-binary-triage

⁨Triage a native binary you can run or read — find the vulnerable logic, the dangerous sinks, and the input path — with static + dynamic analysis. Load when handed an ELF/PE/Mach-O, a thick client, a standalone or obfuscated binary, or a service whose source you don't have. Signals: a compiled execut⁩

v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
2BHcv4yrp8…vqO2QjAA==The CLI checks the SHA-256 and the signature before it writes a file.
Package4e285028…4103ef37
4e28502879e1…1e424103ef371 file · ⁦1.9 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-binary-triage@ee0e0c5

When it applies

You have a compiled binary — a thick desktop/mobile client, a network service, a setuid helper during privesc, or a firmware component (reverse-eng-firmware) — and no source. You need to understand what it does, where attacker input reaches, and whether that path is exploitable, before committing to exploit-poc-development.

Why it works

A binary carries its logic in the code and its intent in the strings, imports, and symbols. Cheap static passes (strings, imports, cross-references) point straight at the interesting functions; a debugger then confirms what actually happens at runtime, so you spend deep analysis only on the paths that matter.

Method

  1. Cheap recon first. file, strings -n8, and the import table tell you the language, protections, and intent in seconds. checksec (or rabin2 -I) for NX / PIE / RELRO / canary — they scope what an exploit would even need.
  2. Map input → sink. Find where input enters (recv, read, argv, getenv, a file/format parse) and trace to dangerous sinks: strcpy/memcpy/sprintf/gets (overflow), system/exec/popen (command injection), format-string sinks (printf(user)), and integer math feeding an allocation size.
  3. Read it in a decompiler. Ghidra or radare2/Cutter — jump to the sink, follow cross-references back to reachable entry points, and note the preconditions to reach it.
  4. Confirm dynamically. Run under gdb+GEF/pwndbg (or ltrace/strace), break at the sink, feed a marker input, and watch whether you control size/pointer/format. A crash you can steer (controlled $pc, overwritten pointer) is the confirmation.
  5. Pull the low-hanging intel — hardcoded secrets/keys (CWE-798), debug/backdoor paths, weak auth checks (a strcmp against a literal), and custom-protocol structure for later fuzzing.

Gotchas

  • Stripped binaries have no symbols — lean on strings, imports, and library-call signatures; name functions as you go so the map survives.
  • Packed/obfuscated (high entropy, tiny import table) → deobfuscate first (reverse-eng-deobfuscation).
  • A crash is not yet a bug worth reporting — determine control and impact before you claim it; validate with reporting-triage-validation.
  • Analyze untrusted binaries in an isolated VM — running an unknown executable is itself risky.

Verify success

You can state the input path, the vulnerable sink, the preconditions to reach it, and a runtime observation (controlled crash or a leaked secret) that proves it — a concrete lead for exploit development, not a guess from the disassembly.

References

Ghidra & radare2 documentation; pwndbg/GEF; the checksec protections model; CWE-121/787/798.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c54e285028Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login