Marvel Rivals bans 500 accounts in massive anti‑cheat sweep
#Security

Marvel Rivals bans 500 accounts in massive anti‑cheat sweep

Laptops Reporter
3 min read

NetEase Games has permanently banned around 500 Marvel Rivals players for using unauthorized third‑party tools, disclosed partial IDs, and handed out four device bans, while debunking myths about anti‑cheat bypasses.

Marvel Rivals bans 500 accounts in massive anti‑cheat sweep

NetEase Games announced a coordinated ban wave targeting players of Marvel Rivals who were caught using unauthorised third‑party enhancements. The company says roughly 500 accounts have been permanently disabled, and portions of the affected usernames and IDs have been published on the developer’s blog, making it possible for some users to verify whether they were among those punished.

Featured image

What triggered the bans?

The anti‑cheat system flagged a range of modifications, from overlay hacks that display opponent health to memory‑editing tools that alter win‑loss ratios. NetEase describes these as “unauthorised third‑party enhancements” that give users an unfair advantage in ranked matches. Most of the banned accounts were stuck in Bronze, the lowest competitive tier, suggesting that even players at the bottom of the ladder were experimenting with illicit aids.

Types of penalties

  • Account bans – The majority of the 500 offenders received a permanent ban on their current account. The ban does not prevent the creation of a new account, so these players can start over, albeit without any rank or progression.

  • Device bans – Four individuals were handed harsher punishments: a device‑level ban that blocks the hardware identifiers associated with the cheating software. Bypassing this requires spoofing component serial numbers, a process that is technically possible but risky and likely to cause stability issues.

Anti‑cheat myths busted

NetEase also addressed circulating rumours that the game’s anti‑cheat could be disabled by tweaking launch parameters. The developers clarified that the alleged method only skipped a warning screen; the anti‑cheat service continued to run in the background. This clarification aims to stop players from believing they can run the game “cheat‑free” by simply hiding the notification.

How this compares to other publishers

NetEase’s approach mirrors the aggressive stance taken by companies like Riot Games, which previously announced that hardware‑based DMA (Direct Memory Access) cards used for cheating would be rendered ineffective. While Riot’s measures sparked debate among its community, NetEase’s ban wave has so far drawn little public backlash. The majority of players appear to support the crackdown, viewing it as a necessary step to keep the competitive environment fair.

Who is affected?

  • Casual players who may have experimented with low‑risk overlays but never intended to cheat are likely to be caught in the account‑ban sweep.
  • Competitive Bronze players seem to be the primary demographic, possibly because they are more tempted to use shortcuts to climb the ladder.
  • Hardcore cheaters who invested in hardware‑level hacks faced the steepest penalties, with device bans that could render their rigs unusable for Marvel Rivals without extensive re‑configuration.

What should you do?

If you reported a suspected cheater, you can now check the published list on the official Marvel Rivals blog to see whether your tip led to action. For players who were banned, the only recourse is to appeal through NetEase’s support portal, though the company has not indicated a willingness to reverse permanent bans.

Bottom line

NetEase’s decisive ban wave sends a clear message: third‑party enhancements will not be tolerated in Marvel Rivals. By publishing partial IDs, the developer adds a layer of transparency that lets the community verify the enforcement. While the bans may push some offenders to create fresh accounts, the threat of device bans should deter the most egregious cheaters from returning.


Article by Anil Ganti, Senior Tech Writer, Notebookcheck

Comments

Loading comments...