Real binary exploitation, kernel fuzzing, and pwn practice with direct review on your exploit code and thinking. Structured progression, not endless tutorials.
Start the week with a small challenge that sharpens debugging, reversing, or scripting speed.
Work a bounded binary or kernel problem with a concrete objective instead of open-ended browsing.
Submit a PoC, exploit script, reproducer, or notes on the primitive you isolated and the dead ends you hit.
Review focuses on exploit logic, reliability, dead ends, and what to fix before the next challenge opens.
You choose a track, work the challenge, submit your artifact, get annotated feedback, and move forward only when the work is ready.
Start from Foundations, Binary Exploitation, Kernel Fuzzing, or Kernel Pwn based on current reps.
Step 01
Start from Foundations, Binary Exploitation, Kernel Fuzzing, or Kernel Pwn based on current reps.
Step 02
Attempt a bounded challenge with the right level of difficulty instead of getting lost in an endless platform catalog.
Step 03
Ship the code, notes, and reasoning so the review is about your actual work product.
Step 04
Mentor feedback calls out primitives, exploit reliability, blind spots, and stronger next steps.
Step 05
Progression compounds only after the current solve is stable and your reasoning is clean.
| Area | Videos | Open platforms | Hackers School |
|---|---|---|---|
| Unit of progress | Watching explanations and taking notes. | Self-directed challenge volume. | Reviewed exploits, PoCs, reproducers, and writeups. |
| Feedback loop | Mostly one-way. | Mostly self-serve unless you find help yourself. | Direct comments on your code, primitives, and dead ends. |
| Difficulty control | Flat curriculum or playlist order. | You choose, which often means bad sequencing. | Track placement plus structured progression. |
| Why pay | Library access. | Breadth and box count. | Reviewed work and deliberate practice design. |
The founding cohort is capped because review quality matters. Seats stay limited so members actually get thoughtful feedback on their work.
Why paid
The cohort is paid because feedback, progression, and challenge sequencing are manual work.
Why paid
Seat caps exist so review quality does not collapse under too many simultaneous submissions.
Why paid
Small invite batches keep the cohort useful while new tracks and review workflows open carefully.
FAQ
fit
Hackers School is for motivated builders with C or Python basics who want serious low-level security reps. The ideal member can give 5 to 10 hours each week to solving, writing, and iterating.
fit
No. Foundations is the shallowest track, but it still assumes you can already write small scripts and work comfortably in Linux.
process
You warm up on a smaller systems challenge, work one serious lab, submit a PoC or exploit artifact, and get annotated feedback before the next level unlocks.
process
Applications run through a free Polar checkout. Fit and track placement are reviewed weekly, and accepted builders receive a separate $25/month cohort invite. First invites go out in August 2026, just after DEF CON 34, inside the 10-seat founding cohort.
This is for builders who want serious low-level practice and direct feedback. First invites go out in August 2026.