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 instalações+3 em 7 dias60 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install trailofbits/idacGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotef6292c7a…4ff0a6da
f6292c7aa3ce…c8534ff0a6da18 arquivos · 33.2 KBVarreduraMédio3 achados
- Script executável junto com a skillreferences/templates/locals-jq-snippets.sh
- injection.no_confirmationreferences/troubleshooting.md:47
- Links para domínios externos
Fontegithub.com/trailofbits/idac/tree/main/plugins/idac/skills/idac@fb078c8
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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.
- Run
idac database open PATH --jsonoutside 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 onlyidac database open PATH --jsonin 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 usesandbox_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. - In a separate tool call, run
idac targets list --json. Confirm the returned record is READY and, for a hosted session,session_statusisready. - Use
--instance RECORD_IDon every database command, includingbatchandpreviewwrappers. Share that record with participating agents. If it disappears, stop and diagnose; do not replace it with a path selector or implicit startup. - 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_IDabove. Outside per-command sandboxes,-c/--context PATHcan open or attach to a database or binary; omitting both selectors requires exactly one READY instance. Put target and timeout options on the wrapper forbatchandpreview. - Run one
idaccommand at a time per target. Write function/type lists and family reads to--outeven with filters; a filtered list can exceed the inline limit. Usedecompilemanyfor several functions and orderedbatchfiles for related edits and readbacks in one session. - During type or prototype recovery, use
decompile --f5ordecompilemany --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-cccan be committed directly with readback. Continue authorized edits through verification. - Run
idac doctorwhen 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:
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.hFor 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.
Arquivos desta versão
agents/1285 B
- openai.yaml285 B
references/1693.8 KB
templates/87.1 KB
- checkpoint-note.md874 B
- locals-jq-snippets.sh939 B
- locals-plan.json169 B
- prototype-pass.idac971 B
- prototype-preview.idac1.5 KB
- README.md1.6 KB
- rename-pass.idac467 B
- rename-preview.idac783 B
- class-recovery.md8.8 KB
- cli.md13.0 KB
- ida-advanced-type-annotations.md12.5 KB
- ida-cpp-type-details.md5.1 KB
- ida-set-types.md13.4 KB
- targets-and-backends.md11.6 KB
- troubleshooting.md7.8 KB
- workflows.md14.3 KB
- SKILL.md7.7 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillreferences/templates/locals-jq-snippets.sh
- MédiaPrompt injection · injection.no_confirmationreferences/troubleshooting.md:47
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.2-fb078c8 | 13 de nov. de 2026 | fb078c8 | f6292c7a | Assinada | – |
Mais de trailofbits
Tudo deste publicadorMais em Engenharia reversa e fuzzing
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login