Welcome to the C1NDR Knowledge Base — a centralized technical wiki for documenting Capture The Flag events, cybersecurity labs, tools, techniques, commands, lessons learned, and repeatable methodologies.
This wiki is designed to grow over time as new CTF events, machines, tools, tactics, and workflows are discovered. The goal is not just to record answers, but to build a reusable knowledge system that helps improve problem-solving, technical depth, and operational discipline.
This wiki will document CTF events and challenge platforms such as Hack The Box, TryHackMe, Hacker101, custom labs, private CTFs, and other training environments.
Each top-level CTF section should represent an event, platform, or training site.
Example structure:
HackTheBox
└── Machines
└── Enigma
├── Overview
├── Lessons Learned
├── Tooling Used
├── Key Findings
└── Full Solution Walkthrough
Each machine or challenge write-up should focus on the technical journey, not just the final flag or answer. The purpose is to preserve the reasoning process, commands used, mistakes made, and techniques learned.
Each technical write-up should follow a consistent format whenever possible.
Briefly describe the machine, challenge, event, or lab.
Include:
Platform or event name
Machine or challenge name
Difficulty level if known
Target operating system if known
Main attack path or learning theme
Final outcome
Summarize the most important takeaways from the challenge.
Examples:
New enumeration technique discovered
Misconfiguration identified
Tool behavior better understood
Exploit chain improved
Mistake or assumption corrected
Defensive lesson learned from the attack path
List the tools used during the challenge and describe why they were used.
Examples:
nmap — port scanning and service discovery
ffuf — web directory and parameter fuzzing
Burp Suite — web request interception and testing
sqlmap — SQL injection validation and exploitation
linpeas.sh — Linux privilege escalation enumeration
john — password hash cracking
hashcat — GPU-based cracking
netcat — reverse shell handling and network testing
Capture the important moments from the solve.
Examples:
Initial foothold
Interesting vulnerability
Unique misconfiguration
Clever bypass
Privilege escalation path
Useful command or payload
Defensive detection opportunity
Document the full process from initial recon to final compromise.
A good walkthrough should include:
Initial enumeration
Service discovery
Web or network analysis
Vulnerability discovery
Exploitation
Privilege escalation
Flags or objectives completed
Cleanup notes
Defensive lessons
Whenever possible, include commands, screenshots, payloads, errors, and explanations.
The Tools section is used to document cybersecurity tools discovered during labs, CTFs, research, and real-world learning.
Each tool page should include:
Tool name
Purpose
Common use cases
Installation notes
Basic syntax
Advanced syntax
Example commands
Cheatsheet
Useful flags
Common errors
Download or project links
Related tools
Notes from actual use
Example structure:
Tools
├── Reconnaissance
│ ├── nmap
│ ├── rustscan
│ └── amass
├── Web Testing
│ ├── Burp Suite
│ ├── ffuf
│ ├── gobuster
│ └── sqlmap
├── Exploitation
│ ├── Metasploit
│ ├── netcat
│ └── searchsploit
├── Privilege Escalation
│ ├── linpeas
│ ├── winpeas
│ └── sudo -l techniques
└── Password Attacks
├── john
├── hashcat
└── hydra
Each tool page should follow a consistent format.
Describe what the tool does and when it should be used.
Document how to install the tool on common systems.
Example:
sudo apt update
sudo apt install nmap -y
Show the basic command structure.
tool-name [options] [target]
Document commands that were useful during real labs.
nmap -sC -sV -oN scan.txt 10.10.10.10
Explain practical use cases.
Examples:
Port scanning
Service enumeration
Directory fuzzing
SQL injection testing
Hash cracking
Reverse shell handling
Privilege escalation enumeration
Maintain quick-reference commands for repeated use.
Add real observations from CTFs and labs.
Examples:
When the tool worked well
When the tool failed
Syntax mistakes to avoid
Output interpretation tips
Good follow-up commands
Include official download pages, GitHub repositories, documentation, and useful references.
Home
CTF Events & Platforms
├── HackTheBox
│ └── Machines
│ └── Enigma
├── TryHackMe
├── Hacker101
├── PicoCTF
├── CyberJew CTF
└── Custom Labs
Tools
├── Reconnaissance
├── Web Application Testing
├── Exploitation
├── Privilege Escalation
├── Password Attacks
├── Reverse Engineering
├── Forensics
├── Steganography
├── Cloud Security
├── Active Directory
└── Defensive Tools
Cheatsheets
├── Linux Commands
├── Windows Commands
├── PowerShell
├── Bash
├── SQL Injection
├── XSS
├── Reverse Shells
├── Privilege Escalation
└── Networking
Methodologies
├── External Recon
├── Web App Testing
├── Linux Privilege Escalation
├── Windows Privilege Escalation
├── Active Directory Attack Path
├── Password Cracking Workflow
└── Report Writing
Lessons Learned
├── Enumeration Lessons
├── Exploitation Lessons
├── Privilege Escalation Lessons
├── Tooling Lessons
└── Defensive Lessons
To keep the wiki useful, each page should be written with future reuse in mind.
Good pages should:
Explain what was done
Explain why it was done
Include commands that worked
Include commands that failed if the failure was useful
Capture screenshots or terminal output when helpful
Link related tools and techniques
Include lessons learned
Avoid only recording the final answer
The best write-ups should help someone understand the path, reproduce the solution, and apply the same technique in a different lab.
Use tags consistently to make pages easier to search.
Suggested tags:
ctf
hackthebox
tryhackme
hacker101
recon
enumeration
web
linux
windows
privilege-escalation
active-directory
sqli
xss
rce
lfi
hash-cracking
reverse-shell
forensics
steganography
networking
cloud
defense
lessons-learned
This wiki is not just a storage location for commands. It is a personal cybersecurity knowledge system.
Every completed CTF, failed attempt, useful tool, strange error, and hard-earned lesson should improve the next engagement.
The goal is simple:
Build a repeatable process.
Document the process.
Improve the process.
Reuse the process.
Recommended starting pages:
HackTheBox
Tools
Cheatsheets
Methodologies
Lessons Learned
Begin by creating the first CTF event page, then add individual machines or challenges underneath it.
For example:
HackTheBox
└── Machines
└── Enigma
Each completed machine should become another reusable technical reference.