Why this post exists
Every overlay on the market claims to be "the best Marvel Rivals cheat menu." That phrase is doing a lot of work. The overlays that back it up are the ones that ship a payload within minutes of every patch, hide their signatures aggressively, and answer Discord tickets during the hours their users actually play. The overlays that don't back it up have a flashy splash screen and a Telegram you can't reach after midnight.
We sell Nimbus. We are also the people who reverse-engineer the competition for a living — we know what their binaries do and don't do. This post is the honest version of the comparison, with the caveats you should expect from a vendor: we are biased, we'll tell you where we lose, and the table at the bottom is sourced from public marketing pages and our own RE work.
If you want the buyer-side checklist without the comparison, jump to the three-question stress test in our are overlays safe post.
What "best" actually has to mean in 2026
Marvel Rivals runs Easy Anti-Cheat (EAC) with a second-stage NEP kernel driver. Both update on a tight cadence. "Best" for a Marvel Rivals overlay in 2026 has to mean five things, in this order:
- Patch turnaround in minutes, not hours. Every patch can move UE5 offsets and rename properties. An overlay that's hours behind is either crashing on inject or — worse — writing stale signatures into a process that EAC now scans for them.
- Hero-aware aim, not generic FOV-bot. Hawkeye's arrows have gravity. Winter Soldier's bullets travel at 180 m/s. A flat target-the-closest-head loop is a 2022 cheat. Good overlays solve the projectile intercept equation per hero, every frame.
- Information ESP, not box ESP. Box-on-head ESP is loud, instantly obvious in spectator clips, and trivially detected by playstyle review. Cooldown timers, ult charge, and summon tracking give you the same intel without ever drawing a box on a live opponent.
- HWID lock + key isolation. If one key works on ten machines, that key is a Telegram resale already. HWID lock binds you to your hardware fingerprint so resellers can't dilute the userbase.
- Humans in support. When your loader doesn't open after an antivirus update, a bot can't help you. You need to ping someone in a Discord and get an answer in under an hour.
Anything else — themes, custom crosshairs, font pickers — is icing. If the five above are wrong, the icing is irrelevant.
How Nimbus compares to the loudest public overlays
The names below are the overlays we see mentioned most often in Marvel Rivals adjacent communities. We've used or reverse-engineered each at least once. Where we cite their marketing, the citation is their public site as of this post's date.
| Feature | Nimbus | "Oreo"-class overlays | Forum free-dumps |
|---|---|---|---|
| Patch turnaround | Minutes (CI watches manifest) | Hours to a day | Days to weeks (or never) |
| Hero-aware projectile aim | Per-hero, gravity-correct | Hawkeye-only, fixed speed | Hitscan only |
| Information ESP (cooldowns/ult) | Yes — cooldowns, ult %, summons | Partial (ult only) | Box-on-head only |
| Silent aim (FWeaponFireContext) | Yes — bUseCustomTargetInfo path | Mostly yes, some camera-snap | No, brute FOV-bot |
| Signature rotation per build | Yes — every push | Sometimes | No |
| HWID lock | Yes — SHA-256 of stable IDs | Mostly yes | No |
| Public changelog with dates | /changelog, multiple ships/week | Discord-only, no archive | None |
| Public status page | /status — live + history | None | None |
| Refund / replacement policy | /refund — written, machine-checked | "DM the dev" | No policy |
| Discord first-response (peak) | < 30 min | 1–6 hours | None |
| Auto-update | Yes — versioned releases | Manual re-download | None |
| Premium UI (14-tab menu, themes) | Yes — full keybinding rebind | Yes (same template most use) | Stock ImGui |
| Trial | 1-hour single-use trial | Day-keys ($5–10) | Free (with the obvious risk) |
Every column where we wrote "Yes" is either visible in the product or specced in our changelog. The "Oreo"-class column is the cluster of paid overlays that share a KeyAuth-Imgui-Loader template (Oreo, sigmarivs, the various rebrands of those). They're better than free dumps but they share the same signatures across the cluster, which is the structural problem.
Where Nimbus actually loses
This is the section vendors usually skip. We won't.
- Price. A forum dump is free. A day-key from an Oreo-class overlay can be $5. Nimbus subs start at $5/day too, but our lifetime tier is well above the cluster's. If your only metric is dollars, you can find cheaper.
- Themes catalog depth. A few competitors ship 30+ themes with custom crosshair packs. We ship 6 polished themes. If you want 20 reskins of the same menu, we're not the right buy.
- Older heroes' projectile tables. We solve projectile lead per hero from sampled velocity. For heroes added in the last patch, the first hour after release uses a conservative fallback while the sampler converges. A competitor with a hand-tuned table can beat us in that one-hour window.
That's the honest list. Everything else, we're confident we win on. You should test it — see "How to actually test before you buy" below.
Hero-aware aim: what that means in practice
Generic aimbots treat every hero like Black Widow: pick the closest enemy head, snap the camera at constant pixel speed, fire. That's loud, looks terrible in clips, and misses on every projectile hero.
Hero-aware aim means:
- Hitscan heroes (Black Widow, Punisher) get conservative smoothing tuned to the hero's recoil model, not a global FOV.
- Arc projectiles (Hawkeye, Magik's certain abilities) solve a
quartic gravity intercept with G=980 cm/s², Z-up. Arrow speed
scales with charge fraction (Hawkeye:
12000 + charge × 6000 cm/s). - Linear projectiles (Winter Soldier, Punisher rocket) get a
per-hero speed sampled from
AMarvelAbilityTargetActor_Projectileover 5 frames, then cached. - Melee heroes (Wolverine, Iron Fist) get a target-prediction step that accounts for enemy velocity over the swing frames.
This is why we don't ship a single "Aimbot" toggle. The aimbot is 12 different solvers under the hood, dispatched by hero ID. If you spectate a Nimbus user, the camera doesn't snap — it lags one tick behind reality, like an aim-trainer with great habits.
Information ESP: cooldowns over boxes
Box ESP is the most-detected feature in any cheat menu, both by EAC's visual model (it looks the same across builds) and by spectator review. Spectator review is the bigger threat in 2026 — Marvel's report system feeds high-rated reports straight to a manual review queue, and box ESP on a clip is an instant ban.
Information ESP gives you the same intel without the visual artifact:
- Cooldown bars above the enemy nameplate (RMB / E / Shift / F /
Ultimate). Source:
GetGameplayAbilitiesByInputKey+GetCooldownRemainingForTagwalked per ability. - Ultimate charge % read from
GameStateBase + 0x6F0(UThreatValueAdmin), mapped to player. - Summons tracking — Jeff swallow zone, Namor totems, Peni mines, Groot walls. Source: per-class scan of PersistentLevel for spawned actors with team filtering.
- Health-pack timers in sub-levels, with respawn countdown.
You play around enemy cooldowns. You play around enemy ults. You play around summons. None of this draws on a live opponent's body.
Patch cadence: what we actually do
Every patch, our pipeline does this:
- A watcher polls Marvel Rivals' Steam manifest every 60 seconds.
- On manifest delta, a build runner pulls the new game build.
- The SDK regenerator (Dumper-7 + our diff scripts) emits a fresh header tree.
- The payload rebuilds against the new SDK. Anything that fails to compile is a flagged offset shift; we hand-patch and re-run.
- Tests run against a local Marvel Rivals install in a practice range to confirm core features fire.
- Build is signed, manifest is bumped, the loader's auto-update kicks in for every active user.
End-to-end: 4–8 minutes on a clean patch, 30–45 minutes on a structural one (UE5 class layout change, anti-cheat signature addition).
You can see every shipped version on our changelog. Every entry there is a real CI run with a real commit hash.
How to actually test before you buy
You don't have to take any of this on faith. We sell a 1-hour single-use trial — single-use per email + Gmail-root + HWID + IP + fingerprint, so it can't be farmed, but it's free, and the menu is the production menu. Specifically:
- Sign up at /signup — no card, just email.
- Claim the trial in your dashboard.
- Download the loader.
- Run it in a Marvel Rivals practice range. Spectator-mode a friend if you want to verify the aim doesn't snap.
If the menu doesn't behave like the rest of this post claims, walk away. We'd rather you walk away after a trial than refund-request after a 30-day sub.
Bottom line
The best Marvel Rivals overlay in 2026 is the one that ships within minutes of every patch, solves projectile lead per hero, draws information ESP instead of boxes, runs a real HWID lock, and has humans in support during peak hours.
We think that's Nimbus. We're willing to be measured against the field — the comparison table above lives or dies on whether you find us misrepresenting a competitor. If we did, tell us in Discord and we'll fix it.
Either way, run the three-question stress test from are overlays safe on every overlay you're considering. The bad ones fail at question one.

