Personal CTF and security-research workspace with two distinct parts:
script/contains local helper scripts, exploit templates, and notes.- the rest of the repo is mostly vendored reference material and submodules.
This is not a single packaged application. Treat it as a toolbox repo.
Clone with submodules if you want the full reference set:
git clone --recurse-submodules <repo-url>
cd toolIf the repo is already cloned:
git submodule update --init --recursiveSet up the local Python environment for script/:
python3 -m venv script/.venv
source script/.venv/bin/activate
pip install -r script/requirements.txtMost custom scripts are then run directly:
python3 script/<category>/<name>.pyExamples:
python3 script/crypto/xor_cipher_tool.py
python3 script/net/scapy/scapy_pcap_analyzer.py
python3 script/pwn/templates/pwntools_example.py| Path | Purpose |
|---|---|
script/crypto |
crypto helpers, CTF solvers, encoders/decoders |
script/net |
packet tooling, Scapy experiments, PCAP analysis |
script/pwn |
pwntools exploits, shellcode work, templates |
script/reverse |
reverse-engineering helpers, angr/r2/cIMG scripts |
script/forensics |
small forensic utilities |
script/web |
HTTP, session, SQLi, and web exploitation helpers |
script/utils |
general-purpose utility scripts |
script/post_exp |
post-exploitation binaries and helpers |
script/shellcode |
assembly payloads and generated shellcode artifacts |
script/cheat_sheets |
notes and quick references |
| Path | Purpose |
|---|---|
dict/ |
wordlists and password dictionaries |
web/ |
third-party exploitation references and offensive tooling |
reverse/ |
reverse-engineering tools, themes, and integrations |
forensis/ |
forensic signatures, patterns, and formats |
misc/ |
assorted utilities, magic signatures, and steg tooling |
The repo tracks a large number of third-party resources as submodules, including:
dict/SecListsweb/PayloadsAllTheThingsweb/PEASS-ngweb/hacktricksweb/GTFOBins.github.ioreverse/dnSpyExforensis/ImHex-Patterns
Do not assume those directories are maintained locally. Check git submodule status before editing them.
script/requirements.txtis the closest thing to a project dependency manifest.script/.venv/may exist locally, but it is ignored by git and should be treated as disposable.- Some scripts contain hard-coded local paths, challenge-specific payloads, or one-off exploit logic. Verify inputs before reuse.
- The top-level repo can be dirty even when your local script changes are clean because submodules track their own state independently.
Useful local notes in this repo: