Apex Legends uses Easy Anti-Cheat (EAC). Like VAC, EAC scans inside the game process — external reads are invisible to it. Here's the full setup guide.
EAC and External Cheats
EAC hooks the Windows kernel to detect DLL injection and memory writes. It cannot detect a process that only reads memory from outside. The Apex build on Cosmo Cheatz uses ReadProcessMemory — EAC has no surface to scan.
Aimbot Settings for Ranked
- FOV: 12–20° in third-person fights, 8° in ADS
- Smoothing: 45–65 depending on your natural aim speed
- Aim bone: Chest (not head) — headshot rate in ranked is reviewed
- Target switch: Manual key, not auto — prevents obvious snapping between enemies
Legend-Specific Tips
Wraith / Pathfinder: High mobility — fast target switches are more believable. You can lower smoothing slightly.
Gibraltar / Caustic: Slower pace, longer fights — lower FOV and higher smoothing look natural.
Octane / Horizon: You're expected to have sharp aim. Slightly more aggressive settings are safe.
Reporting Protection
Apex has aggressive community reporting. Keep K/D under 8:1 in ranked pubs. If you're stream sniped or partied up with streamers, tone down immediately — those clips go straight to the ban team.
Download Free
Free Apex external cheat → No account, no key, updated within 24 h of EAC patches.
Verifying EAC Does Not Flag External Reads
Before trusting any external build, confirm that EAC is not flagging read-only access. EAC's kernel driver, EasyAntiCheat.sys, hooks NtReadVirtualMemory and related syscalls but only records anomalies when write or allocation flags appear. Run a controlled test on a spare account: launch Apex, attach a benign external tool that reads process memory with PROCESS_VM_READ only, and play two full matches. Check the Windows Event Viewer under Applications and Services Logs > EasyAntiCheat for event ID 2000 or 2001, which indicate integrity checks. Absence of those events after 48 hours does not guarantee safety, but presence means the build is already compromised. Many public externals fail because they request PROCESS_VM_READ | PROCESS_VM_WRITE | PROCESS_VM_OPERATION in a single OpenProcess call, which EAC logs immediately. Verify your tool's access mask with Process Hacker 2: right-click the Apex process, inspect the handle, and confirm the granted access is 0x10 (read-only) rather than 0x1F0FFF.
EAC Version Drift Since Season 20
EAC updates its module hashes with each Apex client patch, typically every three to four weeks. Since Season 20, the anti-cheat has added a check for unsigned drivers loaded within 30 seconds of game start, catching many external tools that rely on kernel-mode memory readers. Builds released before February 2024 often fail because they use a signed but now-blacklisted driver such as WinRing0.sys v1.3.0. Confirm your build's driver signature against the EAC blocklist published in the game's support articles. A working external in 2026 must use a driver signed after January 2024 and avoid any driver that exposes physical memory mapping. Test by launching Apex with the external already running; if the game closes without an error dialog within 90 seconds, EAC has silently terminated it due to driver detection. Check the Windows System log for Event ID 7045 (service installed) around the same timestamp to identify the offending component.
Common Mistakes With Bone Selection
Chest targeting is safer than head targeting, but many users misconfigure the bone ID because Apex's skeleton indices differ from other Source engine games. The chest bone in Apex is ID 6 (spine_2), not ID 5 (spine_1) or ID 8 (neck). Selecting ID 8 causes the aimbot to track the neck, which produces headshot-adjacent hits that look suspicious in killcams. Verify the bone by enabling a debug overlay that draws the selected bone as a sphere; in the firing range, aim at a dummy and confirm the sphere sits mid-torso, not at the collarbone. Another frequent error is using the same bone for all legends: Caustic's larger hitbox makes chest ID 6 appear lower than on Wraith, so reduce FOV by 2–3° when playing large characters to avoid dragging the crosshair through the arms. Test each legend for 10 minutes in the range before ranked, and log hit distribution with a simple counter; a headshot rate above 18% in ranked is a statistical outlier that report reviewers flag manually.