Security Model

Riveon is built with "Zero Trust" principles. We assume the client environment is compromised and hostile.

XOR Obfuscation & Dynamic Loading

The detection code is never saved to the player's disk. When a player connects:

  1. The `loader.lua` script requests a unique payload from the Riveon API.
  2. The API generates a custom bundle encrypted with a session-specific XOR key.
  3. The client receives the payload and decrypts it directly into memory.
  4. Once executed, the raw strings are garbage collected, leaving minimal traces for dumpers.

RAM-Only Execution

Traditional anti-cheats are often "dumped" by reading the resource files. Riveon's core logic resides only in RAM. Even if a cheater manages to dump the memory, the variable names and control flow are heavily obfuscated.

Anti-Tamper Mechanisms

If the client stops sending telemetry (Heartbeat failure) or if the telemetry data is inconsistent (e.g., claiming to be on the ground while Z-coord is sky-high), the server automatically flags the user for "Tampering".