How FiveM Anti-Cheat Works and What Admins Actually See

FiveM anti-cheat is Cfx.re's client-side global anti-cheat plus Lua resources each server installs. This guide explains what Badger, Sonoran tooling and screenshot resources observe, what admins see when they investigate, and what stays invisible.

9 min read Updated November 9, 2026 By VOIDEX

Complete FiveM RP menu - aimbot, ESP, magic bullet & more

  • FiveM anti-cheat is two layers: Cfx.re's global anti-cheat inside the client, and Lua or JavaScript resources each server installs.
  • Server-side resources never see your PC; they see events, positions, health, entities and chat your client sends.
  • Badger-Anticheat watches noclip, spectating, fake chat, spawned peds and blacklisted props and events, then bans by configurable rules.
  • Admins can request a screenshot of your game render through screenshot-basic and read event logs sent to Discord webhooks.
  • ESP and other read-only features leave no server trace; spawners and money events are logged with your source ID.
  • How does anti-cheat work on FiveM?

    Anti-cheat on FiveM is two separate systems. The first is Cfx.re's own anti-cheat, built into the FiveM client, which looks for external programs injecting into the game and issues global bans. The second is whatever server-side resources a given server installs: Lua or JavaScript scripts such as Badger-Anticheat that run inside the server runtime and judge players by what their clients send. Neither is a kernel driver. Nothing on FiveM scans your memory or process list the way Easy Anti-Cheat or BattlEye do in Rust or Siege.

    The client-side layer targets the cheat program. The server-side layer targets consequences: an impossible position, an event fired with the wrong arguments, a prop that should not exist. A third layer, human admins with spectate, logs and screenshots, does most of the actual banning on roleplay servers.

    Knowing what each layer observes tells you which mod menu features are effectively invisible and which are logged the moment you touch them. The kernel-level cheats explainer is a useful contrast.

    What Cfx.re's built-in anti-cheat does

    The FiveM client ships with Cfx.re's global anti-cheat. The official Community Server Ban FAQ describes it as an automated system that "detects the use of violative external programs that attempt to inject information into the FiveM or RedM game clients". On detection, the linked Cfx.re account is banned from every FiveM and RedM server for a duration shown when the player tries to join.

    Three details from the FAQ matter for anyone weighing a mod menu:

  • Bans are account-level and platform-wide, not per server. A server owner cannot issue or lift one.
  • Cfx.re says the system is tested to keep false positives limited, warns that unrelated outside applications can interfere, and offers an appeal form.
  • Cfx.re invites players to submit cheats they believe are undetected, with files and licences, so coverage grows from community reports.
  • Separately, pure mode gives servers a client-file integrity check. The June 2022 community update introduced sv_pureLevel 1 (blocks modified client files except common audio and known graphics mods) and sv_pureLevel 2 (blocks all modified files). It stops texture and model edits; it is not a behavioural anti-cheat and does not inspect running programs.

    How server-side anti-cheat resources work

    A server-side anti-cheat on FiveM is an ordinary resource: Lua, JavaScript or C# running in the server's CitizenFX runtime. It has access to server natives and to every event the clients send, and nothing else. Cfx.re's server security guide frames the problem these resources address: "cheats can allow the client to trigger events in any context", so server handlers must validate position, money, inventory, permissions and state bags rather than trusting arguments.

    The signals a server-side resource can work from are limited and specific.

    Signal Where the server gets it What it reveals

    Event triggers Every TriggerServerEvent arrives with a source ID and arguments Blacklisted or malformed events, money and item exploits

    Position and health Networked each tick for every player ped Noclip, speed hacks, teleports, god mode

    Entity creation OneSync attributes vehicles, peds and props to the creating client Spawners, blacklisted props, ped floods

    Weapons and ammo Networked weapon state Weapon spawns, infinite ammo

    Chat and commands Chat resource and command handlers Fake messages, admin commands from non-admins

    Resource list Client reports which resources are running Unauthorised resources injected on the client

    Everything in that table is inference. A resource cannot see the menu, only what the menu causes the client to send. The server-side anti-cheat explainer calls this hard to bypass and easy to avoid: you cannot hide an event you fire, but you can choose not to fire it.

    What Badger-Anticheat watches and how it bans

    Badger-Anticheat is one of the most widely installed free server-side anti-cheats, and its documentation is a clear picture of what this class of tool does. Its listed detections are:

  • Noclip, counted against a configurable trigger threshold (NoClipTriggerCount, default 3) before action.
  • Spectating other players, which legitimate players cannot do.
  • Fake chat messages sent as another player.
  • Spawned peds, with a whitelist for models the server uses legitimately.
  • Blacklisted props, from a long list of large or disruptive objects.
  • Blacklisted events, including common ESX, admin menu, bank and paycheck events, plus event names used by known menus.
  • Optional modules for speed hacks, invincibility, infinite ammo, removing or giving other players weapons, cancelling animations, and a ModMenuChecks scan of resources for injected variables and functions on its detection list.
  • Each component has a separate ban toggle. By default spectating, fake messages, blacklisted events and unauthorised commands ban; noclip only kicks. Detections post to a Discord webhook, the ban message tells the player what caught them, and staff with the Anticheat.Bypass permission are exempt.

    Two limits: the docs note prop scans can flag an innocent player when a cheater spawns an object on them, and nothing in the list touches ESP, aim features or anything that stays on the client.

    Sonoran, screenshots and other admin tooling

    Sonoran Software is best known for Sonoran CAD and Sonoran CMS: dispatch, records, community management and admin panels with a FiveM in-game integration resource. For catching cheaters it is administrative tooling, not a detection engine: identity mapping between in-game players and community accounts, logging, and bodycam-style footage tied to incidents so a report can be checked against evidence. If a seller claims a menu is "undetected on Sonoran", ask what they think Sonoran is detecting.

    Screenshots are a more direct tool. Cfx.re's screenshot-basic resource lets the server request a capture of a player's game render target, encode it as JPG, PNG or WebP, and upload it. Admin menus wrap this in one command. What appears in that image depends on how a menu draws: anything rendered through the game's own drawing natives or DUI is part of the render target and shows up; a separate overlay window on top of the game typically does not. The menu's interface itself is usually drawn in-game, which is why experienced users close it rather than leave it open.

    Other common tooling includes event loggers that post flagged triggers to Discord, client replays where the server allows them, and resource-list checks that compare what your client reports running against what the server started.

    What an admin actually sees when they investigate you

    Put the layers together and the admin's view looks like this.

  • 1 A report or a webhook alert naming your server ID, with the event or behaviour that tripped it.
  • 2 Your identifiers: Rockstar licence, Discord ID, Steam ID where linked, and IP. These are what bans attach to and what shared ban lists exchange.
  • 3 Spectate. The admin's camera follows your ped. They see where you go, what you shoot, what you drive and how fast you move. They do not see your screen, your menu or any overlay.
  • 4 Logs. Framework and anti-cheat logs show events you fired with arguments: an item name and count, a bank amount, a vehicle model. Position histories reveal teleports.
  • 5 A screenshot, if the server runs a capture resource, showing the game render and anything drawn into it.
  • 6 Entity ownership. Any vehicle, ped or prop your client created is attributed to you.
  • What they cannot see is equally concrete: your processes, memory, files, or anything rendered outside the game frame. Evidence for ESP is therefore circumstantial, which is why most ESP bans on roleplay servers come from behaviour. The RP server cheating guide covers the tells admins look for.

    What FiveM anti-cheat cannot detect, and why that is not safety

    Because server-side resources only see what the client sends, a whole category of features produces no signal at all:

  • ESP and overlays. Reading networked positions and drawing them is local. No event, no entity, no position change.
  • Client-side visual changes. Field of view, removal of weather effects, crosshairs.
  • Information reading. Player lists, inventories exposed to the client, vehicle health.
  • A second category produces only statistical signal. Silent aim and magic bullet alter where shots land, but the server receives a normal damage event, so detection comes from hit rates and admin review.

    A third category is logged on first use: spawners, money and item events, teleports, god mode under fire, speed changes. The vehicle and weapon spawner guide explains why these are the features that end accounts.

    None of this makes the first category safe. Cfx.re's client-side anti-cheat targets the program, not the feature, and a global ban removes the account regardless of what you were doing with the menu.

    Treat invisibility to the server as one factor among three, and any account you connect with as one you can lose.

    How this shapes which features you run

    If you use a mod menu despite the risks, the detection model above dictates the configuration more than any feature list does.

  • Keep to read-only features on roleplay servers. Every server-visible action is a log entry an admin will eventually read.
  • Prefer menus whose modules toggle independently and save per-server configs, so a deathmatch setup never loads on a whitelisted city.
  • Use disable-if-spectated and safe unload where offered. The first removes behaviour while staff watch; the second ensures nothing remains hooked after you close the menu.
  • Close the menu interface during play so a requested screenshot shows an ordinary frame.
  • Read the server's rules and anti-cheat announcements. Many publish exactly which events and props they blacklist.
  • As an example of the toggles involved, the Ambani build sold by VOIDEX exposes stealth mode, disable-if-spectated, an input blocker and safe unload alongside independent switches for each of its modules. The companion guide on how FiveM mod menus work and how to judge one sets out the questions to ask any seller before paying.

    Is FiveM anti-cheat kernel-level like Easy Anti-Cheat or BattlEye?

    No. FiveM has two layers and neither is a kernel driver. Cfx.re's global anti-cheat runs inside the FiveM client and looks for external programs injecting into the game. Server-side anti-cheats such as Badger are Lua or JavaScript resources that run on the server and only see events, positions, entities and chat sent by your client.

    Can a FiveM server see what programs I have running?

    A server-side resource cannot. It receives only what your client sends: event triggers, position and health, entity creation, weapon state, chat and the list of resources your client reports. Cfx.re's own client-side anti-cheat is the component that inspects for injected programs, and it reports to Cfx.re rather than to the server you are on.

    What does Badger-Anticheat detect?

    Its documentation lists noclip, spectating, fake chat messages, spawned peds, blacklisted props and blacklisted events, with optional modules for speed hacks, invincibility, infinite ammo and injected code in resources. Each component can kick or ban separately and posts detections to a Discord webhook. It does not detect ESP or any feature that stays on your client.

    Can admins screenshot my screen on FiveM?

    They can request a capture of your game render target through resources such as screenshot-basic, which encodes the frame and uploads it to the server. Anything drawn through the game's own rendering, including most menu interfaces, appears in that image. A separate overlay window on top of the game typically does not, and the resource cannot capture your desktop.

    Does ESP get detected on FiveM?

    Not by server-side anti-cheat, because reading positions and drawing them sends nothing to the server. It can still be caught two other ways: Cfx.re's client-side anti-cheat targeting the program itself, and admins spectating behaviour such as tracking players through walls. A global ban removes the account regardless of which feature you were using.

  • Cfx.re Support: FiveM/RedM Community Server Ban FAQ
  • Cfx.re Documentation: Secure Your Events (server security)
  • citizenfx/screenshot-basic on GitHub
  • Complete FiveM RP menu - aimbot, ESP, magic bullet & more. Undetected on FiveM AC. From $9.99.

    How FiveM Mod Menus Work and How to Judge One

    A FiveM mod menu runs its own code inside the client to call natives and fire server events. This guide explains what each feature exposes to the server, the three detection layers, and seven criteria to judge a menu.

    How Do FiveM Roleplay Servers Detect and Ban Cheaters?

    On a whitelisted roleplay server the ban comes from a staff member, not an automated scan. This guide covers the rules, the identifiers a whitelist checks, how staff investigate reports and what you lose when banned.

    What Is Server-Side Anti-Cheat and What Can It Detect?

    Server-side anti-cheat runs on the publisher's servers and judges the data your client sends: shots, movement and statistics. You cannot disable it, so the only lever you hold is how your play looks.

    How Do FiveM Vehicle and Weapon Spawners Work?

    A spawner calls the same creation natives a server script uses, but from your client. Under OneSync the server registers every vehicle and can compare every weapon with your inventory, which is why spawns fail on well-run servers.