★ ☆ ★   W E L C O M E   T O   M Y   H O M E P A G E   ★ ☆ ★

NULLRAKE'S PAGE

last updated: NOV 19 2026  ·  hosted on a Pentium 133  ·  28.8k friendly
  *** WELCOME 2 MY HOMEPAGE *** IF U R SEEING THIS, THE PAGE LOADED OK *** DO NOT ENTER KEYS U DONT OWN *** SIGN MY GUESTBOOK *** BEST VIEWED IN NETSCAPE NAVIGATOR 4.0 @ 800x600 *** TELL UR FRIENDS *** THIS SITE IS ALWAYS UNDER CONSTRUCTION ***
« back to the catalog
writeup: CubisVision — KeyAuth-style native auth
SOLVED native medium 2026-09-22

CubisVision — KeyAuth-style native auth

target: native x64 DLL (MSVC C++) // platform: windows

HTTP auth with an attestation challenge and a violation log. The network was not the weak point; the verdict compare was.

RESULT patched copy, 6 bytes differ, length unchanged
TECHNIQUES static analysis · Capstone disassembly · verdict compare patch · export-table preserved
PUBLISHED 2026-11-19
!! WHAT I FOUND !!
  1. Auth flow: init, license, periodic check, plus a log call that ships violations back to the auth service.
  2. Hardware fingerprint derived from the C: volume serial plus two more inputs.
  3. Verdict compare inside the module is the single point that matters; six bytes on it.
  4. All four exports still behave after patching, so the module remains droppable.
MY VERDICT:

An auth service only helps if the client trusts its answer correctly. That trust is a compare, and a compare is bytes.


« back to the catalog  |  sign my guestbook

✉ tip me (crypto) · notes & messages (SimpleX) · contact me · telegram bot · services
NETSCAPE NOW! IE 3.0 800x600 HTML 3.2
© 1997-2026 nullrake // this page is best viewed on a CRT // sign my guestbook