Rust is a brutal survival game where everything you build can be lost — and that high-stakes design makes cheating, and anti-cheat, a central part of its story.
Easy Anti-Cheat protects Rust
Rust is protected by Easy Anti-Cheat (EAC), the widely licensed system owned by Epic Games. EAC runs partly in kernel mode alongside the game, checking memory integrity, scanning for known cheats and watching for injected code.
Facepunch enforces on top
EAC handles detection, but Facepunch Studios — Rust's developer — sets the enforcement policy. Facepunch is known for taking cheating seriously, running ban waves and treating confirmed cheating as permanent. Bans are also tracked on the player's record across the game.
How bans escalate to hardware
Most Rust bans are account-level, but serious or repeated cheating can escalate. When enforcement reaches the hardware level, EAC records identifiers from the physical PC — disk serials, MAC addresses, the machine GUID, and firmware values such as the SMBIOS UUID. A new account on a banned machine can be caught. Software-level identifiers can be changed; firmware-resident ones cannot be rewritten by ordinary software.
The wipe cycle changes the rhythm
Rust servers wipe regularly, resetting the world. Wipes do not reset bans — a banned account stays banned across every wipe — but the constant fresh starts mean cheaters are a recurring topic for the community, and ban waves are often discussed around wipe schedules.
The takeaway
Rust pairs EAC detection with Facepunch's strict policy. The realistic summary: account bans are routine, hardware bans are reserved for serious cases, and a wipe never washes a ban away — the record follows the account, and a firmware-anchored ban follows the machine.