Marvel Rivals Ban Wave History — Launch to 2026
Full Marvel Rivals ban wave timeline from Aug 2024 beta name-and-shame to May 2026. Continuous detection model, no batched waves, Incentivized Throwing crackdown.
NetEase published the names and account IDs of 190 banned players on marvelrivals.com in August 2024 — three months before Marvel Rivals' commercial launch. That public name-and-shame announcement told the cheat-buying market exactly where NetEase's enforcement posture would sit: aggressive, public, and unapologetic. Eighteen months later, the pattern has held. This is the compressed ban-wave history for Marvel Rivals from closed beta through May 2026, with primary-source links where available.
This post is a cluster of the Marvel Rivals Cheats Complete 2026 Guide pillar. The pillar referenced the major enforcement milestones at a high level. This piece is the full timeline with date-by-date detail, plus the structural analysis of why NetEase's continuous-detection model differs from Blizzard's quarterly waves or Krafton's weekly notices.
August 2024 — Closed Beta Name-and-Shame
The event. NetEase ran a closed beta for Marvel Rivals from late July through mid-August 2024. During and after the beta, NetEase banned 190 accounts for cheat-software usage and published the full account name and ID list on marvelrivals.com. The announcement is at marvelrivals.com/announcements/20240815.
Why it mattered. Public name-and-shame is unusual in the AC industry. Most publishers ban quietly to avoid drawing attention to the cheat scene or giving banned players the publicity to spin themselves as victims of overreach. NetEase went the other direction — published names, published account IDs, made it a public deterrent.
The closed beta is also where most of NeacSafe's initial detection-engine tuning happened. NetEase used the beta as a data-collection window for cheat-side behavior, with the ban wave as a pre-launch signal that detection was online.
The signal to the cheat market. Two things. First, NetEase will enforce. Second, NetEase is willing to use shame as a tool. Both signals influenced how the early Marvel Rivals cheat market priced and described its products. Vendors who had been planning to launch with "EAC bypass for Marvel Rivals" (because most assumed Marvel Rivals would use EAC — it didn't, see the NeacSafe technical breakdown cluster) reconsidered ahead of launch.
December 6, 2024 — Commercial Launch
The event. Marvel Rivals launched commercially worldwide on Steam + PS5 + Xbox. Free-to-play, cross-play enabled, ~10M concurrent players in the launch weekend per Steam stats.
The cheat presence. Cheaters appeared within hours of launch per Sportskeeda and GameRant coverage. The early cheat market was dominated by repurposed Naraka: Bladepoint cheats (same AC, similar code surface) and a handful of EAC-tuned products mislabeled for Marvel Rivals.
Initial NeacSafe behavior. The driver was loaded and active from day one, with the same VMProtect-packing and load-from-%TEMP%-and-delete pattern documented in the 0x90.sh June 2025 analysis. Detection windows on public cheats sat at hours-to-days; private cheats had longer windows but were limited in distribution.
Industry data point (approximate). Some industry analyst pieces claim ~1.2M total bans in Marvel Rivals' first year (launch through Dec 2025). Primary-source verification is not publicly available; we mark this as approximate. For comparison: Rust had 296K perm bans in a single annual period per Facepunch's reporting, and Fortnite had a single 70K wave at one point. 1.2M for Marvel Rivals first year is plausible given NetEase's continuous-detection model, but unconfirmed.
January 2025 — macOS / Steam Deck False-Positive Wave
The event. NetEase's NeacSafe driver loaded under Wine / Proton (the Linux compatibility layer Steam Deck uses; also used by macOS players running Marvel Rivals through Crossover or similar). The driver's behavior under Proton produced false-positive bans for legitimate cross-platform players. Players reported being banned for "no reason" on Steam Deck despite never running cheats.
The response. NetEase publicly apologized via GamesRadar and Push Square coverage, reversed the bans, and adjusted NeacSafe to recognize Proton-loaded sessions as non-bannable false positives. This is one of the very few cases in modern AC history where a publisher publicly apologized for false-positive bans and reversed them at scale.
Why it mattered. Two things. First, it demonstrated that NetEase will adjudicate cases — they're not "no appeal, ever" the way some publishers operate. Second, it highlighted a persistent risk for Linux / macOS players using Marvel Rivals via Proton. Even with the Jan 2025 fix, NeacSafe's behavior under Proton has remained occasionally inconsistent through 2026.
Steam Deck implication today. Marvel Rivals on Steam Deck is officially supported but the compatibility layer adds risk. Raw Rivals is Windows-only — we don't support Proton-based usage because the driver layer mediation makes cheat behavior unpredictable. If you're playing Marvel Rivals through Proton, the safer path is not to use a cheat rather than risk the inconsistent driver behavior.
Q1 2025 onward — Continuous Detect-and-Terminate Model
The shift. After the Jan 2025 false-positive incident, NetEase moved Marvel Rivals to a per-match continuous-detection model with match invalidation. The pattern, per CBR coverage and Dexerto reports:
- Cheat detection fires during an active match
- Cheater's session is terminated
- Match data is purged for the cheater (no progression, no rating gain)
- The other 11 players in the match keep their MMR and progression
- The cheater's account is flagged; subsequent matches face stricter scrutiny
- Repeat detections escalate to permanent ban + HWID ban
Why this differs from Blizzard / Krafton style. Blizzard publishes quarterly batched ban-wave numbers (Overwatch Defense Matrix blog posts). Krafton posts weekly notices (PUBG Weekly Bans Notice). Both use batched processing where detections accumulate and then ban actions land in waves.
NetEase uses continuous processing — detections fire and actions land in real time. There are no Thursday ban waves on Marvel Rivals. There are no season-end batched announcements. The detection happens roughly continuously.
Operational impact for cheaters. No "ride out the wave window and wait for the next cycle" strategy because there are no cycles. The detection profile is constant, and the action profile is constant. The cheat hygiene practices that matter on continuous-detection ACs are conservative tuning, careful patch-day behavior, and HWID spoofer use.
Q2 2025 — Underground Cheat Marketplace Expansion
Documented in press coverage. Q2 2025 saw a notable expansion of dedicated Marvel Rivals cheat vendors — TATEWARE, several elitepvpers thread chains, the early-period Battlelog Marvel Rivals offerings. Most of the new vendors confidently misidentified the anti-cheat as EAC. The Marvel Rivals comparison cluster covers the major vendors.
No specific ban-wave event in Q2 2025 — the continuous-detection model means the detections accrued without batching. But the underground cheat market data shows several waves of vendor consolidation as cheaper products got detected faster than their detection-window expectations.
June 2025 — 0x90.sh NeacSafe Driver Analysis Published
The event. Independent security researcher published the first detailed public reverse-engineering of NeacSafe's driver internals at 0x90.sh. The writeup documented VMProtect packing, the load-from-%TEMP%-delete pattern, the no-DriverUnload design, the no-kernel-user-heartbeat architecture, and details of the HWID read profile.
Why it mattered for cheat market. Before the 0x90.sh writeup, "what NeacSafe actually does" was tribal knowledge inside cheat dev communities, with no authoritative public source. After the writeup, the technical baseline became public — vendors who had been confidently labeling their products "EAC bypass" had nowhere to hide from the correction.
Why we cite it. The 0x90.sh analysis is the single most authoritative public technical source on NeacSafe. We reference it across every Marvel Rivals cluster because it's the editorial-credibility anchor — knowing NeacSafe is the AC, citing the actual research, is the editorial test that separates serious Marvel Rivals coverage from copy-paste blog spam.
Late 2025 — Season 1-4 Continuous Detection
The pattern. Through Seasons 1, 2, 3, and 4 of Marvel Rivals, NeacSafe's continuous-detection model ran without major incidents. Detection windows on widely-distributed public cheats stayed at hours-to-days; private cheats had longer windows. The detection-to-action latency improved through driver updates that landed silently (NetEase rarely announces NeacSafe updates publicly).
Notable Q4 2025 development. NetEase's behavioral analysis pipeline expanded — additional telemetry on aim patterns, headshot rates, and statistical anomalies started feeding into manual review for top-rank players. This is the layer that's analogous to Epic's behavioral analysis for Fortnite, though NetEase's pipeline is less mature than Epic's (Marvel Rivals is a younger game with less historical telemetry).
February 2025 — Shalzuth RCE Disclosure
The event. Security researcher disclosed a remote code execution vulnerability against Marvel Rivals where a crafted in-game packet could execute attacker-controlled code on a target player's machine. PC Gamer covered the disclosure; the technical writeup is at the researcher's site.
The response. NetEase patched within ~24 hours, faster than typical NeacSafe driver updates. No public statement was issued.
Why it mattered. Demonstrated that NetEase can move fast on critical security issues when motivated. The post-Feb-2025 patch posture has been more responsive than the pre-Feb-2025 posture. Detection windows on widely-distributed public cheats narrowed from weeks to days. Hacker News covered the disclosure thread at length.
March 5, 2026 — Incentivized Throwing Crackdown
The event. NetEase's official statement on third-party bounty sites paying players $10-$40 to throw matches against streamers. Permanent ban policy introduced for participants. The announcement is at marvelrivals.com/announcements/20260306, with Dexerto covering the broader story.
Why this happened. Third-party sites (LosingCo, ThrowFiverr, and a handful of others — names redacted because they don't deserve search-result oxygen) were operating as bounty marketplaces. A streamer would queue a public match; bounty hunters who matched into the streamer's lobby would deliberately throw the match against them and collect $10-$40 from the third-party site. The pattern had been growing through Q1 2026 and became a visible problem during major content-creator events.
The detection mechanism. NetEase rolled out a behavioral classifier targeting AFK / throw patterns — extended inactivity in active engagements, intentional movement away from objectives, repeated death from same direction in patterns inconsistent with normal play. The classifier feeds into the manual review pipeline for borderline cases.
Why it matters for normal cheaters. It generally doesn't. The Incentivized Throwing detection targets players paid to lose, not players using third-party software to win. Aim assist, ESP, ult tracking — none of these are flagged by the throw-detection pipeline. Our brand position: we sell aim assistance, not match sabotage.
Why it matters for the broader market. It expanded NetEase's behavioral telemetry pipeline. The infrastructure now ingests AFK / throw patterns at scale, which means the next behavioral category NetEase wants to add (aim-pattern statistical detection, for example) has a lower marginal cost. Expect NetEase's behavioral side to mature faster going into 2026-2027.
Q1-Q2 2026 — "Lord Farming" Combat-Behavior Detection
The event. NeacSafe rolled out an additional combat-behavior detection system targeting proficiency-AFK exploits. Players had been running scripted Lord-rank farming for cosmetic / progression rewards — botting Quick Match games to grind hero-specific Lord rank without actually playing.
The mechanic. Warning → short-term ban → long-term ban → permanent escalation tiers. The classifier looks at input patterns (mouse movement variance, keyboard input timing) and decision patterns (when ults are used, who they're used on, target prioritization). Scripted farming produces low-variance inputs and predictable decisions; human play has higher variance.
Why it matters. Affects cosmetic / proficiency farming, not cheating per se. But it expanded NetEase's behavioral pipeline further — the input-variance classifier can in principle be repurposed for aim-pattern detection (aimbot produces low-variance aim curves; human play has higher variance). This is the same statistical-anomaly direction Epic took with Fortnite's behavioral layer.
May 2026 — Season 8 "Sins of Alchemax" Patch Day
Coming May 15, 2026. Season 8 launches with Devil Dinosaur as the 50th hero and the Alchemax HQ map. Cyclops drops at S8.5 mid-season.
Expected pattern. Patch lands ~9am PT. NeacSafe + game state schemas update; cheat detection is erratic for the first 6 hours as the patched server-side state drifts from old client state. Cheat operators ship patched builds within 6-12 hours. Status flips back to UNDETECTED.
The risk window. The single highest-risk session of any month is the 6-hour window after a content patch lands. Running an outdated cheat against patched server state produces inconsistent reads that NeacSafe's behavioral telemetry catches. Wait for the Marvel Rivals cheat status page to confirm UNDETECTED before re-queuing.
No season-end ban wave pattern
Worth flagging because some buyers expect Marvel Rivals to follow the seasonal-batched-ban pattern of other games. It doesn't. NetEase's continuous-detection model means waves don't bunch into Thursdays or season-end. Detection happens roughly continuously.
This affects cheat-buying strategy in two ways:
First, there's no "play through the season, ban hits in the off-season" window. If you get caught, you get caught in real time during the match.
Second, there's no "ride out the wave" strategy. The model is constant pressure rather than batched action. Conservative tuning, hygiene, and HWID spoofer use matter more on this AC than on quarterly-wave ACs because there's no recovery window.
The Bigger Picture — What This Tells You About Buying Cheats for Marvel Rivals
Three takeaways from 18 months of NetEase enforcement.
Takeaway 1: Real-time continuous detection means no "off-season." Conservative play matters every session. Aggressive tuning that "works" in one match is the highest-risk pattern over a 50-match window.
Takeaway 2: NetEase will adjudicate cases when wrong. The Jan 2025 false-positive reversal shows the publisher is willing to acknowledge mistakes. This doesn't mean appeals work for legitimately-banned cheaters — it means false positives have a path to resolution that some publishers refuse to provide.
Takeaway 3: HWID spoofer is non-optional. The cross-NetEase ban propagation makes the spoofer the foundation, not the add-on. The cluster on Marvel Rivals HWID spoofer + cross-game ban covers the full technical detail.
Raw Rivals ships with conservative defaults and the kernel-level bypass infrastructure built for NeacSafe's behavioral profile. The pillar Marvel Rivals Cheats Complete 2026 Guide covers the broader product context; the setting up safely cluster walks through the pre-flight workflow. If you've read this far and you're still considering free Marvel Rivals cheats, the free cheats warning cluster covers why that path ends in lost Steam tokens and a banned hardware fingerprint.
