06 — Documentation

Bypass — honest documentation

What PC scans officially claim to detect, what bypass means in practice, and what the Rolex stack does — without promising 100% invisibility.

Ring 0 Kernel Usermode Forensics Registry Journal Event Log

Overview

PC scans (Echo, Detect, Napse, Anticheat.ac/Ocean, Nexora) are forensic tools: they read disk, registry, logs, processes, memory, and drivers.

Bypass does not mean shutting down the scanner. See Status and Honest bypass.

Honest bypass

What bypass really is

Myth Reality
“I leave zero traces forever” Every Windows action leaves some artifact
“The scanner never sees me” Scanners run as admin; existing data can be found
“CCleaner = bypass” Cleaners create their own traces
“Kernel = invisible” Kernel can filter; advanced scans hunt drivers and hooks
“Status Undetect = 100% safe” Status = internal sync label

Official scanner claims

From public sites — not internal rules.

Provider What they say Detection focus
Echo.ac “Forensic lab” · file logs (downloaded/executed/renamed/deleted) · custom strings · process scan · HWID · FiveM cheats · injected DLLs Timeline · strings · RAM · identity
Detect.ac “Residual traces and forensic artifacts” · “Anti-Forensic Detection” for cleaners/bypasses · 710+ methods · memory & process · <60s Anti-forensic · deep forensics · memory
Napse.ac Signed client · PIN · admin · 6–8 min deep scan · binary analysis · custom strings · multi-game — warn: other forensic tools before/after break diagnosis Long forensic · binary · conflict detection
Anticheat.ac Ocean: cheat injection · GTA/FiveM folder mods · unloaded DLL · render/GUI hooks · game hooking · GlobalBan patch · active spoofer (FiveM docs) Injection · files · hooks · ban evasion
NexoraScanner “BIOS injectors and UEFI cheats” · shimcache/prefetch/amcache · process · memory dump · file hash · registry · custom JS/YARA rules · 5000+ detections Firmware class · artifacts · RAM · custom rules

What the Rolex stack does

Two axes — not magic:

Usermode

Usermode work

  • Fewer files on disk (inject, do not drop .exe).
  • No cleaners / wipers before scan.
  • Pause features when scanner app runs.
  • Close helper processes.
Kernel

Kernel work

  • Filter reads from scanner PID when supported.
  • One driver load story per boot.
  • Snapshot: consistent artifacts during scan.
  • Does not erase pre-existing history.

Limits & risks

  • Old traces: may still appear.
  • New rules: undetect today ≠ tomorrow.
  • Human review: staff reads reports.
  • Live AC: separate from PC scan.
  • UEFI/BIOS: Private tier via staff.
  • Status: not a vendor certificate.
Summary

Bypass = reduce + control visibility during the scan.

CPU privilege rings

x86/x64 uses rings 0–3. Most games and scanners run in Ring 3. The OS kernel and drivers run in Ring 0.

Ring 0 — Kernel

Kernel mode can register callbacks (process, image load, registry), filter minifilter I/O, and manipulate handles/objects before usermode sees them. Rolex’s kernel module loads early (or via mapped image on advanced builds) and establishes a trust boundary between the game process and inspection tools.

Ring 3 — Usermode

The in-game menu (107+ functions), config, and injector live here. Usermode talks to the kernel component through a private channel (device object + IOCTL or shared communication buffer). Scanners without kernel access see less of some paths — but advanced scans (Detect, Nexora) also hunt drivers and hooks. Nothing is guaranteed hidden.

Rolex stack (layers)

Kernel (Ring 0)

Hooks, callbacks, memory visibility, driver hygiene.

Usermode

Menu, features, injection into FiveM / game process.

Reduce footprint

Fewer new artifacts, timing, snapshot consistency — not “erase history.”

Status sync

Internal compatibility labels on Status — not vendor certification.

Kernel bypass flow (simplified)

Typical sequence when Rolex is active and a scan starts:

01

Driver init

Kernel module registers callbacks and communication port; usermode waits for ready signal.

02

Process attach

Target game process is marked; sensitive modules are classified (hide / spoof / pass-through).

03

Scan window

When a scanner enumerates handles, drivers, or memory, kernel layer returns filtered results.

04

Cleanup pass

Transient artifacts (logs, prefetch touches) minimized per anti-forensics policy.

Bypass map

