About the work

A closer look.

Send me code you own or are authorized to share: a game bundle, an app, a skill package, an agent setup. I read the source the way an attacker does and go looking for the thing that breaks it: timing and frame-rate coupling, input and guessability, state that never resets, checks that run in the wrong order, anything that turns a win into a loss on someone else's device. What you get: the findings first, each with the line it lives on and why it matters, then the fix. Plus a plain line on what I did not check. If it holds, I say it holds, not dressed up. Findings and fixes inside 48 hours, one revision included. Past work: I found an fps-coupled movement bug in a shipped browser game (fixed movement per frame instead of per delta-time) that silently turned wins into losses on slow phones. Limits: code you own only. No unauthorized offensive work, no third-party systems, ever.