Security researcher doing red-team tooling, CTF/cert prep and OSINT. Outside of that I build and ship my own Linux tools β currently a hardware control center for my own MSI laptop and a local voice assistant.
Everything else on this profile is either a small script or security-research reference material I keep around; these two are the only repos I actively ship.
|
Linux control center for MSI laptops β power modes, fan curves, charge limit, keyboard RGB, battery calibration, dGPU boot mode. Hardware support reverse-engineered myself, no reused private MSI credentials. CI across 5 distros.
|
Local, offline-first voice assistant β mic β whisper β LLM β TTS, with hands-on-the-system actions gated behind a spoken confirmation. Runs entirely on-device.
|
Public, written by me, each does one small job:
- Default_Camera_Changer.sh β swaps the default camera to USB so I don't have to do it manually before every call
- DigiSpark-ReverseShell β a basic DigiSpark HID injection payload
- php-reverse-shell β a minimal PHP reverse shell
Reference collections I maintain:
- Web-Pentesting-Books β a collection of web pentesting books
- learn-aws β AWS concepts with worked examples
A few other personal repos β job-search, Linkedin-Post-automation, KDE-Connect-Custom-Setup β are private, plus an empty test scratch repo; not listed here since there's nothing public to see.
The rest of this account is years of accumulated security-research material β red-team tooling, CTF/cert prep, reference clones. All 140 forks are archived (checked commit history on every one, confirmed zero original edits from me), kept around purely as searchable reference, not as active projects. Archiving is reversible (gh repo unarchive <repo>).
Everything is tagged with GitHub topics on two independent axes, classified from actual repo content rather than just names:
Nature β what kind of thing it is:
| Tag | Meaning | Count |
|---|---|---|
personal |
Something I actually wrote myself (not a fork) | 12 |
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 breakdown β what it's about, zero or more per repo (click to expand)
| 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.