PC scanners build a timeline from many sources. Rolex aims to split work between usermode (policy, timing, game-side) and kernel (filtering what the OS records when supported). Below is the intended approach per surface — see limits for what we do not promise.

Rule of thumb

Usermode decides when and how to act (don’t touch disk, pause features, clean session). Kernel decides what survives on disk and what a scanner process can read while it runs.

Registry traces

Run · Services · MUICache · UserAssist

Windows logs program execution and configuration under HKCU/HKLM. Scanners parse UserAssist, MUICache, shellbags, recent docs, service keys, and driver service entries.

Usermode

What we do

  • Launch injector/menu without writing obvious Run keys.
  • Session-only config; no persistent “cheat” key names.
  • Defer registry-heavy installers during scan windows.
  • Coordinate with kernel before any required service registration.
Kernel

What we do

  • Filter ZwSetValueKey / enumerate for marked scanner PIDs.
  • Hide or alias driver service keys from usermode walkers.
  • Registry callback: block reads of sensitive paths in snapshot mode.
  • Private tier: deeper callback chain + shadow hive view.
registry_policy — concept
// Ring 3 — before creating a service key
if (Rolex.Policy.ScanWindowActive())
    QueueServiceInstall(AfterScan);  // no fresh traces mid-scan
else
    Rolex.Kernel.Ioctl(REGISTER_SERVICE_ALIAS, aliasName);

// Ring 0 — registry callback (simplified)
NTSTATUS OnRegNotify(..., PVOID path, ...) {
    if (SnapshotMode && IsScannerCaller() && IsSensitivePath(path))
        return STATUS_ACCESS_DENIED;
    return STATUS_SUCCESS;
}

USN journal & NTFS traces

$UsnJrnl · $LogFile · MFT

The USN journal records file create/rename/delete on NTFS volumes. Forensic tools replay it to prove a file existed even if deleted. Scanners also check $LogFile and directory timelines.

Usermode

What we do

  • Run from RAM-mapped or reused paths where policy allows.
  • Avoid burst copy/rename during active scan (Status-driven).
  • Stage updates via kernel channel instead of loose drops on disk.
Kernel

What we do

  • Minifilter on volume: mask USN records for classified paths.
  • Coalesce or delay journal writes for Rolex-owned file ops.
  • Snapshot mode: return truncated / consistent journal view to scanner PID.
  • Advanced: handle delete + recreate patterns without obvious USN spikes.
journal_filter — concept
// Ring 0 — minifilter pre-operation
FLT_PREOP_CALLBACK_STATUS PreWrite(PFLT_CALLBACK_DATA Data, ...) {
    if (IsRolexProtectedFile(Data) && ShouldMaskUsn(Data))
        SuppressUsnForThisOperation(Data);
    return FLT_PREOP_SUCCESS_WITH_CALLBACK;
}

// Ring 3 — policy
Rolex.Policy.OnScannerStart("detect.ac", () => {
    Rolex.Kernel.Ioctl(ENABLE_JOURNAL_SNAPSHOT);
});

Event logs & service traces

System · Security · SCM · ETW

Windows logs driver loads, service installs, logons, and powershell in Event Viewer channels. SCM records service start/stop. ETW providers can feed live telemetry to advanced scanners.

Usermode

What we do

  • No noisy service install/uninstall during scan window.
  • Driver load orchestrated once per boot via kernel — not repeated toggles.
  • Menu/features avoid spawning suspicious child processes while scanned.
  • ETW-aware builds reduce high-signal usermode providers.
Kernel

What we do

  • Filter event write paths for classified event IDs (tier-dependent).
  • Driver object named generically; load via approved path only.
  • Block or sanitize .evtx read from scanner process handles.
  • Hook image load notify — no duplicate “unknown driver” spam in logs.
Log source Typical scanner use Rolex layer
System — 7045 / driver Prove kernel driver load Kernel load hygiene + single boot attach
Security — 4688 Process creation audit UM: fewer spawns · K: filter enumerate
Application / PowerShell Script / tool usage UM: no helper exes during scan
ETW (Defender, etc.) Live telemetry Reduced surface + snapshot mode
service_log_policy — concept
// Ring 3
void InstallRolexDriver() {
    if (!Rolex.Kernel.AlreadyLoadedThisBoot()) {
        Rolex.Kernel.MapAndInit();  // one shot — avoids SCM churn
    }
}

