! warned

! warned

reverse engineering · web · tooling

I take programs apart to see how they work, then write the small tools that keep the notes in order. Windows, mostly. Mostly at night.

What I actually write

Bands are honest, not decorative. Daily means I open it without thinking. If something is missing, I have not needed it yet.

  1. JavaScript

    daily

    Node for the tools, the browser for the pages. Most of what I ship is this.

    in: reb, this page

  2. HTML & CSS

    daily

    Layout, type, and the parts that are supposed to move. No framework in the way.

    in: every page here

  3. Python

    regular

    Frida hooks and scripts for jobs that are only boring the second time.

    in: runtime harnesses

  4. PowerShell

    regular

    PATH, environment variables, batch runs. Windows does not care how much I like bash.

    in: setup, glue

  5. Java

    when required

    Ghidra scripts. That is the entire reason, and it is a good one.

    in: dump and decompile scripts

  6. x86-64 assembly

    reading only

    I read it all day in disassembly lists. I am not writing a compiler with it.

    in: every dossier

The bench

Every binary I open gets a folder and a dossier: hash, sections, imports, what Ghidra found, whether Frida has run, and the exact question I stopped on.

One command, reb, prints where I am and what the next step is. The point is not the tool. The point is that the next session starts where the last one stopped instead of repeating an hour of work.

static pass
Ghidra headless, scripted imports into a per-target project
runtime pass
Frida harness per target, session log kept as JSON lines
paperwork
layers, evidence, dead ends, next move, in markdown

Find me