The Apex Legends anti-cheat team has suspended 258 Predator players after investigating account sharing on consoles. Announced on September 18, the action covers PlayStation and Xbox accounts that were accessed from multiple devices in patterns consistent with multiple people maintaining the same Ranked position. Every affected player received a 60-day suspension, with associated Ranked points also set for removal.
This was an account investigation, not a client patch
The inquiry followed community reports about Predator accounts showing unusually long, continuous Ranked sessions. Investigators reviewed login activity alongside device information connected to high-ranked accounts and found patterns they attributed to repeated account sharing.
That distinction matters. The announcement describes an enforcement action built around account and device telemetry; it does not announce a new game build, anti-cheat driver, detection module, or client-side scan. It also focuses specifically on console users rather than presenting a broader enforcement wave across every Apex Legends platform.
Some accounts appeared on five or more devices, while others were shared frequently without crossing that threshold. A third group met both conditions. The anti-cheat team says account sharing violates the game’s terms and undermines the legitimacy of the Predator leaderboard.
PlayStation and Xbox breakdown
The 258 suspensions were divided as follows:
- PlayStation: 115 players in total. Of those, 92 were categorized as frequent sharers, two appeared on five or more devices, and 21 met both criteria.
- Xbox: 143 players in total. The team identified 124 frequent sharers, two accounts used on five or more devices, and 17 that fell into both groups.
The penalties are more substantial than a temporary loss of access. Removing the relevant Ranked points directly changes the affected accounts’ leaderboard positions, addressing the advantage gained by keeping a single account active through several users or devices.
The Bot Royale ban claims were reviewed
The same update addresses community claims that recent bans had been incorrectly issued while people were playing Bot Royale. The anti-cheat team reviewed the accounts submitted as examples and performed additional validation of those enforcement decisions.
According to the published conclusion, the bans were valid. No account-specific reasons were disclosed, so the statement should not be read as an explanation of what triggered each case. It does establish that the team found no basis for blaming Bot Royale itself for the reviewed penalties. Credible reports of potential false bans will continue to be examined.
What this means for players using software
There is no source-backed reason to assume this announcement changed offsets, broke existing configurations, or introduced a new client-side detection method. It is also not, by itself, a reason to impose a fixed 24-hour waiting period. Before starting a session, however, users should still check the current software update statuses rather than treating an account-enforcement post as proof that any particular build remains compatible.
Switching products would not address the behavior described here. The investigation connected long activity patterns with login and device data, meaning the central issue was how one account was being used across several systems. Nothing in the announcement supports treating an HWID spoofer as a necessary response, particularly when the disclosed action targeted consoles and did not identify a specific hardware fingerprinting method.
Players looking for builds matched to the current game version can use the Apex Legends software catalog, but the status of each option still needs to be checked separately. Bot Royale should not be treated as a protected environment either: the reviewed cases did not support the claim that the mode caused false bans.
Dominate Apex Legends with our software
Statuses update automatically; ambiguous cases are reviewed manually. Sales may be paused during extended updates.