// Ring 0 — open evtx for read
if (IsScannerProcess(PsGetCurrentProcess()) && IsProtectedLogPath(path))
    return STATUS_OBJECT_NAME_NOT_FOUND;

File execution traces

Prefetch · Amcache · BAM · Shimcache

Even without the USN journal, Windows keeps Prefetch (.pf), Amcache, BAM/DAM (background activity), and Shimcache evidence that an executable ran.

Usermode

What we do

  • Prefer in-process / injected path — no new random .exe per session.
  • Reuse stable launcher name in allowed directory when disk touch is required.
  • Never run “cleaner” tools during scan (creates new artifacts).
Kernel

What we do

  • Snapshot: prefetch write for protected paths redirected or skipped.
  • Timestomp avoided — consistency preferred over naive date edits.
  • Align MFT/USN/prefetch story so timeline doesn’t contradict.

Process, modules & memory

PEB · Handles · Drivers · Strings

This is what most users think of as “the cheat detected”: foreign DLL in game, suspicious thread, unknown driver, strings in memory. Kernel is primary here.

Usermode

What we do

  • Manual-map or private load into game process (no loose on-disk module).
  • Menu runs in isolated render path; strings encrypted at rest.
  • Feature pause when Status marks provider in check window.
Kernel

What we do

  • Process/module callbacks — hide from CreateToolhelp32Snapshot walkers.
  • ObRegisterCallbacks on handles (scanner can’t open game with full rights).
  • Non-paged protected regions; no plaintext signatures in readable pages.
  • Driver not listed in standard enumeration APIs during filter mode.

Unified policy — how it runs together

Status · Snapshot · Boot

One orchestrator in usermode reads Status and pushes mode to kernel. All artifact classes follow the same state machine:

A

Idle / gaming

Full features; kernel logs minimum; normal registry/file behavior.

B

Pre-scan (heuristic)

Scanner process detected → UM pauses risky ops → kernel arms snapshot.

C

Active scan

Filtered registry, journal, logs, modules; consistent “clean PC” view.

D

Post-scan

Gradual restore; no sudden artifact bursts; Status last-check updated.

orchestrator — concept
// Ring 3 — central policy engine
enum RolexMode { Idle, PreScan, Snapshot, Cooldown };

void SetMode(RolexMode m) {
    Rolex.Kernel.Ioctl(SET_MODE, m);
    switch (m) {
    case Snapshot:
        PauseMenuFeatures();
        BlockRegistryWrites();
        EnableJournalMask();
        EnableLogReadFilter();
        break;
    case Idle:
        RestoreDefaults();
        break;
    }
}

Scanners — detect vs aim

Each section: official claims → what the Rolex stack aims for (UM/K). No guarantee. Bypass map · Honest bypass · Status.

Sources (Status providers)

Based on official marketing/docs: echo.ac · detect.ac · napse.ac · anticheat.ac · nexorascanner.ac. Build sync: Status.

Provider Typical scan time Primary focus Doc section
Echo.ac ~60s File timeline · strings · HWID ↓
Detect.ac <60s Anti-forensic · 710+ methods ↓
Napse.ac 6–8 min Deep binary forensics · custom strings ↓
Anticheat.ac Seconds FiveM injection · folder mods ↓
NexoraScanner Minutes UEFI/BIOS · artifacts · YARA scripts ↓

Echo.ac

echo.ac ↗

Markets itself as a forensic lab: chronological file logs (downloaded → executed → renamed → deleted), Tool Designer + Custom String Builder (upload EXE for auto strings), process scanning, HWID / ban-evasion marks, publishable scan links, FiveM/Rust/Minecraft — ~60s scans.

