Learn · modules
What Is Hacker Detector in Minecraft?
Hacker Detector is a Minecraft module that scores opponents for reach, KillAura, and aimbot signatures, then flags likely cheaters mid-fight.
What is Hacker Detector?
Hacker Detector is a Minecraft module that watches everyone else in a fight and keeps a running suspicion score on who might be cheating. Every tick it checks nearby opponents against a set of known signatures: reach stretching past the vanilla limit, KillAura-style auto-attacking, aimbot-smooth rotation curves, anti-knockback suppression, click patterns too clean to be a hand. Cross the threshold and the module raises a flag. It's the same read every experienced PvPer already makes when a fight feels off, just turned into a number instead of a hunch you talk yourself out of.
How Hacker Detector works
Each tick, Hacker Detector samples nearby opponents and runs their movement, rotation, and combat behavior against known cheat signatures: reach past vanilla limit, KillAura-style auto-attacking, aimbot rotation curves, velocity or anti-knockback suppression, and click intervals that don't look human. A match adds to that player's suspicion score. Cross the threshold and the module flags them.
The scoring runs over a window of ticks rather than reacting to any single moment. A stray lag spike, one lucky click, or a coincidental frame of movement isn't enough on its own. Real cheat behavior tends to repeat consistently across a fight, and a fluke doesn't. That window is the difference between a module that's actually useful and one that cries wolf at the first weird packet.
Sample nearby opponents
Every tick, scan for players close enough to fight and gather their current position, rotation, and attack timing.
Run signature checks
Compare their behavior against known patterns: reach distance, rotation smoothness, attack cadence, knockback suppression, click timing.
Score suspicion
Each match adds to that player's running score over a time window, not a single tick.
Flag if threshold crossed
When the accumulated suspicion crosses a configured threshold, mark the player as suspicious and notify the user.
A built-in bypass test bench
Clients that ship offensive modules, KillAura, an aimbot, extended reach, tend to ship Hacker Detector too, and that's not a coincidence. Running your own detector against your own client while a bypass is active shows a developer exactly which checks trip and which don't. Tune the bypass until the local detector goes quiet and you've run something close to the same loop a server-side anticheat runs on you. Clients that build both pieces side by side tend to end up with cleaner offensive modules for it, the detector doubles as QA.
Is it safe to use?
Yes, running it carries none of the risk of the cheats it's looking for. Hacker Detector only reads information the client already has—positions, rotations, hit timing, click intervals—never authoritative server data. It never changes what your account sends to the server. No altered hits, no altered movement, no different packets. There's nothing for a server-side anticheat to catch.
Whether it's right about the other guy is a separate question. Since it reasons from client-visible state instead of the server's actual truth, its scoring is an estimate, not a verdict. A high-ping opponent, an unusual mouse setup, or a run of coincidental timing can still trip a flag, and a well-tuned bypass can sit under every threshold without lighting one up.
FAQ
No. It only reads information already visible to the client, like opponent position and hit timing. It never changes how your own character moves or attacks, and it doesn't take any action on your behalf.
Tenacity ships a HackerDetector module. The same pattern shows up in several paid clients built for competitive 1.8-era PvP under different names.
No. Because it only observes state the client already receives and never alters movement, combat, or packets sent to the server, it carries none of the risk of the cheats it's looking for.
It's an estimate, not a verdict. It reasons from client-visible state instead of the server's actual truth, so false positives and false negatives both happen. Treat a flag as a reason to watch closer, not as proof.