Your results are in.

Sidekick is a service and plugin for Binary Ninja that uses agentic AI to accelerate reverse engineering. Run agents across your binaries, monitor progress, review the results, follow the evidence, understand the work, and own what you deliver.

Sidekick's workspace monitor showing task status, active agents, analysis coverage, and budgets beside a chat explaining a finding in the selected binary.

Why use Sidekick?

Sidekick is designed to help reverse engineers deliver AI-generated results.

  • Own your work

    You stay in control of the work and stand behind what you deliver. Sidekick gives you the tools to manage multiple tasks, inspect the results, follow the linked evidence into the code, understand the work, and correct it if needed.

  • Do more with Binary Ninja

    Sidekick's agents draw deeply on Binary Ninja's analysis and API. Built-in specialized skills equip them to handle your tasks. A custom query language designed to efficiently access the analysis enables them to better reason about the code.

  • Privacy

    When data can't leave your network, run the self-hosted edition of Sidekick on your infrastructure. Apply the same tools and capabilities to your sensitive work.

Put agents on every binary.

Add your binaries and describe the task once. Sidekick runs it in a separate workspace for each binary. Set a limit to pause work when a workspace reaches its budget.

The New Workspace form. Binaries, five: dropbear, dnsmasq, lighttpd, dbclient, dropbearkey. Task: 'Review this binary for backdoors: hard-coded credentials, hidden listeners, and authentication bypasses. Record what you inspected and what you did not.' Run as: Run Batch, described as 'Run the same task independently for each binary.' The summary reads '5 binaries, 5 independent workspaces' and the button reads Start Batch (5).
One task, five binaries.
The Workspace Budget dialog for the dbclient workspace. It reads 'A one-time credit budget for this workspace. It doesn't reset monthly.' A card shows 1,706,389 credits spent with the status No limit and the line 'Set a limit to pause this workspace's chats when they reach it.' Under Budget, 'Limit to' is selected with 3,000,000 credits, and a line beneath reads '3,000,000 credits, 1,293,611 left after what's been spent'. The buttons are Cancel and Set Limit.
A credit limit for one of the five workspaces.

Monitor progress.

See which agents are active, which tasks are still open, and what each workspace has spent. Review the latest results as they come in.

Sidekick's Monitor view listing five workspaces from one batch, with columns for open tasks, active agents, coverage, agent time, and spend against budget. dbclient has three agents running, 20% coverage, and six minutes of agent time. dnsmasq has one agent running and no results yet. lighttpd, dropbearkey, and dropbear each list their latest results beneath their row. The last result under dropbear reads 'Blank-password none authentication bypasses the advertised two-factor requirement when -B an...'.
Five workspaces in one batch, with active agents, open tasks, spending, and the latest results in one view.

Review as deeply as you need.

Read the findings, or review a report beside the decompilation. Follow links to the cited code, data, and types, hovering for a preview or clicking to inspect. Go as far into the evidence as you need before using the result.

Binary Ninja with a malware sample open. On the right, a Sidekick pane shows a report artifact at a section headed 'Execution chain / concealment', a numbered list whose steps cite addresses as links. The first step begins 'Entry 0x40b270 calls 0x446ad0'. On the left, High Level IL shows the function at 0x40b270, _start, which calls sub_446ad0. Over the third step, a Binary Ninja preview popup is open on the address 0x410327 and shows the High Level IL of sub_410327.
A malware triage report beside the entry point it cites, with Binary Ninja's hover preview of another function.

Sidekick keeps a record of what it finds.

Sidekick records findings with their evidence. A second agent checks findings against the binary and records its verdict. You can revisit that record to see what supports a conclusion.

