Skip to content
Commitpedia
Log in Join & edit

HackTricks: a community wiki of security notes

A large, continuously updated wiki of security study notes, organised like a textbook and published in GitBook style, used for learning, CTF practice and assessments carried out with permission.

Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?

Edit history of HackTricks: a community wiki of security notes: 1 recorded edit
Edit history · 1 edit
Type
Repo
Edits
1
Editors
1
First issued
15 Oct 2026
Last edit
15 Oct 2026
Source
HackTricks-wiki/hacktricks

HackTricks-wiki/hacktricks

Stars
12.6k
Forks
3.2k
Language
JavaScript
Last push
15 Oct 2026

On GitHub: Welcome to the page where you will find each trick/technique/whatever I have learnt in CTFs, real life apps, and reading researches and news.

Open on GitHub

HackTricks (about 12,500 stars on GitHub) began in 2019 as the personal notes of Carlos Polop, who collected what he learned while studying for certifications and playing CTFs. It grew into one of the largest community security wikis and is now maintained by the HackTricks-wiki organisation with many contributors. The repository holds the Markdown source of the book; the rendered version is published at book.hacktricks.wiki with a sidebar, search and translations into several languages. A sister project, HackTricks Cloud, covers cloud platforms in the same style.

What it contains and how it is organised

The wiki is organised like a reference book. Top-level parts cover general methodology, operating-system internals for Linux, Windows and macOS, network services by port, web applications, mobile platforms, cryptography and reversing, and physical and hardware topics. Each page is a working note rather than a polished essay: short, dense, with links to the original research it summarises. The project uses a GitBook-style layout (a SUMMARY.md table of contents that maps to the directory tree), so the GitHub view and the website have the same structure.

Who it is for

  • Students preparing for practical security certifications, who use it as a companion to lab exercises.
  • CTF players and people learning on platforms such as Hack The Box and TryHackMe.
  • Penetration testers on authorised engagements, as a memory aid during an assessment.
  • Defenders and administrators who want to understand which configurations are routinely abused so they can harden their own systems; many pages describe the weakness and the fix side by side.

How to browse it

The website is the intended reading experience; use its search or start from the methodology pages and follow the sidebar. To read offline, clone the repository and open the Markdown files in any editor, or build it locally with the tooling described in the repository README. Contributions are accepted through pull requests, and the maintainers ask that new material cite its sources.

Credit

HackTricks was created by Carlos Polop and is maintained by the HackTricks-wiki team and contributors. The content is published under a Creative Commons Attribution-NonCommercial 4.0 licence; check the licence page in the repository for the current terms before reusing material.

Use it responsibly

Material of this kind is meant for systems you own or have written permission to test, for bug bounty programmes within their published scope, and for training labs and capture-the-flag (CTF) exercises. Unauthorised testing of other people’s systems is illegal in most countries, regardless of intent, and the maintainers of these projects say so in their own terms. Defenders can use the same material to check their own environments and to understand what their detection rules should catch.

Did this work for you?

No votes yet. Be the first.

If it did not work, the report form below tells the editors what went wrong.

See also

  • 0431 What is a detection rule? Sigma explained for beginners A detection rule describes one kind of suspicious activity in logs. Sigma is the shared, tool-independent way to write such rules, so… Beginner · Explains an idea · Any system Article Alerting & dashboards · Security resources & detection 15 Oct 2026
  • 0432 Try Sigma rules against your own logs Install the sigma-cli converter, take a rule from the public SigmaHQ library, convert it into a query for a log tool you… Intermediate · Step by step · Linux, macOS Article Logs · Security resources & detection 15 Oct 2026
  • 0433 What is an awesome list? Awesome lists are hand-curated link collections on GitHub, one per subject, that follow a shared convention. How they work, how to tell… Beginner · Explains an idea · Any system Article Security resources & detection 15 Oct 2026
  • 0454 Scan your own code and containers in CI: Gitleaks, Semgrep and Trivy Set up a GitHub Actions workflow that runs Gitleaks, Semgrep and Trivy on every push of your own project, learn what each… Intermediate · Step by step · Any system Article Pipelines, runners & hooks · Security testing & CTF 15 Oct 2026
  • 0455 Which security tool does what? A map for beginners A beginner's map of open source security tool families: vulnerability scanners, secret detection, static analysis, host audits, web application testing, network inventory… Beginner · Explains an idea · Any system Article Security resources & detection · Server hardening 15 Oct 2026

History

Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.

  1. Dominik +2,880 chars

Report a problem

Something wrong, unsafe or copied? Tell the editors.
What is wrong?