I’m Christian.

How it started

Games and computers pulled me in early, but I never settled for just playing. I wanted to see what was underneath, so I spent more time bending clients, testing limits, and figuring out how far things could be pushed than actually beating levels. That habit of poking at edges never left. It just got a name: security research.

What I do now

Penetration testing and security engineering are the core. I hunt bugs and exploits across web apps, services, networks, and software, and creative attack paths interest me far more than checklists. The last few years have also been heavy on Linux servers: building, hardening, and running my own systems for personal and private projects.

I also understand AI well, both how AI systems are built and how they break. That means using LLMs and new techniques in offensive work, and knowing where AI systems themselves go wrong. On top of that sits OSINT and opsec, finding what leaks about a target and locking down what should never leak, plus real time spent in crypto, DeFi, and privacy tech, including private work on smart contract vulnerabilities.

How I build

I still try to build most things myself, and I believe I can build most things if you give me time. Go and Rust are my picks when something needs to be fast and hard to break, Node.js when it just needs to ship. Offensive tooling is usually Python, Go, and Bash. I would rather build my own API than rent someone else's, I enjoy hardening a server as much as breaking one, and I keep learning because I want what I build to be genuinely useful and powerful. Debian and Red Hat on my servers, Parrot and Kali for testing.

I do not stick to one kind of project. I move between security tools, systems software, web apps, automation, research, and whatever else is worth building.

Where it is going

Most of my work so far has been private. That is changing. I’m moving projects into the open, partly because they are useful, partly because I want proof behind everything on this page: open source, bigger public projects, and write-ups of the things I break and build, published here instead of scattered across profiles.

Open to

Security work, engineering roles, contracts, collaborations, and unusual projects. Just hit me up anyway. If it sounds interesting, I might be interested. Contact is right below.