Auditing kernels and inspecting memory — one syscall at a time.
I focus on working close to the system boundary — where operating systems actually behave, fail, and expose assumptions.
I avoid unnecessary abstractions and prefer understanding what happens underneath: memory layout, process behavior, and how the system enforces (or fails to enforce) its own protections.
Projects like K-Scanner and OpenSec come from this mindset — building small, transparent tools to observe and validate system behavior without hidden layers.
Most of my work follows a few core principles:
- Push systems to their limits: stress memory layouts and process behavior until edge cases appear.
- Keep it minimal and transparent: small tools written in C and Bash.
- Focus on what matters: syscalls, memory management, and real exposure points.
Security is not about running tools — it’s about understanding how systems actually behave under pressure.
Interested in system security, low-level internals, or these projects? Feel free to reach out — always open to a good conversation.
Independent projects focused on system behavior, memory analysis, and kernel-level security.
| Project | Description | Stack |
|---|---|---|
| LinSpec | Forensic kernel hardening audit tool for identifying defensive vulnerabilities. | C |
| K-Scanner | RWX memory region detection and analysis tool for Linux process auditing. | C |
| S.I.R.E.N | Interactive system triage tool for live forensic analysis and auditing. | Bash |
| OpenSec | OpenBSD mitigation auditor (W^X, ASLR, pledge, unveil) at process level. | C |
Daily tools and environment used for system development and security research.
- 🖥️ Core OS: OpenBSD & Arch Linux
- 💻 Languages: C11, Bash
- ⌨️ Editor: Neovim (AstroNvim)
- 🔍 Focus: Memory Forensics, Kernel Mitigations, Process Behavior & Exploit Surface Analysis
Different systems reflect different design philosophies — from minimalism to security hardening.
Selected resources for studying system security, kernel internals, and real-world exploitation.
Understanding memory is fundamental to understanding system behavior — from virtual memory to real-world exploitation.
Contributions are welcome. I value simplicity, safety, and transparency — especially in memory-related and low-level code. If you have ideas, improvements, or find something interesting, feel free to open an issue or reach out.