How Marathon's Anti-Cheat Works — and What It Misses — blog cover image
BlogHow Marathon's Anti-Cheat Works — and What It Misses

How Marathon's Anti-Cheat Works — and What It Misses

daudzulfiqar80
June 24, 2026·
1 min read
·
936 views

Bungie tested anti-cheat during the Server Slam. Here is how detection works and why some cheats still slip through.

Bungie treated cheating as a launch priority. The February Server Slam doubled as an anti-cheat stress test. Five months later, cheaters still show up — so how does the system work?

Three layers

Kernel client protection

Catches known signatures and memory tampering. Public free cheats die here within days.

Server behavior analysis

Tracks impossible aim, loot paths, and stat outliers. Ban waves come in batches so devs cannot easily reverse-engineer triggers.

Player reports

Feeds the behavior pipeline. Update 1.1.5 added voice moderation too.

Marathon anti-cheat — Bungie tested systems during Server Slam

Image credit: IGN

What slips through

Private builds with small user pools are harder to fingerprint. External ESP and DMA setups sit outside what kernel drivers see easily. That is why undetected Marathon cheats remain a market — not an endorsement, just reality in extraction shooters.

Protect yourself

Assume someone in every lobby has information you do not. Our ESP explainer shows what wall vision actually reveals so you can position smarter.

More from the Blog

Comments

Join the conversation

Sign in to like, reply, and comment