About BitJacker
The story behind the handle
No name, no photo, no city. Just a handle, a stack, and a few years of breaking things on purpose. Here's the long version.
/origin
I started building things because I had to. Not for school, not for clout — just because something needed to exist and no one else was going to make it. That mindset hasn't changed.
BitJacker isn't a brand. It's a handle. The person behind it stays opaque on purpose: identity is a leak waiting to happen, and the work should speak before the author does. What you can know is the trajectory — what got built, what got broken, and why.
/journey
-
[T-MINUS · early days]
> First Linux install
Discovered the terminal. Never looked back. Found out a computer is a thing you talk to, not a thing you click.
-
[T+1 · the breakage years]
> First server
Broke it. Fixed it. Broke it again on purpose. Learned more in a single weekend of bringing a box back online than in an entire year of a class on the same topic.
-
[T+2 · the unlock]
> First exploit (in a lab)
Realized security isn't a separate field. It's just systems thinking inverted — the same questions, asked from the other side of the wall.
-
[T+3 · ship something]
> First framework shipped
BadHand. Born from frustration with bloated pentest distros that bundle 400 tools so you can use 4. Started as a single Python file, grew into a modular CLI.
-
[T+4 · cut the cord]
> First offline AI
Uncensored-Coder. Because cloud LLMs come with leashes — rate limits, content policies, telemetry — and none of those should sit between me and a buffer-overflow tutorial in a lab.
-
[NOW live]
> Studying for eJPT, then Security+, then OSCP
Building tools the community actually uses. Cerberus Recon and LANScope are next in the pipeline. Certifications are scaffolding, not the destination.
/philosophy
Build it yourself. You'll understand it forever.
If a tool doesn't exist, that's not a problem — that's an opportunity.
Privacy isn't paranoia. It's hygiene.
/focus
Offensive security, self-hosted infrastructure, local-first AI, and game dev as a creative outlet.
The through-line is the same in every domain: build it, own it, understand it. Whether that's a pentest framework, an offline model, a homelab, or a level in Unreal — the rule is that nothing ships I couldn't take apart and put back together.
/not
// what i'm not
Not a script kiddie. Not an influencer. Not interested in hype cycles or AI-generated portfolios. Everything here is built by hand. If a tool has my name on it, I wrote it. If it doesn't ship yet, it's because I haven't finished — not because I'm farming engagement.
/stack
Not a buzzword list. These are the tools I open every day: