Cutter Python — authorized scripting orientation
Cutter (rizinorg/cutter) is a GUI over rizin. Its Python surface helps automate repetitive, authorized analysis steps. Use scripts only on binaries you may examine.
Snapshot
| Field | Value |
|---|---|
| Surface | Cutter embedded Python |
| Product start | Cutter getting started |
| Plugins sibling | Cutter plugins |
| Headless peer | rizin scripting |
Allowed framing
- Enumerating functions/strings you already see in the UI and dumping a CSV for the case binder.
- Replaying the same annotation checklist across a student-compiled corpus.
- Teaching students to keep scripts short, reviewed and version-pinned with the Cutter/rizin builds.
Scope we will not cover
- No crack/keygen generators disguised as "Cutter scripts."
- No DRM or license-check defeat recipes.
- No anti-anti-debug cookbooks.
- No claiming a script replaces authorization or chain-of-custody hashes.
Beginner path (authorized only)
- Finish Cutter getting started on a binary you compiled.
- Open the Python console; run a read-only listing (functions/strings) and save output beside the SHA-256.
- Prefer scripts that only export Evidence over scripts that mutate the binary.
- If you need installable extensions, read Cutter plugins.
- For CI/headless automation, graduate to rizin scripting under the same authorization.
- Use Cutter Python to automate repeatable authorized UI work, not to invent malware tooling.
- Prefer plugins for shared lab features; rizin scripting for headless pipelines.
- Refuse crack, DRM-bypass and anti-anti-debug framing.
For legal, authorized and educational use only.
FAQ
How is this different from cutter-plugins-overview?
Plugins overview covers installing/enabling plugin packages. This page is in-session Python scripting orientation — small automations you write for an authorized sample.
Cutter Python vs rizin scripting?
Cutter embeds a Python console/API over the rizin session. For headless rizin automation see rizin scripting. Do not invent flags — check your installed Cutter/rizin docs.
Do I need Python to use Cutter?
No. Complete Cutter getting started first. Add Python only when you repeat the same navigation on many authorized samples.
Can scripts talk to the network?
Treat network-capable scripts as out of scope for beginner labs unless your org reviews them. Prefer local Evidence writes under the case directory.
Does this teach unpack-for-piracy or anti-debug defeat?
No. Authorized analysis and education only — no crack/keygen, DRM bypass or anti-anti-debug cookbooks.