EA has published its monthly anticheat rundown for Battlefield 6, covering June — a month that overlapped with most of Season 3 and the game’s first Ranked season. The numbers are up rather than down, and the report explains why: the studio is deliberately holding a door open until the TPM 2.0 grace period ends, and that switch is expected to flip within a few weeks.
June by the numbers
EA tracks Match Infection Rate (MIR) — the share of matches spoiled by at least one suspected cheater, including accounts the team hasn’t gathered enough evidence to punish yet.
- June opened at 5.52%, picking up exactly where May left off.
- A slow climb led to an early peak of 6.37% on the 11th.
- The rate then drifted down until the 24th, sitting at 5.88%.
- From there it rose again, reaching 6.59% at the time the report was written.
The developers frame the increase as a known cost rather than a detection failure. While the TPM 2.0 warning phase is running, one bypass route stays usable, and part of the cheating population is using it. Once enforcement lands, EA expects both a drop in MIR and the ability to ship additional detections and enforcement actions that are currently gated behind that change.
Javelin activity and the vendor landscape
Over the course of June, EA Javelin Anti-Cheat is credited with stopping 226,592 cheating or tampering attempts before any of them reached a live match. The team says it is monitoring 112 active cheat-related entities — software, hardware solutions, vendors, resellers and their communities — with 107 of them (95.53%) reporting broken features, detection notices, downtime or a complete shutdown.
There’s also a forward-looking note: the list of prohibited hardware and software is being revised for Season 4. Season 3 gave EA reasons to reassess features and use cases that sit close to the line without being obvious cheats, and those changes will bring blocks, warnings and enforcement. A dedicated Season 4 anticheat post is promised with details.
What this means for players using software
Start with TPM 2.0, because it has a hard deadline attached. Right now the warning is informational — systems without a properly enabled module still get into matches. Once enforcement is active, they won’t. If your setup relies on a configuration that avoids TPM, whether that’s a dedicated build or a virtualised environment, migrate before the switch rather than after. Scrambling for a workaround on the day enforcement lands is how people end up with crash loops and flagged sessions.
The second thing worth reading carefully is the mention of “dependent detections”. EA is openly saying that a batch of checks is waiting on the TPM change. That points to a spike shortly after enforcement goes live instead of a slow ramp. The sensible play is to stay off the game for the first day or two after the block activates and wait for your provider to confirm status. Checking software update statuses before launching costs nothing; finding out mid-match costs an account.
Third, the Season 4 prohibited list matters more than it sounds. This isn’t only about aimbots and ESP — the wording covers tools and features that previously fell into a grey zone. If you run DMA hardware or any external configuration, watch for that Season 4 post, because something you consider harmless may show up as blockable.
Finally, treat the 95.53% figure for what it is: an average across the whole market, including cheap public builds that break with every client update. Individual products vary wildly right now. What matters is the current, verified status of the specific solution you use — see the Battlefield 6 options with stated version support — not the industry-wide headline number.
Dominate Battlefield 6 with our software
Verified cheats and software — updates within 12–48 hours after major patches, with guarantees and 24/7 support.