Build
Started from software: APIs, web apps, automation, backends.
>_A
HANDLEAmped
GITHUB@AmpedWasTaken
ROLEDeveloper / Security Builder
FOCUSWeb · Recon · Tooling
MODEWhite-hat / Responsible
>_ABOUT / AMPED
I like building systems. I like understanding their failure modes more.
Amped is the name I use for my public security work. I'm a software developer first, which is probably why I approach security by building small tools, reproducing behavior, and tracing the system instead of only running scanners.
How I got here
Build → inspect → automate → research.
Inspect
Got more interested in what happens at the boundaries: HTTP, auth, routing, caching, network behavior.
Tool
Turned repeated manual checks into focused CLI tools and monitoring projects.
Research
Now building a public workflow around evidence, disclosure, and reproducible write-ups.
02
The workbench.
Most projects start because I'm doing the same thing twice and decide it should become a tool. The stack changes; the preference for direct control and inspectable output doesn't.
LANGGo / TypeScript / Python / PHP
WEBNext.js / Node.js / Laravel
SECHTTP / Web / Recon / Monitoring
BIASCLI-first / Evidence-first / Small tools
>
The goal isn't to look like a hacker. It's to leave behind code, evidence, and write-ups that make it obvious I understand what I built and what I tested.