- 👋 Hi, I'm @p34t1k
- 👀 I'm interested in cyber security
150+ repos accumulated from years of security research, red-team tooling, and CTF/cert prep. Everything is tagged with GitHub topics on two independent axes, classified from actual repo content (not just names), so it's actually searchable instead of just a wall of repo names.
140 forks are archived — checked commit history on every one and confirmed zero original edits from me on any of them, they're pure reference clones. Archiving is reversible (gh repo unarchive <repo>); the topic tags below still apply to archived repos too, so filtering by tag surfaces them alongside anything active. The 10 repos below in "Personal projects" are the only ones I actually wrote, and are the only ones showing as active/unarchived on the main repo list.
Nature (what kind of thing it is — exactly one per repo):
| Tag | Meaning | Count |
|---|---|---|
personal |
Something I actually wrote myself (not a fork) | 10 |
tool |
Runnable software — forked or written, does a task | 85 |
reference |
Non-executable knowledge: guides, cheatsheets, mindmaps, writeups, exam prep | 53 |
payload |
Raw exploit code / shellcode / malware samples / ransomware PoCs — handle with care | 7 |
Domain (what it's about — zero or more per repo):
| Tag | Count | Tag | Count |
|---|---|---|---|
red-team |
44 | web-security |
25 |
windows |
13 | osint |
12 |
cert-prep |
10 | hid-hacking |
9 |
evasion |
9 | mobile-security |
9 |
malware-analysis |
8 | social-engineering |
7 |
wifi-hacking |
7 | bug-bounty |
7 |
cloud-security |
7 | active-directory |
6 |
ctf |
4 | hardware-iot |
4 |
forensics |
2 | honeypot |
2 |
Going forward: every new repo (created or forked) gets tagged with one nature + relevant domain topic(s) at creation time — gh repo edit <repo> --add-topic <tag>. Keeps this list from rotting back into chaos.
- Default_Camera_Changer.sh — Default_Camera_Changer for when i need to chnage the default camera to USB so i dont have to do it manually 50 times a day for every conference call
- DigiSpark-ReverseShell — This Shell, is not the most optimized one possible. However, as I learn more I will definitely write a more powerful injection. Essentially when plugged in the DigiSpark should begin after it's natural 5 second delay(unless you have that disabled, which I recommend in wild injections). The DigiSpark then proceeds to open windows defender, as a user
- KDE-Connect-Custom-Setup
- Linkedin-Post-automation — A linkedin post automation for lazy pratik
- Web-Pentesting-Books — A collection of Web Pentesting books
- job-search
- learn-aws — Learn AWS main concepts with examples and scenarios based examples
- p34t1k — Config files for my GitHub profile.
- php-reverse-shell
- test