File timeline Custom strings Process memory HWID FiveM cheats Injected DLLs Recycle bin 5000+ strings
What Echo scans (public) Usermode bypass Kernel bypass
File log: Downloaded → Executed → Renamed → Deleted No new executables on disk during scan; inject in-process USN journal + Prefetch/Amcache aligned timeline
Custom String Builder / uploaded EXE rules No plaintext signatures; polymorphic string table in build Scanner read of Rolex pages → sanitized (memory)
Process scan · “Injected cheat DLLs” Manual-map; pause menu/features when Echo app runs PEB/module unlink; ObRegisterCallbacks on game handle
FiveM cheat names · ghost clients · scripts Feature pause; no second cheat process Filtered module list for scanner PID only
HWID · marked banned · publish scan No third-party spoofer during check Stable HW fingerprint policy; Private tier options
Cleared recycle bin · suspicious cleanup Never “clean” during Echo — creates new story Snapshot: consistent delete/recycle narrative
IP / program usage (minimal logging per Echo) Close helper apps before scan (their recommendation) N/A — network not kernel-filtered on public stack
echo_policy — concept
// Triggered when Echo scan app is detected (~60s window)
Rolex.Status.OnProvider("echo.ac", () => {
    SetMode(Snapshot);
    BlockFileTimelineWrites();     // no new "Executed/Renamed" story
    Kernel.FilterProcessOpen(gamePid);
    Usermode.PauseHighSignalFeatures();
});

Detect.ac

detect.ac ↗

Positions as complement to live AC: residual forensic traces in <60s, 710+ detection methods, explicit focus on anti-forensic tools and bypasses that hide from normal scanners.

710+ methods Anti-forensic Memory deep-dive Process investigation Residual traces Cleaners / bypass tools
What Detect scans (public) Usermode bypass Kernel bypass
Residual forensic artifacts (not live AC) One consistent session story; no pre-scan “wipe” tools Snapshot mode on all artifact classes at once
Anti-forensic tools & bypass traces Never run CCleaner-style / journal wipers / known cleaners No contradictory USN vs Prefetch vs registry (map)
Advanced memory analysis Encrypt sensitive buffers; pause high-signal features Filter ReadProcessMemory from scanner PID to game
Process / module investigation Single inject path; no cheat .exe drops Toolhelp / NtQuery filtered via callbacks
Traces of cheats that ran earlier Stable launcher identity; no rename spam Journal mask for protected paths (journal)
Hidden drivers / kernel hooks Don’t load test drivers during scan Stealth callbacks; shadow on probe (drivers)
Cleared logs / tampered event channels One driver load per boot — no SCM on/off loop Event log read filter for scanner process
Why Detect is the hardest category

They explicitly market catching bypasses that fool other scanners. Rolex never relies on “just memory” — Detect gets the full unified policy (registry + journal + logs + files + RAM).

detect_policy — concept
Rolex.Status.OnProvider("detect.ac", () => {
    SetMode(Snapshot);
    Usermode.BlockCleanersAndWipers();      // Detect hunts these by name
    Kernel.EnableFullArtifactMask();        // journal + reg + evtx together
    Kernel.SanitizeMemoryWalk(gamePid);
});

Napse.ac

napse.ac ↗

Signed forensic client (PIN, admin): 6–8 minute deep scan per their download flow. FiveM, Rust, DayZ, RedM, Alt:V, RageMP — binary analysis + custom string configs. They warn: do not run other forensic tools before/after Napse (conflicts diagnosis).

Deep forensics Binary analysis Custom strings Admin scan Dashboard report Multi-game
What Napse scans (public) Usermode bypass Kernel bypass
Long 6–8 min artifact pass (deeper than 60s scanners) Hold Snapshot mode entire window — no mid-scan installs Sustained journal/reg mask — not just short burst
Binary / executable analysis engine Rolex build has no obvious PE metadata strings Protected memory; no dropper .exe on disk
Custom string configurations per game Encrypted + rotated string tables per update Block scanner reads of game process memory
Injected DLLs · cheat signatures in RAM Manual-map only; pause features for full 8 min PEB filter + handle ACL on FiveM PID
Anti-forensic / bypass tool traces No cleaners; no second scanner before Napse Consistent artifact story across full scan duration
Registry · USN · NTFS (implied deep pass) Defer all registry service writes until after Registry + journal filters active
Conflict with other forensic software Don’t run Echo/Detect/etc. same session — Napse flags overlap One Rolex policy — don’t mix external “clean” tools
napse_policy — concept
// Napse = long scan — extend snapshot
Rolex.Status.OnProvider("napse.ac", () => {
    SetMode(Snapshot);
    Policy.SetDurationMinutes(8);           // match their 6–8 min window
    Usermode.PauseAllRiskyFeatures();
    Kernel.EnableSustainedArtifactMask();
});

Anticheat.ac (Ocean)

anticheat.ac ↗

