Auditing kernels and inspecting memory — one syscall at a time.
Mostly learning by breaking things and figuring out why.
I'm a self-taught developer focused on system security and low-level behavior.
I didn't come from a formal background in this area — most of what I know came from curiosity, reading documentation, breaking systems in VMs, and trying to understand what actually happened under the hood.
I like working close to the system boundary — where abstractions stop helping and you have to deal with memory layout, process behavior, and real execution flow.
Instead of relying on large frameworks, I prefer small and transparent tools written in C and Bash, where I can see exactly what is happening.
Projects like K-Scanner, LinSpec, S.I.R.E.N, and OpenSec come from that mindset — building simple tools to observe, validate, and question how systems behave in real conditions.
Most of what I do follows a few ideas:
- Push systems until edge cases start to show up
- Keep things minimal and inspectable
- Focus on real behavior instead of assumptions
Security, for me, isn't about running tools — it's about understanding what the system is actually doing when things start to break.
| Project | Description | Stack |
|---|---|---|
| SYNTROPY | The antithesis of digital entropy. Unified suite for forensic triage (LinSpec + K-Scanner + S.I.R.E.N). | C, Bash |
| LinSpec | Kernel hardening audit tool focused on identifying real security gaps. | C |
| K-Scanner | RWX memory detection and live process analysis for Linux. | C |
| S.I.R.E.N | Audit-aware memory acquisition and forensic triage tool. | Bash |
| K-Verify | Purple Team adversarial validation and detection gap analysis for the SYNTROPY ecosystem. | C |
| PMV | OpenBSD mitigation auditor (W^X, ASLR, pledge, unveil). | C |
- OS: OpenBSD + Arch Linux (daily drivers)
- Languages: C11, Bash
- Editor: Neovim (AstroNvim)
- Focus: Memory forensics, kernel mitigations, process behavior, exploit surfaces
Contributions are welcome. I care about simplicity, safety, and transparency — especially in low-level and memory-related code. If you have ideas, improvements, or just want to discuss something interesting, feel free to open an issue or reach out.