explaingit

the-art-of-hacking/h4cker

📈 Trending26,414Jupyter NotebookAudience · developerComplexity · 1/5ActiveLicenseSetup · easy

TLDR

A massive curated library of cybersecurity learning resources, tools, and reference material covering ethical hacking, bug bounties, forensics, AI security, and more, organized as a navigation system for beginners to professionals.

Mindmap

mindmap
  root((h4cker))
    What it covers
      Ethical hacking
      Bug bounty hunting
      Digital forensics
      AI security
      Reverse engineering
      Application security
    How it works
      Curated links
      External resources
      Jupyter notebooks
      Cheat sheets
    Who uses it
      Security beginners
      Working professionals
      Founders building apps
      Bug bounty hunters
    Learning formats
      Tutorials
      Labs
      Writeups
      Reference material

Things people build with this

USE CASE 1

Learn how to find and report security vulnerabilities in web apps before deploying them to production.

USE CASE 2

Understand AI security risks and defenses when building machine learning features into your product.

USE CASE 3

Study ethical hacking techniques and tools to prepare for a career in cybersecurity or bug bounty hunting.

USE CASE 4

Reference quick security cheat sheets and best practices while building or auditing your application.

Tech stack

Jupyter NotebookGitHubMarkdown

Getting it running

Difficulty · easy Time to first run · 5min
Use freely for any purpose including commercial, as long as you keep the copyright notice.

In plain English

This is a massive curated library of cybersecurity learning resources, tools, and reference material maintained by Omar Santos, a well-known cybersecurity educator who has written books and created courses on ethical hacking and security. Think of it as a personally curated encyclopedia for anyone learning cybersecurity, from beginners to working professionals. The collection covers an unusually broad range of topics: ethical hacking (legally testing systems for weaknesses), bug bounty hunting (getting paid to find security flaws in companies' products), digital forensics (investigating security incidents after they happen), AI security (protecting and attacking AI systems), reverse engineering (analyzing software to understand how it works), and much more. For a founder or vibe coder, the most directly relevant sections are likely the application security resources (how to build apps that aren't vulnerable to common attacks), the AI security materials (increasingly important as everyone builds AI-powered products), and the cheat sheets in the training reference section which provide quick, practical security knowledge. The repository links out to thousands of external tools, tutorials, labs, and writeups, it's a starting point and navigation system rather than containing all the content itself. It also supplements Omar's paid books and video courses, so some sections serve as companion material to those products. Built as a GitHub repository with Jupyter notebooks for some interactive content, this is freely accessible to anyone. It's a solid first stop for a non-security-specialist who wants to understand what cybersecurity practitioners actually do and learn.

Copy-paste prompts

Prompt 1
I'm building a web app and want to understand the most common security vulnerabilities. Point me to the application security section of h4cker and explain what OWASP Top 10 means.
Prompt 2
Show me the AI security resources in h4cker and explain what adversarial attacks are and why they matter for my AI product.
Prompt 3
I want to start bug bounty hunting. What does h4cker recommend as first steps and which tools should I learn?
Prompt 4
Walk me through the ethical hacking cheat sheets in h4cker and explain how penetration testing differs from hacking.
Prompt 5
I found a security flaw in a company's website. Use h4cker's resources to explain the responsible disclosure process.
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.