ARC Raiders Fair Play Update: New Kernel Anti-Cheat Test, Anybrain Controversy, And The Question Embark Did Not Answer

The ARC Raiders fair play update from Embark Studios went live on May 7, 2026, the same day the Riven Tides patch 1.26.0 dropped. It is part news post, part operating-statement, framing anti-cheat as a "studio-wide effort" rather than a one-time launch. The headline change is a new kernel-level solution under test on Speranza and the Rust Belt. The headline omission is any direct response to the Anybrain false-ban threads that have been climbing the r/arcraiders front page for months. Below is what Embark said, what the community has said back, and where the gap sits.

For the broader explainer on which anti-cheat ARC Raiders uses and how Abnormal Match Compensation works, see our anti-cheat and compensation breakdown. This post focuses on what is new in the May 7 announcement.

The post describes anti-cheat as ongoing work, not a finished product. Three operational details are worth pulling out:

First, there is a new kernel-level solution being tested on Speranza (the Finals' map) and the Rust Belt (ARC Raiders' world). Embark frames it as a way to "sharpen both detection and precision," which in anti-cheat terms means catching more cheats while flagging fewer legitimate players. The product name was not disclosed, and the rollout date was not given.

Second, the Anybrain machine-learning layer continues to run on top of EAC. Embark calls it "input telemetry analysis" and credits the partnership with Anybrain. This is the layer that looks for behavioral patterns no human could plausibly produce - perfect headshot chains, inhuman reaction times, impossible movement speeds.

Third, the post acknowledges accessibility devices as a hard problem. Players who use adaptive controllers, eye tracking, or voice command can produce input patterns that look statistically unusual to behavioral models. Embark says the system analyzes telemetry plus communication patterns to separate legitimate accessibility use from abuse. The post offers no specifics on how, citing operational security.

What is missing from the announcement: any numbers. There are no ban totals, no detection rates, no false-positive rates, no comparison to launch-period performance. The full official text is on the Embark fair play page.

Four pieces ship in production right now. Easy Anti-Cheat sits at the kernel level and blocks known commercial cheats before they inject into the game. Anybrain machine-learning analysis runs on top of EAC, looking for statistically improbable behavior. Abnormal Match Compensation kicks in after the fact, automatically returning stolen loot through in-game mail when a match gets flagged. And undisclosed layers behind those handle pieces Embark will not name in public.

Kernel-level visibility is non-negotiable for catching modern commercial cheats. Most current cheat developers operate at ring 0 or below the OS, and a user-mode anti-cheat cannot see them. EAC already runs at the kernel level, so this new solution is either a layered second kernel agent or a replacement candidate Embark is evaluating. Anyone who has worked on anti-cheat will recognize the pattern. Layering kernel agents adds detection coverage at the cost of complexity, while a replacement is a higher-risk swap that resets a lot of internal tooling.

The phrase "sharpen both detection and precision" is the interesting tell. "Precision" in this context means false-positive rate. Calling it out publicly suggests Embark knows the false-positive problem exists, even though the fair play post does not name it.

The community split here is sharp. Past Embark anti-cheat moves have pulled enormous positive engagement on r/arcraiders. The "Dear Cheaters, the reckoning has begun" ban-wave thread hit 10,594 upvotes in January 2026. The post celebrating the loot-return system pulled 7,290 upvotes. The "Are these the best devs ever?" thread for Embark taking cheaters seriously hit 5,043. By any normal community-management measure, this is a fanbase that loves what Embark is doing on bans.

And then there is the other side. The thread "This is ENTIRELY Embark's fault" from March 17, 2026 has 2,323 upvotes and 335 comments. The followup post on a disabled player who has been banned since November 2025 and remained banned as of April 9, 2026 has 1,622 upvotes and 465 comments. Those threads document specific receipts: Anybrain has been false-banning players for months, automated support routes through HelpShift have closed tickets without resolving them, and high-profile cases (the streamer Tfue is named) only got resolved when the audience escalated publicly.

The May 7 fair play post does not respond to any of this directly. The single signal that Embark is aware comes in the word "precision" attached to the new kernel test.

Two practical points if you play right now. If you use accessibility hardware, keep records of device serial numbers and any medical or accessibility documentation. The Reddit threads show that escalating a false ban requires you to provide a paper trail, and the AI-driven support pipeline has historically closed tickets without responding to evidence. Public visibility (a popular streamer signal-boosting your case) has worked when private support channels have not.

If you have not seen Abnormal Match Compensation trigger for you, that does not mean it is broken. The system fires after a confirmed cheater detection, which can land days or weeks after the match itself. Check your in-game mail occasionally. The deeper mechanics live in our anti-cheat and compensation post.