The Findings tab of a dropbear workspace showing finding 3 of 4, with the header 'Finding, Verified, Updated 11:56 AM'. The finding reads: 'All indexed listener-capable socket paths resolve to configured SSH service, requested SSH TCP forwarding, or authenticated Unix-domain agent forwarding; no independent hidden listener was identified.' Scope: indexed static listener-capable socket paths. Location: sub_417740, SSH and requested TCP forwarding; sub_41d140, authenticated agent forwarding. Notable: runtime sockets, external launch config, code mutation, indirect execution not tested.
A finding from a firmware review, marked Verified after its second read.

Correct what's wrong.

Every change an agent makes to your binary is its own transaction, with a description of what it did. When an agent gets something wrong, just revert the change.

The Changes tab of a workspace for Synth1.dll, listing the transactions an agent made, one per row, each with a description: 'Apply verified CLFO pointer to CPan modulation gate local', 'Connect CPan/CLFO virtual tables and correct folded offset-4 setter typing', 'Recover CPan and CLFO layouts from construction, RTTI, DSP access and...', 'Undo class-specific typing of a folded offset-0x20 setter...', and more. The row that begins 'Recover CPan and CLFO layouts' is selected, and a menu over it offers Show Details, Revert Transaction, and Delete Transaction, with Revert Transaction highlighted.
Transactions from an agent recovering a plugin's C++ classes, one of them about to be reverted.

Deliver your work.

Ask for a report, a detection rule, an extracted configuration, a script, and more. Each artifact is saved as a file you can review and export.

The Artifacts tab of the dropbear workspace showing a rendered Markdown file, dropbear-blank-password-twofactor.md, titled 'Firmware advisory: conditional Dropbear two-factor bypass'. It begins 'Status: Supported by static AArch64 analysis; not runtime-reproduced. Underlying notebook finding remains draft, pending independent validation. This is an authentication policy defect, not evidence of an intentional backdoor.' A 'Reviewed target' paragraph and a section headed 'Issue and affected configurations' follow.
A firmware advisory the agent wrote from its review.

An annotated database.

Names, types, and comments are saved in your Binary Ninja Database. Come back to it later, or hand it to a colleague.

Binary Ninja with dropbear open. On the left, High Level IL for recv_msg_userauth_request, scrolled to the none branch at 0x418a8c: a comparison against the string 'none', a call to send_msg_userauth_failure, and a comment that begins "'none' requires -B, an empty resolved account password" and goes on to say that no two-factor check precedes USERAUTH_SUCCESS, so public-key proof is not required here. On the right, a Sidekick Changes pane shows change 3 of 3, 'Replace userauth descriptive names with user-specified upstream Dropbe...', as a table with Property, Before, and After columns: handle_userauth_request became recv_msg_userauth_request, send_userauth_failure became send_msg_userauth_failure, send_userauth_success became send_msg_userauth_success, handle_password_auth became svr_auth_password, and handle_public_key_auth became svr_auth_pubkey.
Dropbear's authentication handler with upstream names and a comment, beside the change that applied them.

Find work when you need it.

Every workspace keeps its chat, findings, artifacts, and changes. Browse them in one list, or search across all of them. Open a match where it was recorded, and carry on from there.

The Sidekick tab's workspace list after a search for XOR. A strip reads All 25, Findings 4, Artifacts 1, Changes 1, Chats 19. Each row is a workspace with its matching results and when it was last active: three Mach-O samples last active two weeks ago, with results such as 'Fixed raw-TCP endpoint and XOR-encoded p...', 'ARM64 Mach-O XOR downloader', and 'XOR-decoding downloader with disguised argv...'; dropbear.bndb, one day ago; Synth1.dll.bndb, two weeks ago; and a Windows PE sample, four days ago. The search term is highlighted in each result.
A search for "XOR" across every workspace: 25 matches in findings, artifacts, changes, and chats.
Privacy

The same workflow, on your infrastructure.

When data can't leave your network, run Sidekick fully on-premises, with self-hosted models on your own hardware.

See self-hosted deployment

Own your work.

Let Sidekick accelerate it.

Start for Free