Marvel Rivals Anti-Cheat Explained: How NEAC Works and What Actually Gets Players Banned

Marvel Rivals runs NetEase’s own anti-cheat on PC, and NetEase bans cheaters in public waves. That is the short answer to “marvel rivals anti cheat”. The longer answer matters more, because this game has something most shooters do not: a replay system that lets the team you just beat rewind the match and watch exactly what your crosshair did. That one feature changes what actually gets people banned.

The Marvel Rivals anti-cheat on PC: NEAC on Steam and Epic

On PC, Marvel Rivals ships with NEAC, the anti-cheat NetEase built and maintains itself. You will see it listed as Neac Protect in Task Manager and the install folder. It is not a licensed product like Easy Anti-Cheat or BattlEye, so NetEase decides what it looks for and when it updates, and those updates do not always line up with game patches. Steam and Epic run the identical client, and the game will not enter a match without the driver running.

NEAC is a kernel-level driver. In plain terms, it runs at the same depth as your graphics and network drivers, so it can see every process, driver and module on the machine rather than just what happens inside the game window. If it recognises something sitting in memory, that is enough.

Consoles are different. PlayStation 5 and Xbox Series are closed platforms, so there is no NEAC driver and no real software cheat scene, just modified controllers and the odd exploit. What they do have is cross-play with PC in Quick Play and the casual modes, so a console Strategist can still end up healing behind a PC Hela who never misses. Competitive is the exception: as the game is set up now, console ranked queues are kept apart from PC ranked. The server checks and the report system cover every platform.

The three layers of detection, in plain terms

Three separate systems can end an account. Most people only think about the first one and get caught by the second or third.

Layer one: the NEAC driver looks at your machine

This is the piece that loads with the game. It checks the game’s files for tampering, watches for code being injected into the process, scans memory for known cheat signatures, and flags debuggers and hooking tools. It also phones home, so a signature NetEase adds today applies the next time you launch.

What it does not do is understand Marvel Rivals. It has no idea what a Team-Up is and cannot tell you are seeing Psylocke’s outline through a wall. It only knows what software is running and whether it matches something seen before. Our page on how cheat detection works covers this layer in more depth.

Layer two: the server looks at what your account did

Marvel Rivals is server-authoritative. The server knows where every hero is, when every shot was fired and whether the target was visible. Aim that swings to a target behind a wall and fires the frame they peek. Every Hawkeye arrow landing a headshot at maximum range for an entire match. Inputs arriving faster than a human hand can produce them. Movement no hero’s kit allows. None of that needs NEAC. The numbers coming from your client are impossible, and the server logs them against the account. A perfectly hidden client can still get you banned if the account does things a server can measure.

Layer three: replays and reports

This is the layer that makes Marvel Rivals different. The game keeps replays of recent matches, and anyone who was in one can load it from their match history, jump to any moment and follow any player’s camera. When someone reports you, NetEase’s review team can look at the same replay. A report in most shooters is one player’s word against another’s. Here it comes with a recording the reviewer can scrub through. The enemy team can lose, make a cup of tea, then open the replay and watch your Hela’s crosshair for ten minutes. That is why blatant settings are more dangerous in this game than almost any other.

What a Marvel Rivals ban looks like

A Marvel Rivals cheating ban is an account ban. It attaches to the NetEase account tied to your Steam, Epic, PlayStation or Xbox login, and logging in gets you a penalty notice instead of the main menu.

NetEase’s stated position is that cheating is a permanent ban. There is no strike system and no timed ban for third-party software. The timed penalties for leaving matches, going AFK or abusive chat are matchmaking and communication restrictions that run out on their own. NetEase has also said a ranked party that knowingly stacks with a cheater can be penalised alongside them. Our page on how bans work covers the penalty types and what an appeal can and cannot do.

Ban waves. NetEase bans in waves and says so publicly, with an anti-cheat announcement that often includes a count, which we are not going to quote because the pattern matters more than the number. Flags collected over days or weeks get applied together, so a cheat developer cannot push a build, watch who gets hit within the hour and work out what tripped it. A flag on day one can turn into a ban on day twenty, so a fortnight without a ban proves nothing.

Appeals. These go through NetEase’s Marvel Rivals customer service and rarely go anywhere, because the ban was issued from data NetEase can see and you cannot. Support has the driver logs, the server data and the replay. A ticket that says “I was not cheating” is compared against a recording of the match, and the reply is usually a template. The only appeals with a real chance are the ones where the ban was genuinely a mistake.

Hardware bans. NetEase has not published anything about hardware bans for this game, and almost every ban we hear about is a plain account ban. NEAC is a kernel driver, though, and can read hardware identifiers, and a fresh account on the same machine minutes after a ban is exactly the pattern that invites a closer look. Our explainer on HWID bans covers what a hardware ban actually is.

What actually gets people banned in Marvel Rivals, ranked honestly

Here is the honest order, most bans first.

Rank one is miles ahead of the rest. Free cheats from forums and YouTube get detected quickly because everyone using one is running the same file, so NEAC only has to catch a single copy.

