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
trailofbits/idacReverse engineering and fuzzing

idac

⁨Analyze binaries and inspect or edit IDA Pro databases with the local idac CLI. Use for IDA decompilation, xrefs, type or class recovery, and database edits, rather than general RE explanations or source-only work.⁩

v2026.11.2-fb078c83 installs+3 in 7 days60 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install trailofbits/idac

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

SignatureSigned, ed25519
Jj7SKbov1z…vYPsb3Dg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagef6292c7a…4ff0a6da
f6292c7aa3ce…c8534ff0a6da18 files · ⁦33.2 KB⁩
ScanMedium3 findings
  • Executable script shipped with the skillreferences/templates/locals-jq-snippets.sh
  • injection.no_confirmationreferences/troubleshooting.md:47
  • Links to outside domains
See the full scan
Sourcegithub.com/trailofbits/idac/tree/main/plugins/idac/skills/idac@fb078c8

Use idac against a live IDA GUI, an existing .i64, or a binary IDA can open. Every operation uses ida-nexus. Prefer first-class commands; use idac py exec when they cannot express the required IDA operation.

Follow the user's target, scope, and deliverables. Explicit user instructions take precedence over this skill's defaults. Inspection requests stay read-only; recovery, annotations, and workspace creation belong only where the task calls for them.

Database lifetime in Linux command sandboxes

Complete this setup before any database read or edit, including metadata and function lists. Opening via -c/--context inside a per-command sandbox can leave the database unclean when the command exits; repeated opens create crash backups.

  1. Run idac database open PATH --json outside the command sandbox. In Codex, check both $CODEX_HOME/rules/ (default ~/.codex/rules/) and repository .codex/rules/: absence of repository rules does not imply absence of global rules. Inspect the rules in their own tool call. With a trusted allow rule, send only idac database open PATH --json in the next command tool call; do not combine it with rule checks, cd, assignments, pipes, or other shell commands. The approved prefix runs this standalone invocation outside the sandbox without a new approval. Otherwise use sandbox_permissions="require_escalated" when supported. Follow the configured approval policy; the skill grants no permission. If a shared hosted session or live GUI already exists, attach to its exact record.
  2. In a separate tool call, run idac targets list --json. Confirm the returned record is READY and, for a hosted session, session_status is ready.
  3. Use --instance RECORD_ID on every database command, including batch and preview wrappers. Share that record with participating agents. If it disappears, stop and diagnose; do not replace it with a path selector or implicit startup.
  4. Before your final response, close a hosted session you opened for this task: idac database close --instance RECORD_ID --json. Wait for successful shutdown. For a shared task, the coordinating agent closes it after all participants finish; agents joining someone else's session leave its lifetime to that owner.

Read hosted sessions for coordination, recovery, and startup when neither approval route is available.

Operating defaults

  • Work from the binary and database evidence. Consult the web or external source trees only when requested or when external correlation is part of the task.
  • Keep the selected target on subsequent commands. Hosted sessions use the exact --instance RECORD_ID above. Outside per-command sandboxes, -c/--context PATH can open or attach to a database or binary; omitting both selectors requires exactly one READY instance. Put target and timeout options on the wrapper for batch and preview.
  • Run one idac command at a time per target. Write function/type lists and family reads to --out even with filters; a filtered list can exceed the inline limit. Use decompilemany for several functions and ordered batch files for related edits and readbacks in one session.
  • During type or prototype recovery, use decompile --f5 or decompilemany --f5 (--no-cache) so readback reflects current types.
  • For edits, read mutation workflows. Inspect the current prototype before setting it, declare support types before dependent prototypes, and reanalyze after meaningful type or prototype changes before calibrating local selectors from fresh JSON. Preview parser-risky type changes or uncertain selectors and inspect the artifact before committing. Confirmed symbol renames, comments, and parameter-name edits with --preserve-cc can be committed directly with readback. Continue authorized edits through verification.
  • Run idac doctor when the runtime stack is uncertain. For a Nexus failure, diagnose the reported cause using troubleshooting. Read affected state before retrying a mutation with an uncertain outcome.

Read what the task needs

Common command paths:

text
function list FILTER --demangle --json --out functions.json
function prototype show FUNC
function prototype set FUNC --preserve-cc --decl 'RETURN CONVENTION FUNC(ARGS);'
misc rename FUNC NAME
misc reanalyze FUNC
misc reanalyze START --end END
comment show FUNC --scope function
comment set FUNC TEXT --scope function
type show NAME
type check --decl-file types.h
type declare --replace --decl-file types.h

For parameter names or a return type, edit the declaration from function prototype show and use set, preserving the other types, parameters, and calling convention. Add --preserve-cc to keep IDA's existing calling convention even when its parser normalizes the declaration to another convention. For __usercall and __userpurge, the flag retains explicit argument locations by parameter position and the return location, requiring unchanged parameter count and type sizes. Supply explicit locations without the flag when changing those. This does not require an IDAPython script. Use the known paths directly; consult targeted --help for unfamiliar flags or subcommands. Use --full-help when the command family is unclear. Read only the relevant reference sections.

Reanalysis requires a function name or address. Use misc reanalyze START --end END for a bounded address range.

Task Reference
Command grammar, reads, filters, output formats CLI quick reference
Select a GUI or headless target; understand saves and runtime requirements Targets and backends
Prototypes, locals, type edits, annotations, preview, batch, IDAPython Mutation workflows
Recover C++ layouts, inheritance, or virtual targets Class recovery
Write IDA-compatible C++ class or vtable declarations C++ type details
Custom calling conventions or IDA declaration keywords IDA type syntax
Shifted pointers, scattered arguments, or display annotations Advanced type annotations
Discovery, import, preview, or stale-readback failures Troubleshooting

Artifacts and completion

Use the user's existing artifact locations and workspace conventions. When a recovery workspace is requested or useful for sustained work, idac workspace init provides headers, audit notes, and temporary artifact directories; follow its installed conventions. Keep existing audit logs append-only. Optional templates cover prototype and local-edit passes.

For analysis, ground findings in function names or addresses and state unresolved uncertainty. For edits, verify the affected database state and fresh pseudocode where relevant. Report artifact paths and whether changes were saved: successful headless mutations are checkpointed automatically; live GUI saves are explicit. Checkpointing does not close a hosted session: finish the shutdown step above before reporting completion, unless its shared owner still needs it. Stop when the requested result is supported by evidence; cosmetic pseudocode cleanup is useful only when it helps that result.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillreferences/templates/locals-jq-snippets.sh
  2. MediumPrompt injection · injection.no_confirmationreferences/troubleshooting.md:47
  3. InfoLink · Links to outside domains

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

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.2-fb078c8Nov 13, 2026fb078c8f6292c7aSigned–

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