The headline is prevention, not a ban total
EA says its Javelin Anti-Cheat blocked 277,649 attempts to cheat or alter Battlefield 6 during July before those attempts could affect matches. That figure is not a count of banned players. The announcement does not provide a ban total.
EA also says it is monitoring 104 parts of the cheat market, covering software, hardware-based setups, sellers, and related communities. Of those, 100 showed public indications of disruption: reported detections, broken capabilities, interrupted availability, or services being taken offline. The post does not identify the affected tools, and it does not connect these numbers to any product listed on our site.
MIR was recalculated
The company changed how it calculates Match Infection Rate, or MIR. EA says the revised method removes some false reporting noise from legitimate high-skill players, particularly players who spend much of their time in vehicles, where no other anti-cheat evidence exists and manual reviews repeatedly find no violation.
Under that revised calculation, June closed at 4.62%. July peaked at 5.74% from July 13 through July 15, fell to 4.86% on July 20, and stood at 4.76% by the end of the month.
Do not use MIR as a personal detection-risk percentage or as proof that a particular cheat is up or down. It is a title-wide match metric, not a status label for one account or one tool. For context on detections, reports, updates, and player behaviour, see Why Cheats Get Detected.
What to do before playing
The practical takeaway is simple: do not treat a lack of visible warnings as evidence that a cheat is working normally or has avoided detection. EA’s own figures show continuing anti-cheat activity against both cheats and attempts to modify the game.
Check the live status information and developer notices on the relevant product page before launching. That applies when reviewing Crooked Arms for Battlefield 6 or Dullwave for Battlefield 6, for example. These links are not a claim that EA mentioned either product or that this report affected them; the source gives no product-specific details.
If compatibility with the current game build is unconfirmed, the status is unclear, or the developer has announced maintenance, wait for a clear update instead of testing it on an account. Review the safe launch checklist before any session. No cheat can be treated as risk-free.
TPM 2.0 is now enforced
EA also reiterated that its TPM 2.0 requirement has been live since August 31. This is a Battlefield 6 system requirement. It is not an announcement of a new ban wave, and it does not confirm detection of any particular product.
If the game fails to start after a system change, rule out TPM 2.0 and PC configuration issues first. Do not interpret a launch problem alone as a verdict on cheat status. If an account has already received a penalty, follow the steps in What to Do After a Ban rather than relying on random fixes.
Original source developer announcement