Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyยฉ 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
idalib-cli โ€” Agent-native CLI wrapping IDA Pro IDALib for stateless, JSON-output binary analysis: disassembly, Hex-Rays decompilation, CFG, xrefs, strings, and batch or parallel IDB processing. | Kitploit
Tools/GitHubGitHub/ylca0/idalib-cli
Static AnalysisCode AnalysisDynamic Code Analysis (DAST)Reverse EngineeringScripting & AutomationUtilities & FrameworksBinary AnalysisAI-Assisted Reversing
GitHubylca0/idalib-cli

idalib-cli

Agent-native CLI wrapping IDA Pro IDALib for stateless, JSON-output binary analysis: disassembly, Hex-Rays decompilation, CFG, xrefs, strings, and batch or parallel IDB processing.

2331132 months agoReviewed by Kitploit
View Repository
Share

idalib-cli๏ธ idalib-cli

Agent-native CLI for the IDA Pro IDALib โ€” every command takes one -d/--db flag, every answer is JSON.

English ยท ไธญๆ–‡

IDA Pro 9.1 idalib-rs 0.6.1 v0.9.1 Apache-2.0


โœจ Features

  • ๐Ÿ—„๏ธ Stateless โ€” pass -d/--db <PATH> (a binary or an .i64); no daemon, no session bookkeeping.
  • ๐Ÿ’พ Persistent IDB state โ€” the IDB file is the state: comments, bookmarks, names and analysis survive across processes.
  • ๐Ÿงฉ Full IDALib coverage โ€” segments, functions, CFG, disassembly, Hex-Rays decompilation, strings, names, xrefs, entries, metadata, comments, bookmarks, FLIRT signatures.
  • โšก batch & parallel โ€” run many commands with one IDB open; fan a command out to many databases concurrently (glob supported).
  • ๐Ÿค– Agent-first โ€” one JSON document on stdout, errors on stderr; skills included for Codex / Claude Code / OpenCode.

๐Ÿš€ Install

Prerequisites: IDA Pro 9.1 (licensed, launched once) ยท IDA 9.1 SDK unpacked (build time only) ยท Rust + LLVM/Clang (bindgen requirements)

export IDADIR="/Applications/IDA Professional 9.1.app/Contents/MacOS"  # IDA install dir
export IDASDKDIR=/path/to/idasdk91                                     # unpacked SDK (absolute path!)

git clone <this-repo> && cd idalib-cli
cargo install --path .

idalib-cli info    # โœ… verify tool version, IDA version, license

The SDK is needed at build time only; the binary links your local IDA libraries at runtime. Dev checks without an SDK: cargo test --no-default-features --features stub-idalib.

๐ŸŽฎ Commands & usage

Every command needs -d/--db <PATH> โ€” an IDB file (.i64) or a binary (an IDB is created next to it on first use). Addresses accept 0x401000 or 401000. Output is always one JSON document; errors go to stderr with a non-zero exit code.

Database

CommandDescription
idalib-cli -d <bin-or-i64> db infoResolved paths, IDB state, size

Query

CommandDescription
idalib-cli -d <db> metaFiletype, compiler, bitness
idalib-cli -d <db> processorProcessor info
idalib-cli -d <db> segmentsAll segments
idalib-cli -d <db> segments-by-range -a <ea>Segment containing an address
idalib-cli -d <db> functions [-u]Function list (-u = skip lib/thunk)
idalib-cli -d <db> function -a <ea>One function: CFG, blocks, xrefs
idalib-cli -d <db> disasm -a <ea> [-n N]Disassemble N instructions (default 8)
idalib-cli -d <db> decompile -a <ea> [--all-blocks]Hex-Rays pseudo-code
idalib-cli -d <db> insn -a <ea>Single instruction (+ group/is_call/is_ret classification)
idalib-cli -d <db> stringsString list
idalib-cli -d <db> namesNamed locations
idalib-cli -d <db> xrefs [-a <ea>] [--all] [--from]Xrefs to an address (default) or from it (--from), or all
idalib-cli -d <db> find --text <s>Search text hits
idalib-cli -d <db> find --imm 0x1337Search immediate-value hits
idalib-cli -d <db> find --pattern 554889e5Search a hex byte pattern
idalib-cli -d <db> bytes -a <ea> [-n N] [--width byte|word|dword|qword]Raw bytes (hexdump) or little-endian integers
idalib-cli -d <db> entriesEntry points

