Building systems that resist attacks by first understanding how they happen.
I am a computer science (datamatiker) student at Dania Erhvervsakademi with an interest in IT security and backend development. My projects sit at the intersection of understanding how systems fail and building ones that resist it.
When I am not breaking things intentionally, I am working on projects that demonstrate both offensive awareness and defensive craftsmanship. I am currently open to internships and interesting problems.
My first coding language, the one I have by far the most experience with, and therefore forms the base for most of my work.
Designing and querying relational databases. Learning schema design, parameterized queries to prevent SQL injection, and Supabase's managed Postgres environment.
Daily driver on Fedora. Comfortable in the terminal, though with a preference for Plasma over GNOME — file system navigation, process management, networking tools, and setting up development environments from scratch.
Used in university coursework and for security tooling — scripting network scanners, automating enumeration tasks, and cracking weak LCG-based password generators.
Using Git for version control on all projects. Comfortable with branching, committing with intent, and maintaining a clean enough history.
Building the backend for this portfolio — REST API routes, JWT auth middleware, rate limiting, and database integration with PostgreSQL via Supabase.
Implementing a full auth system with bcrypt password hashing, JWT session tokens stored in httpOnly cookies, TOTP-based MFA via speakeasy, and facial recognition as a third factor.
Been learning TCP/IP fundamentals, port scanning, BPF filters, and network-level attacks through hands-on pentest work.
Still learning, however i have completed a full pentest engagement covering SQL injection, privilege escalation, buffer overflows, and custom exploit development. Documented findings in a report.