Ocean screenshare for FiveM (anticheat.ac/docs): direct cheat residues, generic + specific detections — injection, GTA V / FiveM / mods folder edits, unloaded DLLs, render/GUI modules, import hooking, GlobalBan patch attempts, active spoofer. Fast automated scan → dashboard verdict.

Generic injection Folder modification Unloaded module Render / GUI hook Game hooking Spoofer Skript residues Direct detections
Ocean / FiveM docs detection Usermode bypass Kernel bypass
Generic cheat injection (external to game) Manual-map into FiveM; no external injector .exe Module hidden from Ocean’s process walk
Possible loaded cheat / DLL inject (non-ReShade) Single stable module; no load/unload cycles PEB / LDR list filter for scanner PID
Folder modification — GTA · FiveM · Mods Don’t patch game folders during Ocean window Minifilter: mask USN for protected paths (journal)
Suspicious unloaded module Never inject-then-unload before screenshare No “unloaded cheat DLL” timeline spike
Generic cheat render · GUI external to game Rolex menu render isolated from Ocean-visible surfaces GPU/process read filter where applicable
Game hooking · import hooks Hooks via kernel-staged stubs, not obvious IAT Debug/register read blocked from Ocean process
Generic game cheat render (clear injection) Feature pause when Ocean downloader detected Snapshot on game memory regions
GlobalBan patching (CitizenFX ban bypass) Don’t run ban patchers — direct Ocean flag N/A — behavioral detection
Active spoofer (HWID / ban evasion) No spoofer EXE during Ocean Block known spoofer driver loads
Direct detections (Skript loader, etc.) No Skript/cheat residues on disk String scan of RAM → sanitized pages
Tampering / cheat dependencies Minimal disk footprint for dependencies Registry + prefetch consistent (files)
1

Before Ocean link

UM: close helpers · K: arm snapshot if Ocean downloader detected.

2

During ~few second scan

Filtered enumeration + clean FiveM/GTA folder view.

3

After scan

Cooldown mode — no sudden artifact burst; Status last-check updates.

NexoraScanner

nexorascanner.ac ↗

FiveM-focused automated screenshare: 5000+ detections, cheat signatures, BIOS injectors & UEFI cheats, forensic artifacts (shimcache, prefetch, amcache), built-in toolkit — process scan, memory dump, file hash, API monitoring, registry, Panda Scanner integration. Pro+: custom JS rules (yara(), shimcache(), processIDs(), fileSize()).

UEFI / BIOS Shimcache Prefetch Amcache Memory dump File hash Custom YARA/JS Modified DLLs
What Nexora scans (public) Usermode bypass Kernel bypass
Process scan · running cheats / injectors In-process Rolex; no second cheat process Filtered process/module enumeration
Memory dump · signatures in RAM Encrypted strings; feature pause on Nexora start Non-readable protected regions for scanner PID
File hash · known cheat files No Rolex files on disk with public hashes RAM-only or staged payloads via IOCTL
Shimcache · Prefetch · Amcache (artifact UI) Launch hygiene — one stable path if disk needed File traces snapshot — aligned story
Registry forensics No Run-key / service spam during scan Registry callback filter
API call monitoring Fewer suspicious WinAPI from helpers Limit visibility of hook targets to scanner
BIOS injector · UEFI cheat detection Don’t use firmware cheat tools Private tier: EFI layer — contact staff (Pricing)
“3 modified DLLs” / game file integrity Don’t patch FiveM/GTA DLLs during scan Directory notify filter for scanner reads
Custom detection scripts (Pro/Enterprise) Build-specific obfuscation per Rolex update Snapshot freezes state for script pass
Panda Scanner / third-party modules Close extra tools before Nexora (like Napse advises) Same unified mask — avoid conflicting artifacts
UM

Usermode before Nexora

Pause menu · close helpers · no BIOS/UEFI tools · no file drops.

K

Kernel during Nexora

Snapshot + artifact mask + memory sanitize + registry/journal filter.

↻

After report

Cooldown — Status page updates Nexora last-check on Status.

nexora_policy — concept
Rolex.Status.OnProvider("nexorascanner.ac", () => {
    SetMode(Snapshot);
    Usermode.PauseHighSignalFeatures();
    Kernel.EnableArtifactMask(SHIMCACHE | PREFETCH | AMCACHE | REG);
    Kernel.BlockFirmwareCheatProbes();     // BIOS/UEFI class
    Kernel.SanitizeMemoryForDump(gamePid);
});