Edit (persisted in the IDB)

CommandDescription
idalib-cli -d <db> comments get|set|append|remove -a <ea> [-c "text"]Comments
idalib-cli -d <db> bookmarks list|add|get|remove -a <ea> [-d "desc"]Bookmarks
idalib-cli -d <db> rename -a <ea> -n <name>Rename a function / data label
idalib-cli -d <db> set-type -a <ea> -t "int f(int, char *);"Apply a C type declaration (function prototype / data type)
idalib-cli -d <db> signatures --make [--only-pat]Generate FLIRT signatures

Combine

CommandDescription
idalib-cli -d <db> batch -- <op> [<op>...]Sequential ops, IDB opened once
idalib-cli parallel -d <list|glob> [--jobs N] -- <op>One op across many DBs, subprocess each
idalib-cli info [--version|--ida|--all]Tool / IDA version, license

Scenario walkthroughs

๐Ÿ”Ž Triage an unknown binary

idalib-cli -d ./sample meta            # what is it? (filetype/compiler/bitness)
idalib-cli -d ./sample segments        # memory layout
idalib-cli -d ./sample strings         # quick hints
idalib-cli -d ./sample functions -u    # user code only

๐Ÿ” Dig into a function

idalib-cli -d ./sample function -a 0x401000       # CFG + blocks + xrefs
idalib-cli -d ./sample decompile -a 0x401000      # read the pseudo-code
idalib-cli -d ./sample disasm -a 0x401000 -n 20   # or the raw instructions
idalib-cli -d ./sample xrefs -a 0x401000 --all    # who calls it

๐Ÿ“ Annotate findings (survives across processes/agents)

idalib-cli -d ./sample comments set -a 0x401000 -c "parses config, see 0x402100"
idalib-cli -d ./sample bookmarks add -a 0x401000 -d "entry point"
idalib-cli -d ./sample comments get -a 0x401000    # verify

โšก Bulk analysis of many samples

# first pass: create IDBs + overview for every sample
idalib-cli parallel -d "./samples/*.bin" -- "batch -- meta functions -u"

# deep pass: decompile one hot function in every IDB
idalib-cli parallel -d "./samples/*.i64" --jobs 8 -- "decompile -a 0x401000"

๐Ÿ”Ž Search & inspect raw data

idalib-cli -d ./sample find --text "MAGIC"            # string hits
idalib-cli -d ./sample find --imm 0x1337              # immediate-value hits
idalib-cli -d ./sample find --pattern 554889e5        # byte pattern (prologue)
idalib-cli -d ./sample bytes -a 0x401000 -n 32        # hexdump
idalib-cli -d ./sample bytes -a 0x401000 --width qword -n 4
idalib-cli -d ./sample xrefs -a 0x401000 --from       # outgoing refs (calls)
idalib-cli -d ./sample rename -a 0x401000 -n decrypt  # label it
idalib-cli -d ./sample set-type -a 0x401000 -t "int f(const char *, int);"  # set prototype

๐Ÿค– Agent-friendly batched inspection (one JSON doc)

idalib-cli -d ./sample batch -- "meta" "segments" "functions -u" "decompile -a 0x401000"

Agent workflow guide: skills/idalib-cli/SKILL.md; a runnable end-to-end example in examples/workflow.sh.

Sample output (decompile)
{
  "id": 7,
  "start": "0x401000",
  "end": "0x401080",
  "size": 128,
  "name": "main",
  "blocks": 3,
  "decompiled": true,
  "pseudocode": "int __cdecl main(...) { ... }"
}

โš™๏ธ Configuration

Optional ~/.idapro/idalib-cli/config.toml (base dir: $IDALIB_CLI_HOME):

FieldDescription
idadirIDA install dir (default: auto-detected)
idb_dirWhere new IDBs are created (default: next to the binary)
default_dbUsed when -d is omitted
saveSave the IDB after each command (default true)
auto_analyseRun full auto-analysis when creating an IDB (default true)

โ“ FAQ

Where does the IDB go when I pass a binary?

Next to the binary: ./target.bin โ†’ ./target.bin.i64. Set idb_dir in the config to change the location.

What do batch / parallel actually do?
Download Tool

Most Popular

View all โ†’

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    ๐ŸŽฏ The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurityโ€”where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools โ†’