Rank two catches people who paid for a private build and assumed that meant they were safe. An aimbot set to snap to every head with no delay looks fine from your seat and looks like a magnet from the enemy’s replay camera. The client can be perfectly hidden; the account still did something no human does.

Rank three is slower and very real. Six players on the other team all have the replay and the report button, and in a lost ranked match at least one of them will use both. Our guide on how to spot a cheater in Marvel Rivals is written from their side of the screen. Rank four is the genuine “the cheat got detected” case. It happens, and any provider that says otherwise is lying, but it is the smallest share by a long way.

Things that do not get you banned in Marvel Rivals

Plenty of people search “marvel rivals ban” because they are worried about something ordinary. None of the following is something NetEase or NEAC bans for on its own.

One caveat on macros. They are safe when one key does one thing. The moment a macro strings together an ability combo or a perfect-timing cancel, you are into script territory, and NetEase’s rules are not on your side. Our post on scripts and macros in Marvel Rivals draws that line properly.

How private cheats try to stay undetected

The other side of the arms race, without the usual promises.

Polymorphic builds. NEAC’s fastest weapon is a signature, a fingerprint of a known cheat’s code. A polymorphic build reshapes itself so the file on your machine does not match anyone else’s, and a signature written for one copy does not catch the rest.

Updating when the game and the driver update. Every Marvel Rivals patch, and there is a big one each season plus mid-season passes, shifts the game’s internal layout. A cheat reading the old layout will crash, misbehave or, worse, do something the server notices. NEAC also updates on its own schedule, sometimes with no game patch attached. Serious providers take the loader down the moment either drops and bring it back once the new build is verified.

Live status. A status page that reads undetected, updating or detected, kept current by the people who maintain the build, is worth more than any marketing copy. One that has read “undetected” since launch without ever flipping is not being maintained.

Pausing sales when something looks off. When a wave hits, or reports spike in a way that does not fit the usual pattern, the honest move is to stop selling until the cause is known.

That is how the Elocarry Marvel Rivals cheat is run: an internal build, updated on every game and NEAC change, with a public status page and sales paused whenever that status is not green. And the caveat we put on every page: no cheat is ever guaranteed undetected. Not ours, not anyone’s. Every provider that has ever existed has had a detection at some point. What separates the good ones from the bad is how quickly they notice and how honestly they say so.

How to check your status, and what to do if you are banned

First work out which of two things happened. A detection is a kick: NEAC throws an error at launch or mid-match and refuses to run the client. Your account still logs in afterwards. A ban is the account being refused at login every time, with a penalty notice that says why and for how long. Our walkthrough on whether you were detected or banned lists the messages and what each one means.

If it is a detection, stop launching the game. Repeatedly starting a flagged client is the fastest way to turn a kick into a ban in the next wave. Check the provider’s status page, and if it says nothing, assume the worst.

If it is a ban, here is the order of operations from our page on what to do after a ban:

1. Confirm it is a ban and not a platform problem: log in through Steam or Epic and read the penalty notice properly.
2. Do not create a fresh account on the same machine within the hour. See the hardware section above.
3. Only open a ticket with NetEase if you genuinely did not cheat. Support has the replay, and a ticket claiming innocence while the recording shows your crosshair jumping between heads through walls gets a template reply.
4. Work out which of the four causes above applied. If your replay shows something blatant, no client update would have saved you.

Playing with legit-looking settings, and why replays change the maths

Detection is only one of the four causes. The other three are about what other players see, and here that is stored and rewindable.

Natural aim presets. An aimbot that snaps is a report waiting to happen, and a replay makes it a report with proof. The Elocarry Marvel Rivals aimbot has aim behaviour presets running from assist up to natural, with a speed multiplier and temporal stability that keep the correction gradual. Pick a natural preset, keep the FOV tight, and let per-hero profiles do the work rather than one global setting that makes Mantis aim like Punisher.

Reaction-time pause. Real players do not fire the frame someone peeks. The reaction-time pause puts that gap back, so the replay shows a player who reacts rather than one who already knew. It removes the most obvious tell a reviewer looks for.

Flick accuracy below 100 percent. Flick shot is the setting people get greedy with. At full accuracy and full headshots, every flick lands, and that is exactly what a cheating Hela looks like in a replay. Drop the accuracy and headshot percentages so some flicks land body and some miss. Missing a flick is what makes the ones that hit look like skill.

No bunny hop in ranked. The bunny hop option has press duration, release gap and a minimum speed for a reason, and it is fun in Quick Play. In ranked, leave it off. No hero moves like that, so chained perfect hops are something a reviewer can pause on and say “that is not in the game”, and the server has already measured it.

Put those together and the version of you in the enemy team’s replay is a decent player who occasionally misses, reacts a beat late and moves like everyone else. If nobody who scrubs that recording can point at a moment and say “there”, the only layer left that can catch you is the driver, and that is the layer a provider can actually do something about. That removes three of the four ways this ends badly. The fourth is never zero, and anyone who says otherwise is selling something.