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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
ceasta — reverse engineering tool with a built-in MCP server: an AI can debug your binary, not just read it — breakpoints, stepping, memory, calling functions. disassembler + decompiler + x64dbg-style debugger in one. windows gui, linux cli. | Kitploit
Tools/GitHubGitHub/ngwg/ceasta
Static AnalysisDynamic Analysis (Sandboxing)Reverse EngineeringScripting & AutomationDebuggersMalware AnalysisBinary AnalysisAI-Assisted ReversingBinary Exploitation
GitHubngwg/ceasta

ceasta

reverse engineering tool with a built-in MCP server: an AI can debug your binary, not just read it — breakpoints, stepping, memory, calling functions. disassembler + decompiler + x64dbg-style debugger in one. windows gui, linux cli.

251318h 16m agoReviewed by Kitploit
View RepositoryWebsite

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

ceasta

ceasta

a disassembler, decompiler and debugger in one — for windows and linux

latest release platforms license c++17

ida-style listing, a decompiler, a function graph, an x64dbg-style debugger, lua plugins, and a built-in MCP server so you can point an AI at a binary — one small program, everything vendored, nothing to install to build.

listing

one function, three ways

ceasta shows the same code from raw bytes up to readable c, so you can drop to whatever level you need:

root@kitploit:~
; assembly - the real instructions // pseudocode (f5) - reconstructed c checksum proc int checksum(int rdi) movzx edx, byte ptr [rdi] { test dl, dl rdx = *(char*)rdi; je loc_1191 if (rdx == 0) { mov eax, 0x1505 return 0x1505; loc_1179: } mov ecx, eax rax = 0x1505; shl ecx, 5 do { add eax, ecx rax = rax + (rax << 5) + rdx; add rdi, 1 rdi = rdi + 1; movzx edx, dl rdx = *(char*)rdi; add eax, edx } while (rdx != 0); movzx edx, byte ptr [rdi] return rax; test dl, dl } jne loc_1179 ret loc_1191: mov eax, 0x1505 ret

that's djb2 (5381 is 0x1505, and (h << 5) + h is h * 33). the decompiler is best-effort: no types or structs yet, so you read registers and casts - great for getting a routine quickly, while the listing stays the source of truth.

download

grab it from the releases page:

fileplatformwhat you get
ceasta-x.y.z-setup.exewindows 10/11 x64the full app, installs for your user (no admin), start menu + optional "open with ceasta"
ceasta-x.y.z-windows-x64.zipwindows x64the full app, portable — unzip and run ceasta.exe
ceasta-cli-x.y.z-linux-x64.tar.gzlinux x64ceasta-cli + plugins: analysis, disassembly, decompiler, scripting, terminal debugger (on linux)

what it does

  • opens pe files (exe, dll, sys — 32 and 64 bit), elf (x86 / x64) and raw shellcode
  • auto analysis: functions (entry, exports, symbols, .pdata, tls callbacks, calls, pointers in data), switch tables, xrefs, strings (ascii + utf-16), imports / exports, thunks, noreturn calls
  • ida-style listing: names instead of addresses, labels, xref and string comments
  • function graph (space): colored edges, zoom with ctrl + wheel, drag to pan
  • decompiler (f5): c-like pseudocode for a function — if / else, while / do, switch, calls with names
  • debugger: start or attach, breakpoints, step into / over, run to cursor, pause, registers, stack, live memory
    • windows: full gui debugger + terminal, win32 debug api, 32-bit via wow64
    • linux: a terminal debugger on ptrace (ceasta-cli dbg) — breakpoints, stepping, registers, memory. basic but real; best on single-threaded targets
  • decompiler while debugging: stopped in a function, the pseudocode marks the current line
  • call a function in the running program (call decrypt "..."), record indirect call targets as xrefs (trace)
  • binary diff: match functions between two builds and see what changed
  • library signatures: name known functions in a stripped binary (sigmake / sigapply)
  • a built-in MCP server: connect an AI (Claude Code, Cursor, ...) to the open binary — see connect an AI
  • rename, comments, jump to address or name, xrefs, byte search, back / forward
  • names, comments and breakpoints save per file, and to a committable <binary>.ceasta next to it
  • lua plugins and a lua console; ceasta-cli for scripts and ci

layout

one window, nothing floating around:

  • top: menu and toolbar
  • left: functions
  • middle: overview band, then the listing, the graph, or the pseudocode
  • right: imports / exports / strings / segments / xrefs, with the debugger (registers + stack) under it
  • bottom: output + lua console, hex, breakpoints, modules
  • drag the lines between panels to resize, the view menu hides panels and switches theme, ctrl + / ctrl - changes the text size

graph

the decompiler (f5):

pseudocode

keys

