Rust HWID Spoofer — EAC & Server Unban.
Rust bans you twice: EAC stamps the whole machine out of Facepunch's game servers, and every community server you've played on keeps its own HWID ban list. Edgey rewrites the identifiers both layers read, so one spoof clears the global EAC lockout and every pop-up community ban in the same pass.
The right plan for Rust
Permanent Spoofer
Rust runs on EasyAntiCheat and samples your SMBIOS, disk, MAC and NIC fingerprints — no TPM dependency. The Permanent driver rewrites all of them in kernel mode. Because Facepunch's community server plugins (RustAdmin, Battlemetrics, Rustbanned) hash from the same set of identifiers, one spoof wipes global and per-server bans at the same time.
- SMBIOS, disk serial, MAC and IPv4 / IPv6 randomized every spoof.
- Clears both EAC global ban and Facepunch community-server HWID bans.
- Includes Battlemetrics / Rustbanned-matching patches, pushed with every build.
Beating EAC on Rust
Two ban layers, one spoof
Rust's EAC build is tuned harder than Fortnite's — Facepunch sends more identifier samples at every match start and does a second hardware pull mid-session. On top of that, popular community servers run Battlemetrics, RustAdmin and Rustbanned plugins that keep their own HWID lists derived from the EAC-reported identifiers. A global EAC ban locks you out of official servers, but even if that's cleared, every community server you played on keeps its own ban cache for months. Edgey's Permanent driver rewrites the SMBIOS, disk, MAC and NIC values below EAC's kernel layer before Rust launches, so EAC reports a new box and every community plugin hashing those same values sees a different signature. One spoof. Both layers cleared. We push a maintenance build within 12 hours of every EAC signature refresh — see the public changelog.
Rust is the one game where community-server bans hurt as much as the official EAC ban. The Permanent spoof breaks both at the same time because they fingerprint the exact same identifiers. If your server runs a custom plugin we haven't profiled, open a ticket — we'll scope it in a build within 48 hours, free.
Will I get banned again?
Does the spoofer clear Battlemetrics and community-server bans too?
Yes — that's the whole point of the Rust-specific build. Battlemetrics, RustAdmin, Rustbanned and the admin plugins used on big communities (Rustopia, Rustoria, Reddit Vanilla) all hash the same identifiers EAC reports, because the plugin is given its data by EAC rather than reading hardware directly. When the Permanent driver rewrites SMBIOS, disk and MAC values beneath EAC, every downstream plugin sees a different box. One spoof clears the official EAC lockout and every community-server HWID ban in your history in the same pass.
Will my Steam account also need to be new?
Depends on the ban type. A pure EAC global ban is attached to the Steam account AND the hardware fingerprint — Facepunch requires both to clear, so yes, a new Steam account is part of the fix (buy Rust on it). A VAC-less community server ban is HWID-only, and the spoof alone is enough — your existing Steam account still works, you just need the new hardware signature. We'll ask which case you're in during the pre-sale ticket and tell you exactly what you need.
Can I server-hop safely after spoofing?
Yes — a Permanent spoof lasts across sessions until you decide to re-roll, so you can play Rust across any mix of official and community servers on the same identifiers for as long as you want. If a specific server catches up to you later and HWID-bans the new fingerprint, you re-spoof (one-time plan = buy another spoof, Lifetime = free re-roll). Most Lifetime customers re-spoof two or three times a year, usually before a big community wipe.
8,247+ Rust & EAC vouches
Rust vouches are heavy on screenshots — Battlemetrics ban lifts, community-server rejoins, fresh EAC statuses. Read exactly what landed people back on the server list.
HWID & server-banned on Rust?
Open a Discord ticket with the server name and the ban reason — we'll confirm whether a Permanent spoof clears your specific community-server list or you need a plugin-specific build first.