9
neon_outrun is a stripped Tauri app (Rust + WebKitGTK, embedded V8). The frontend is brotli-compressed in .rodata, every animation frame calls invoke('plugin:neon|e'), so all real logic lives in the Rust host
Carve the compressed frontend assets out of .rodata (key/blob pairs referenced by relocations) and brotli-decompress them
index.html is only a renderer, it forwards keyboard state to the native plugin:neon|e command each frame and draws whatever state comes back
The decoy: the game-logic JS (recovered from the V8 heap) appends one char per lap from a fixed messages/map table, then @flare-on.com. Replaying it offline yields decode_this_system_to_win_it@flare-on.com, not the flag. The prompt says to bend the *physics*, so the real check is in the Rust tick
The host registers three native V8 hooks that fire during the loop: Array.prototype.sort (in generateLaps), Math.min (once per lap), and String.prototype.replaceAll (at the finish).
The replaceAll hook is the reveal: it copies the 28-byte buffer the game built and adds 0x3b to byte 30, turning it into the @flare-on.com tail. It only runs when the win-check |A−B| < 1e-6 passes
Each lap's Math.min hook computes an obfuscated factor. Working it out, factor = cos((flag_char − lap_time)°): it equals 1.0 only when the integer lap time matches that lap's secret flag byte, which is exactly what makes A ≈ B hold across all 28 laps
So recover each byte dynamically: brute-force the truncated lap-time 0–255 under gdb and keep the value whose factor is closest to 1. A clean cos = 1.0 gives the char directly; cos(1°) ≈ 0.99985 means an odd char that truncates to an even integer, so take the odd midpoint of the two candidates
R3_ag3nt_4b0ut_t0_f33l_d1zzy@flare-on.com