Method catalog

Index of all methods — same data as Status.

Reduce footprint

Scanners sell anti-forensic detection. Goal: fewer new traces. See limits.

Claims: Scanner claims. Methods: Scanners.

Trace types (all scanners)

Trace type Where it lives Scanner focus Usermode (aim) Kernel (aim)
New .exe / download / execute Prefetch, Amcache, USN, Echo file log Echo, Nexora, Napse Inject in-process; no cheat .exe drop Mask USN/prefetch for protected ops
Registry Run / Service key HKLM/HKCU hives All (forensic pass) Defer install keys until after scan Reg callback filter for scanner PID
Driver load / unload Event 7045, SCM, driver list Detect, Nexora, Napse One load per boot via policy Mapped load; hide from enumeration
Cleared event log / BAM gap EVTX, BAM/DAM Detect, Nexora No cleaners — gap = flag Filter read, do not wipe logs
Journal wipe / timestomp $UsnJrnl, $SI vs $FN Detect, Nexora Never use timestomp tools Consistent MFT view
Cheat strings in RAM Process memory All + custom rules Encrypt; pause features Protect pages; filter RPM
Cleaner / bypass tool artifacts Cleaner prefetch, new gaps Detect (explicit) Blocklist: no CCleaner, journal wipers Snapshot before “fixes” create flags

Footprint policy — Ring 3

Usermode: fewer disk/registry touches — no cleaners. See Ring 3 (privilege model).

✓

Load

Manual-map into FiveM — no separate cheat.exe in Downloads.

✓

Session

Config in memory; no Run keys; no new service install mid-scan.

✗

Never

Cleaners, journal wipers, “bypass all scans” tools, second forensic scanner same day.

✓

Scan window

Pause menu; close helpers; wait for scanner policy from Status.

footprint_usermode.cpp — concept (aim, not guarantee)
// === ROLEX USERMODE: reduce new artifacts (honest goal) ===

bool RolexUsermode::LaunchFiveMStack() {
    // 1) No dropper on disk
    if (!Kernel.IsReady()) return false;
    DWORD pid = FindFiveMProcess();
    if (pid == 0) return false;

    // 2) Map payload from kernel buffer — not WriteFile("cheat.dll")
    PVOID image = Kernel.IoctlMapImage(IOCTL_ROLEX_GET_IMAGE);
  ManualMapIntoProcess(pid, image);   // no new Prefetch for "cheat.exe"

    // 3) No registry footprint for menu
    //    — config stays in encrypted heap, not RegSetValue
    return true;
}

void RolexUsermode::OnScannerDetected(const char* provider) {
    PauseAllFeatures();                  // stop hooks/strings in game
    CloseHelperProcesses();              // injectors, debug tools

    // NEVER do this — Detect/Napse/Nexora flag it:
    // RunCleaner("ccleaner"); WipeUsnJournal(); DeletePrefetch();

    Kernel.Ioctl(SET_MODE, MODE_SNAPSHOT);
}

void RolexUsermode::BeforeAnyDiskTouch() {
    if (Policy.ScanWindowActive()) {
        QueueUntilAfterScan(DiskOp);     // defer = 0 new USN/prefetch rows
        return;
    }
    DiskOp();
}

Footprint policy — Ring 0

Filter reads/writes for scanner PIDs when the build supports it. Advanced scans hunt drivers/callbacks — see Ring 0. Not a fully invisible driver guarantee.

footprint_kernel.c — concept (aim, not guarantee)
// === ROLEX KERNEL: fewer new artifacts + filtered view when possible ===

NTSTATUS RolexDriverEntry(...) {
    RegisterMinifilter(VolumeCallback);       // USN / write path
    RegisterRegistryCallback(RegCallback);
    RegisterProcessNotify(ProcCallback);
    CreateDeviceIoctl("\\Device\\RolexLink");
    return STATUS_SUCCESS;
}

// --- don't CREATE traces ---
FLT_PREOP_CALLBACK_STATUS VolumePreWrite(...) {
    if (IsRolexProtectedPath(File) && Policy.MinimizeFootprint)
        SuppressUsnRecord(Operation);        // no new journal row
    return FLT_PREOP_SUCCESS_NO_CALLBACK;
}

