handlelustful
I'm studying how systems break so I can help them hold. Every bit of practice happens on machines I own or targets built to be attacked — labs, CTFs, and write-ups, never someone else's systems.
- role
- student
- discipline
- offensive security
- targets
- own labs & ctfs
- status
- learning
What I'm learning to break.
A study surface, not a certificate wall. These are the areas I'm working through in labs — some further along than others.
Web & API testing
Injection, broken object-level authorization, business-logic abuse, and the request nobody thought to validate.
Auth & access control
Session handling, token lifetimes, privilege boundaries, and every path around the login screen.
Network & infrastructure
Exposed services, weak segmentation, and lateral movement inside an authorized boundary.
Cloud configuration
Over-permissive roles, public buckets, forgotten keys, and identity misconfiguration.
Secure code review
Reading source for the flaw before it ships — trust boundaries, sinks, and unsafe defaults.
Reverse engineering
Static and dynamic binary analysis to understand what a program really does.
OSINT & attack surface
Mapping what an organization exposes to the internet without meaning to.
Research & reporting
Findings written so an engineer can reproduce, prioritize, and actually close them.
How I work a box, start to close.
Repeatable process beats improvisation. I practice the same phases a real assessment uses, so the habits are already there when the work is real.
- 01
Authorize
Nothing starts unless I own the target or it exists to be attacked. Permission and scope first — the gate, not a formality.
- 02
Recon
Map the reachable surface — hosts, endpoints, dependencies, and the assumptions holding them together.
- 03
Analyze
Hunt for the failure that automation misses: broken logic, misplaced trust, and states nobody designed for.
- 04
Validate
Prove real impact with the smallest possible footprint. No destructive testing, no user data taken.
- 05
Report
Reproducible steps, honest severity, and a fix that fits the codebase. I write every lab up as if an engineer had to ship the patch.
- 06
Retest
Return after the patch and confirm the door is actually closed — including the ways around it.
The line, in writing.
The difference between an ethical hacker and an attacker is consent and disclosure. I hold to both while I'm still learning, not after.
always
- Practice only on systems I own or that exist to be attacked
- Stay strictly inside the scope a lab or program defines
- Never touch production systems or real users
- Report anything I stumble onto to the owner first
- Follow coordinated disclosure timelines
- Be honest about what I do and do not know yet
never
- Access systems without permission
- Exfiltrate, retain, or resell user data
- Sell, trade, or leak vulnerabilities
- Deploy ransomware, backdoors, or persistence
- Take requests targeting individuals or private accounts
- Claim skills or authorization I do not have
If you are looking for someone to access an account, device, or system you do not own — I am not that person, and I will not refer you to one.
Ask the machine yourself.
A real prompt with a real command set. Type `help` to see what it knows — arrow keys walk history, tab completes.
sandboxed interface · nothing here touches a live host