+-----------------------------------------------+
| [ PLAYER CARD ] |
+-----------------------------------------------+
| IGN R0x7e |
| CLASS Game Security Engineer |
| LEVEL 01 - rookie, still grinding |
| ORIGIN B.Eng. Computer Science, Jun 2025 |
| FOCUS Trojan analysis / Anti-Cheat |
| DIRECTION Fair play & security defense |
| STATUS reading binaries instead of playing |
+-----------------------------------------------+
Game security engineer — level 1, still grinding.
Computer Science, class of June 2025. No grand career story yet: I'm at the stage where I've finally figured out what I want to spend my time on — keeping games fair, and defending the players who just want a clean match.
The direction I care about is fair play and security defense, not offense for its own sake. So these days I spend more time reading binaries than playing them: taking trojans apart, watching how cheats talk to their servers, and poking at the assumptions game clients make that they really shouldn't.
Not an expert. Just stubborn, curious, and taking notes in public. Weird sample, nasty cheat, or a writeup I should read — I'm listening.
| 🦠 Trojan & Malware Analysis | 🛡️ Anti-Cheat / Cheat Research | 🎯 Fair Play & Defense |
|---|---|---|
| Static triage first, always. PE headers, sections, imports, entropy, strings — then unpacking and rebuilding what the sample actually does. Rule #1: never run a sample outside an isolated VM. Ever. |
How cheats actually get in: memory reads/writes, DLL injection, hooking, driver-level games — and what all of it looks like from the detection side. Still on the reading-heavy end of this curve. |
The goal behind the technique: a match where skill is the only variable. Client-side authority, unsigned data, plaintext protocols — the boring-but-fatal stuff a motivated player will eventually notice. |
The long game: go deep on game security defense — make cheating expensive, keep matches honest, and protect the players who only ever wanted a fair fight.
I'd rather spend my years building the wall than only studying the holes.
| Project | What it is |
|---|---|
LearnMaliciouCode · C++ |
My malware lab notebook — hand-written samples and notes covering the classic malicious code patterns, one technique at a time. |
SimplePacker · C++ |
A minimal PE packer. Built purely to understand what packers do to a binary — from the packer's side of the table. |
SearchCodeCaving · C++ |
Scanner for code caves in PE files. Started as an excuse to learn PE layout, accidentally became a small tool. |
Argus · Python |
AI-driven multi-agent system for SRC vulnerability hunting. My most-starred repo, and the reason I read so many stack traces. |
JavaCodeAudit · Java |
Code audit notes and practice targets — where I learned that reading code is a skill of its own. |