// --- don't LET scanner READ raw traces ---
NTSTATUS RegCallback(..., PVOID path, ...) {
    if (Policy.SnapshotMode && IsScannerProcess())
        if (IsSensitiveHivePath(path))
            return STATUS_ACCESS_DENIED;
    return STATUS_SUCCESS;
}

NTSTATUS HookNtReadVirtualMemory(...) {
    if (IsScannerCaller() && TargetIsProtectedGameProcess())
        return SanitizedRead(...);           // no cheat strings in dump
    return OriginalNtReadVirtualMemory(...);
}

// --- driver: one clean story per boot ---
VOID LoadRolexImage() {
    if (g_LoadedThisBoot) return;
    MapDriverFromSignedBuffer(...);          // not repeated SCM install/uninstall
    g_LoadedThisBoot = TRUE;
}
Provider mapping

Detect → full unified policy.
Napse → 8 min sustained mask.
Echo → journal + prefetch alignment.
Nexora → artifact bitmask + Private EFI tier.
Ocean → in-process + directory filter.

Rules checklist

Short list — details in Honest bypass.

  • Reduce footprint = fewer new artifacts — no cleaners before scan.
  • Consistency — registry, journal, logs, files, RAM: same snapshot story (unified policy).
  • Timing — pause features while scanner runs (Status).
  • Per surface — Bypass map.
  • Per scanner — Scanners.
  • Updates — provider rule changes; no pass guarantee.

Code examples

Handshake, callbacks, orchestrator. Footprint: Ring 3 policy · Ring 0 policy.

Usermode → kernel handshake

ioctl_example.c — concept
// Ring 3 — after menu loads
HANDLE h = CreateFile("\\\\.\\RolexLink", ...);
ROLEX_HANDSHAKE in = { .magic = ROLEX_MAGIC, .ver = BUILD_ID };
DeviceIoControl(h, IOCTL_ROLEX_INIT, &in, sizeof(in), &out, sizeof(out), ...);

if (out.status == STATUS_READY)
    InjectFiveMProcess(out.protected_pid);

Kernel — hide module from enumeration

callback_sketch.c — concept
// Ring 0 — simplified process notify
VOID OnProcessCreate(PEPROCESS proc, HANDLE pid, ...) {
    if (IsScannerProcess(proc))
        EnterFilterMode(pid);  // restrict what this PID can Open/Read
}

VOID OnModuleLoad(...) {
    if (IsRolexModule(base) && FilterActive())
        SkipFromPebList(...);  // usermode walker sees less
}

Anti-forensic trap — what scanners catch (do NOT do)

bad_practices.c — what gets you flagged
// Detect.ac literally markets catching these:
Run("ccleaner.exe");              // cleaner prefetch + gaps
WipeUsnJournal();                    // "anti-forensic" spike
DeletePrefetch("*.pf");             // inconsistent with Amcache
TimestompFile(path);                 // MFT $SI vs $FN — Nexora-class
LoadDriver("vulnerable.sys");     // BYOVD trail
UnloadCheatDll();                    // Ocean "suspicious unloaded module"

// Rolex: none of the above — reduce footprint + snapshot (see honest-bypass)

Forensics — scan-time snapshot (all Status providers)

orchestrator_all_scanners — concept
// Match any Status provider
const char* PROVIDERS[] = {
    "echo.ac", "detect.ac", "napse.ac",
    "anticheat.ac", "nexorascanner.ac"
};

void OnAnyScanner(const char* id) {
    Usermode.OnScannerDetected(id);      // pause, no cleaners
    Kernel.Ioctl(SET_MODE, MODE_SNAPSHOT);
    if (strcmp(id, "napse.ac") == 0)
        Policy.SetDurationMinutes(8);    // long scan
    Kernel.EnableFullArtifactMask();    // reg + journal + logs + RAM
}

Product depth

Stack depth per Rolex product. Pricing.

Tier Layers Best for
Rebirth (public) Core usermode + bypass stack Entry tier — instant checkout
Extreme (public) Usermode + kernel stack Full public stack — instant checkout
Elite / Beta / Private + slotted updates, deeper kernel Long-term / high scrutiny servers
Private 550€ EFI · Kernel · Hardware · Usermode Maximum coverage — contact staff

Setup and onboarding for slotted tiers: Contact staff on Discord.

Architecture and official scanner claims — not a pass guarantee. Terms.