keywhatkeywhat
ctrl+oopen a filespacelisting / graph
gjump to address or namef5pseudocode (decompiler)
enter / double clickfollow the operandalt+bsearch bytes
esc / ctrl+enterback / forwardf9start debugging / continue
nrenamef7 / f8step into / over
;commentf4run to cursor
xreferences to heref2toggle breakpoint
ctrl+ssave names and commentsf1all shortcuts

plugins

plugins are lua files in plugins/ (next to the program) or in %APPDATA%\ceasta\plugins. they add commands to the plugins menu. five come with it: file summary, crypto finder, wrapper namer, strings report, call tracer (debugger).

root@kitploit:~
ceasta.register_command("Count calls", function()
    local n = 0
    for _, fn in ipairs(ceasta.functions()) do
        n = n + #ceasta.xrefs_to(fn.addr)
    end
    ceasta.log(n .. " references to functions")
end)

the whole api is in the lua scripting guide. the output panel has a lua prompt too — try ceasta.name(ceasta.here()).

cli

root@kitploit:~
ceasta-cli info file.exe            format, entry, segments
ceasta-cli funcs file.exe           functions
ceasta-cli disasm file.exe main 40  listing from a name or address
ceasta-cli graph file.exe start     basic blocks of a function
ceasta-cli decompile file.exe main  pseudocode for a function
ceasta-cli xrefs file.exe CreateFileW
ceasta-cli find file.exe "48 8b ?? 05"
ceasta-cli run file.exe script.lua  run a plugin / script
ceasta-cli dbg ./program [args]     interactive debugger (linux + windows)
ceasta-cli diff old.exe new.exe     match functions, show what changed
ceasta-cli sigmake libc.a lib.sig   make signatures from a file with symbols
ceasta-cli sigapply stripped lib.sig  name matching functions
ceasta-cli mcp file.exe             serve the file to an AI over MCP

connect an AI

point an AI (Claude Code, Claude Desktop, Cursor, ...) at the binary through ceasta's built-in MCP server:

root@kitploit:~
claude mcp add ceasta -- ceasta-cli mcp /path/to/target.exe

it can decompile, read xrefs, rename functions, diff builds, and — with --allow-debug — set breakpoints, step, read memory and even call a function in the running program. the full guide, including the debugger tools and the safety notes, is in connect an AI.

on linux

the gui is windows-only, but the command line tool does the analysis, disassembly, decompiler, scripting and a terminal debugger. grab ceasta-cli-x.y.z-linux-x64.tar.gz, unpack and run — nothing else to install:

root@kitploit:~
tar xzf ceasta-cli-*-linux-x64.tar.gz
cd ceasta-cli-*-linux-x64

./ceasta-cli info /bin/ls                   format, entry, function / import / string counts
./ceasta-cli decompile /bin/ls start        pseudocode for the entry point
./ceasta-cli run /bin/ls plugins/hello.lua  run a lua plugin
./ceasta-cli dbg ./program                  debug it (break, step, registers, memory)

it reads elf (x86 / x64) and windows pe files alike, so you can look at a windows exe from linux too.

the terminal debugger (dbg) is a ptrace debugger with ceasta's names, disassembly and decompiler built in:

root@kitploit:~
(ceasta) b main            break at a name or address
(ceasta) c                 continue
(ceasta) ni / si           step over / into      until <addr>  run to
(ceasta) r                 registers             k  stack       x <addr>  memory
(ceasta) u                 disassemble here (with names)
(ceasta) dec               decompile the function you're stopped in
(ceasta) lua ...           run lua against the live process

build

everything needed is in the repo — just a compiler, nothing to fetch.

windows

  • visual studio 2022: open ceasta.sln, pick Release | x64, build → build\msvc\Release
  • or cmake: cmake -S . -B build then cmake --build build --config Release
  • release files (zip + installer, needs inno setup 6): powershell -ExecutionPolicy Bypass -File installer\package.ps1

linux (core + cli, the gui is windows-only)

root@kitploit:~
cmake -S . -B build && cmake --build build -j

code

  • src/app.* — state, actions and the main layout
  • src/ui/ — one file per panel (top_bar, left_panel, ida_view, graph_view, pseudo_view, right_panel, cpu_panel, bottom_panel, status_bar, dialogs)
  • src/widgets/ — small shared bits (nav_band, splitter)
  • src/core/ — no ui: loaders (binary, pe, elf), disasm (capstone), analysis, database, decompiler, lua_host, debugger (win32) + debugger_linux (ptrace), os
  • src/cli/ — ceasta-cli and the dbg terminal debugger
  • plugins/ — lua plugins that ship with it
  • docs/ — the lua guide, the changelog, third-party licenses, screenshots
  • installer/ — inno setup script and packaging
  • third_party/ — imgui, capstone (x86 only), lua 5.4

license

ceasta is GPLv3. the vendored libraries keep their own (permissive) licenses — dear imgui and lua are MIT, capstone is BSD; details in docs/THIRD_PARTY_NOTICES.md.

Download Tool