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
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.
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:
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.
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.
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:
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 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.
Put the layers together and the admin's view looks like this.
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.
Because server-side resources only see what the client sends, a whole category of features produces no signal at all:
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.
If you use a mod menu despite the risks, the detection model above dictates the configuration more than any feature list does.
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.
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.