Yes — there are ban waves. Multiple a year.
Marvel Rivals does run ban waves. They're a real, periodic enforcement event. NetEase announces some of them publicly with a banned-account count ("we banned 504 cheaters this week"); others happen quietly in the backend signature pipeline without a public post.
The right question isn't "is there a ban wave coming." The right questions are:
- What does each wave actually target? Because they don't all target the same thing.
- How often do they happen? Because the cadence matters for how you think about risk.
- What's the recovery path when an account is hit?
- What does the wave history tell us about which categories of overlay tooling survive and which don't?
This post is the honest read. We sell an overlay (Nimbus); we're in the same broad category that ban waves scrutinize. We're going to be specific about what we've seen, what we haven't, and what the prudent risk posture is for any player using any external tool.
If you want the technical anti-cheat layer underneath the bans, the EAC + NetEase + NEP explainer covers the stack. This post is about the enforcement pipeline on top of it.
The 2026 ban wave cadence
Across 2025-2026, the observed pattern from NetEase has been:
- Quarterly large waves. Roughly every 8-12 weeks, a major signature update ships and a batch of accounts gets banned in the following 48-72 hours. These are the waves NetEase sometimes publicizes.
- Continuous trickle bans. Between the large waves, there's a steady background rate of individual bans from manual review queues (replay reports, support tickets) and from the behavioral model flagging outliers.
- Pre-event hardening. Before major in-game events (new season launches, tournament weekends, anniversary patches), the cadence accelerates. NetEase wants the event to look clean on broadcast.
The 2026-specific pattern adds one new variable: NetEase started HWID-propagating more aggressively in late 2025. A banned account can carry a HWID stain that affects subsequent accounts on the same hardware fingerprint. This is documented; it's not hypothetical.
What the waves target
Not all ban waves target the same tooling. From observed post-wave forum chatter and the pattern of which cheat-providers went dark after each wave, the categories that get hit are distinct:
Signature-detected cheats
The most common target. NetEase's signature database catches memory patterns from known public cheats — old aimbots, recycled Themida-packed binaries from forum providers, multi-game cheats that share code with detected products.
If a cheat provider is selling a tool with stable memory layout, they get caught on the next wave. The provider goes silent for a week, ships a "new" build with shuffled bytes, gets caught again three weeks later. This is the cheap-provider treadmill.
Behavioral outliers
Inhuman aim trajectories, impossible-to-achieve flick angles, and sub-frame target acquisition. The behavioral model flags these even when the binary itself isn't signature-detected. Lockon aimbots produce these patterns by default; silent aim produces them on the server side.
Reported accounts in manual review
Player reports flow into NetEase's review queue. Reviewers watch replays and ban on judgment. This is slower than the automated pipelines but catches accounts that the automated systems miss.
HWID-tagged hardware
A banned account leaves a HWID stain. New accounts created on the same hardware can be insta-banned on creation in some cases. For mitigation, see our HWID reset guide.
What waves don't target (as much)
Worth being specific about which categories are not the primary focus of NetEase's enforcement pipeline:
- Single-game settings tools. Apps that adjust your in-game sensitivity, FOV, or keybinds via Marvel Rivals' own settings menu are not cheats and don't trigger ban detection.
- Replay analyzers. Tools that watch your saved replays after a match are entirely outside the game's runtime and don't intersect with the anti-cheat stack.
- External coaching software. Voice coaches, screen-sharing to a coach, post-game analysis — none of these are anti-cheat concerns.
These categories are never the target of ban waves because they're not in the anti-cheat's threat model. If you're using this kind of tool, you're not in the conversation.
The honest read on overlay risk
External overlays — including Nimbus — sit in the "runtime external tooling" category that anti-cheat does scrutinize. Saying "Nimbus has never had a ban wave hit it" would be a sales claim; saying "no overlay is zero-risk in this category" is the honest read.
What we can be specific about:
- We've shipped continuous detection-resilience updates since launch. The changelog lists the major hardening passes by version.
- We do not lock crosshairs, modify shot vectors, or apply the inhuman-trajectory patterns the behavioral model flags.
- Nimbus' usage during periods around publicly announced ban waves has not produced a customer-reported wave-affected account, but we don't promise this — anyone making that promise is selling, not informing.
- The status page reflects current customer-reported account health. If a wave hits a non-zero percentage of our user base, it goes there. We don't hide it.
Customers should run on accounts they can afford to lose. That's the honest, unembellished position. Any overlay vendor (us included) that tells you otherwise is misrepresenting the category.
What to do if you suspect a wave is imminent
A few prudent steps if you read about a publicly announced wave or see chatter about one in r/marvelrivals or related forums:
- Don't log in for 48-72 hours after the wave is announced. The first 72 hours of a wave are when the bulk of bans land. Sitting it out reduces exposure to the version-specific signatures that the wave is built around.
- Wait for the overlay you use to ship a post-wave update. For Nimbus, this happens within days when needed; the changelog reflects post-wave responses.
- Don't try to "out-cheat" the wave by buying a different forum cheat. The forum cheat is almost certainly the category being targeted; switching from a category-A tool to a category-B forum cheat mid-wave is how people lose accounts at compound rates.
If you're using a free forum cheat right now and a wave is announced, the realistic outcome is your account is banned in the next 72 hours regardless of what you do. Plan accordingly.
Recovery path
If your account is banned:
- NetEase's appeal process is the official path. It's slow (weeks) and the success rate for genuine cheating-detected bans is low. For appeals of false-positive bans, the success rate is higher; for appeals of "I was using a cheat and got caught" bans, the success rate is near zero. Appealing in good faith only.
- HWID reset and account creation is the unofficial path. This carries its own risks (see the HWID-propagation note above). Our HWID reset guide covers the technical steps for legitimate hardware migration — same workflow applies for post-ban hardware refresh, though the legitimacy of doing so post-ban is on you.
- Re-buying the game on the new account. Marvel Rivals is free-to-play, so this is no-cost on the game side. The cost is in lost cosmetics, rank, and friends list.
There's no fast undo. The realistic position is that a ban landing on an account means that account is gone. Plan for that outcome up-front by not playing on an account you can't afford to lose.
How ban waves correlate with overlay updates
Reading the historic pattern of overlay providers across the 2025-2026 wave cycle:
- High-quality, frequently-updated overlays (Nimbus, a small number of others) have weathered each wave with relatively minor user impact, because the update cadence stays ahead of the signature database refresh cycle.
- Stale, forum-leaked, or compiled-once-shipped-forever overlays get hit hard. Every public-source aimbot that ships the same binary for six months gets caught by signature on schedule.
- High-ban-risk feature categories (lockon aimbot, silent aim, no-recoil) get hit harder than info-only categories (ESP, ult-charge tracker, projectile prediction). The behavioral model catches the action-modifying features faster than the information-only ones.
The pattern argues that information-only tooling with frequent updates is the more durable category. Nimbus sits there. Action-modifying tooling, regardless of provider, is exposed.
Bottom line
Yes, Marvel Rivals has ban waves in 2026. Quarterly large waves, continuous trickle bans, pre-event hardening. They target signature-detected cheats first, behavioral outliers second, reported accounts third, HWID-tagged hardware fourth.
The honest risk posture for any external overlay user: run on accounts you can afford to lose, watch the status page for wave coverage, and don't try to out-clever the enforcement pipeline by hopping between sketchy forum providers. The category as a whole is not zero-risk; the upper-tier providers (Nimbus and a small number of others) carry materially less risk than the forum end of the market, but "materially less" is not "none."
For the technical layer beneath all this, see the EAC + NetEase + NEP explainer. For the overlay safety baseline, see are Marvel Rivals overlays safe. For current product status, the status page is the ground truth.
If you're considering a purchase, the Marvel Rivals overlay product page is upfront about features and risk. If you have account-specific questions, the help center covers the recovery and account-care workflows.
